Hi Vidya, It is really a good start to discuss the client mobility issues in RELOAD. Using DAP and OAP seems a good solution for clients that attached to arbitary peers. However, does eClient really need a specific bootstrapping different with that in RELOAD BASE?
IMO, a client does not need to claim itselft an eClient or not when joining in the overlay. A ordinary bootstrapping can work as if it is a normal client. The node ID is allocated by bootstrap server. This client can use the Node ID to set up connection with OAP and neighbours as normal overlay nodes do. If the bootstrap server used here has the ability to consider a little bit physical network topology, the allocated node ID, of cause, is quite close to its OAP. There should no problem to set up a direct connection between the client and OAP on the overlay at the begining. Only when the client found that it is impossible to directly connect to its OAP (most of time, it is due to the client moving out of the OAD's reachability), it'll select a DAP from its neighbours. This could keep your scheme more simpler and accordant with RELOAD BASE. Right? Best Regards, Lin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Narayanan, Vidya Sent: Wednesday, July 01, 2009 4:51 AM To: [email protected] Subject: [P2PSIP] New draft on enhanced client operation for RELOAD Hi, We have submitted a draft on enhanced client operation for RELOAD. It supports the attachment of clients to arbitrary peers without needing application specific destination list population and it inherently provides support for client mobility. The draft can be found at http://www.ietf.org/internet-drafts/draft-vidya-p2psip-eclients-00.txt. Comments welcome. Thanks, Vidya _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
