Hi Julian, The enrollment server mentioned in this draft is required to support the communication messages between an overlay peer and itself. We don't define the exact message formats yet, but reusing the existing messages(whatever they are) are preferred.
Xie Xie, Haibin > -----Original Message----- > From: jc [mailto:[email protected]] > Sent: Tuesday, March 02, 2010 11:35 PM > To: Song Haibin > Cc: 'P2PSIP WG' > Subject: Re: [P2PSIP] New draft notification: > draft-song-p2psip-bootstrap-status-maintenance-00 > > Hi, > Are you building some new type of enrollment server? What > I've read thus far is fairly impossible to do with the > current drafted enrollment server which is simply an HTTP > server that isn't connected to the Overlay. > > Regards, > Julian > > On Mar 2, 2010, at 1:38 AM, Song Haibin wrote: > > > Dear all, > > > > I have submitted a new I-D, which can be accessed at: > > > http://tools.ietf.org/id/draft-song-p2psip-bootstrap-status-maintenanc > > e-00.t > > xt > > > > Abstract: > > In order to join the overlay, a joining peer/client has to find the > > enrollment server first, and then acquire the configuration > file from > > the enrollment server where it can find the bootstrap peers' > > information, and after that it contact a bootstrap node to > route the > > join request message to join the overlay. However, nodes > in P2PSIP overlay network are dynamic. > > They can leave gracefully or abruptly at any time. This document > > focuses on the bootstrap server mechanism and proposes a > mechanism to > > select proper bootstrap peers and improve the availability of > > bootstrap nodes through bootstrap peer status maintenance. > > > > > > BR, > > Haibin > > > > > > _______________________________________________ > > P2PSIP mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/p2psip > > _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
