I agree. "Public" here does not mean a global routable address. IMO, it depends on the scenarios. As you mentioned, in some closed overlay, it does not require bootstrap peer to have a public address. It only requires that the bootstrap peers can be reached by any other peers in the same overlay directly. In relay draft(http://tools.ietf.org/id/draft-jiang-p2psip-relay-00.txt), authors propose a mechanism to determine whether a peer can be a "public peer".
I'd like to add a term in concetp draft to make "public" more clear. Regards Jiang XingFeng > All, > RELOAD requires that a node have a public IP address in order to > serve as a bootstrap peer. One issue with that is that there is > no real way to know for sure that a particular address is globally > routable. Second, there may be overlays where this is not > necessary at all (e.g., overlays formed entirely in an enterprise > network may not have any peers that are globally reachable). > Third, a bootstrap peer is still useful even if it only helps a > few peers get on the overlay. > > Hence, I don't think the requirement for serving as a bootstrap > peer is to have a globally routable address. Rather, it is to be > reachable to at least some set of nodes wanting to join the > overlay. > > Thoughts? > > - 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
