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
