At Wed, 24 Dec 2008 10:23:53 +0800, Song Haibin wrote: > > 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.
Yes, I agree that it's important that the bootstrap nodes be both available and publicly reachable. The question is whether the specification needs to actually provide a mechanism for the configuration server to determine that's the case or whether we can assume that the operators of the system can figure out how to do that themselves using existing IETF standards such as SNMP. IMO, the latter approach is preferable. -Ekr _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
