Hi Bruce, Various early drafts have proposed the mechanisms of bootstrap peer discovery, e.g. draft-garcia-p2psip-dns-sd-bootstrapping-00, and draft-matthews-p2psip-bootstrap-mechanisms-00. Even in the p2psip base draft section 11.4, it also describes that using the cached peers or broadcast mechanisms to find the bootstrap peers. However, the only remaining issue here is what I mentioned in my last email that how the enrollment server guarantees the effectiveness of the information of the bootstrap peers in the configuration file, which is very important for the initial bootstrap process of p2p nodes, even for the later bootstrap process when it can't find effective bootstrap nodes with other methods.
The charter assumes the enrollment server can provide an initial set of bootstrap nodes, but I am not sure if it assumes the effectiveness of the bootstrap nodes. By the way, another factor that impacts the effectiveness of the bootstrap nodes is that whether or not the bootstrap nodes are behind NATs. Best Regards, Haibin Email: [email protected] Skype: alexsonghw >-----Original Message----- >From: Bruce Lowekamp [mailto:[email protected]] >Sent: Wednesday, December 24, 2008 12:33 AM >To: Roni Even >Cc: Eric Rescorla; Song Haibin; [email protected] >Subject: Re: [P2PSIP] Bootstrap peer status > >Hi Roni, > >My understanding of that part of the charter is that the base protocol >can simply assume that there exists some way for the enrollment server >to be aware of the bootstrap peers. So we don't need to solve that >problem in the base draft. I think this makes sense because the >process of identifying and tracking active bootstrap peers will be >very deployment specific. > >With that said, if someone works up some solutions to that problem and >submits a good draft that really addresses the problem, I would be in >favor of adding it to the charter. > >Bruce > > >On Tue, Dec 23, 2008 at 11:00 AM, Roni Even <[email protected]> wrote: >> Hi, >> From the p2psip Charter >> >> "The initial work will assume the existence of some enrollment process >> that provides a unique user name, credentials, and an initial set of >> bootstrap nodes if that is required by the protocols." >> >> I think that bootstarp nodes are important to the solution, so option 2 is >> part of the required solution. >> Regards >> Roni Even >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of >> Eric Rescorla >> Sent: Tuesday, December 23, 2008 4:10 PM >> To: Song Haibin >> Cc: [email protected] >> Subject: Re: [P2PSIP] Bootstrap peer status >> >> At Tue, 23 Dec 2008 17:38:38 +0800, >> Song Haibin wrote: >>> >>> >>> Overlay configuration file has contained some bootstrap peers' >> information. >>> For the initial join of a peer, I think we should ensure the effectiveness >>> of the bootstrap information in the configuration file. IMO, two options >>> here: >>> >>> (1) The administrator of the overlay has deployed some always on bootstrap >>> peer, the information of these bootstrap peers is included in the overlay >>> configuration file; >>> >>> (2) The enrollment server should keep status of bootstrap peers at least >>> some of them, to ensure that it can always provide information of some >>> effective bootstrap peers >> >> IMO, this is outside the scope of the specification. >> >> -Ekr >> _______________________________________________ >> P2PSIP mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/p2psip >> >> _______________________________________________ >> P2PSIP mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/p2psip >> _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
