> I might be missing the point, but I don't think Bruce is talking about > the enrollment server here at all. > > The question rather is what the purpose of a bootstrap server that > isn't also a peer. If a bootstrap server is just essentially a > persistent bootstrap peer, then I think RELOAD already has this.
> > The question is -- do you have an interest in a server that is the > bootstrap server but *isn't* a peer, and if so, why? If not, isn't a > bootstrap server really just a bootstrap peer that happens to be up > all the time? Right. In my mind, bootstrap server could learn enough peer information in the overlay. But maintaining accurate information about peer, for instance, online or offline, will make the bootstrap server hard to scale. So trying candidate mechanisms sequentially may be useful. Anyway, I think bootstrap peer would be listed as a candiate mechanism. Whether the bootstrap server is really used in the specific deployments is up to network operator . > > On Mon, Jul 28, 2008 at 3:29 AM, jiangxingfeng 36340 > <[EMAIL PROTECTED]> wrote: > > Hi, Bruce: > >> > I think bootstrap server should be included. > >> > > >> > >> Currently reload doesn't have a notion of a bootstrap server > >> (separate > >> from a bootstrap peer). I'm not really sure what the purpose of > >> having > >> a non-peer bootstrap server would be, actually. > > > > In my mind, I think there are big difference between enrollment > server and bootstrap server. Enrollment server is contacted when a > user first joins the p2p system, but the bootstrap server should > be contacted each time the user joins the system if the boostrap > server is used. Although boostrap server role could be taken by a > peer, but the procedure for getting bootstrap peer from bootstrap > server has different semantics from the JOIN proced > > ure, so it should be handle differently. > > > > > >> OTOH, I don't > >> think > >> the existing protocol would need to be changed at all to support > >> it---the JP doesn't need to know it's not a bootstrap peer it's > >> contacting and the routing wouldn't be any different from the JP > >> or AP's > >> perspectives. > > > > I am not sure I understand above texts. If a JP does not know > where the bootstrap server is, where will it send the JOIN message? > > > > > > Regards! > > > > JiangXingFeng > > > > > > _______________________________________________ > > P2PSIP mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/p2psip > > > > > > -- > David A. Bryan > [EMAIL PROTECTED] > +1.757.565.0101 x101 > +1.757.565.0088 (fax) > www.SIPeerior.com > _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
