2010/7/8 Xianghan Zheng <[email protected]> > " One or more Node-IDs which MUST be cryptographically random > [RFC4086]. Each MUST be chosen by the enrollment server in such a > way that they are unpredictable to the requesting user. Each is > placed in the subjectAltName using the uniformResourceIdentifier > type and MUST contain RELOAD URIs as described in Section 13.13 > and MUST contain a Destination list with a single entry of type > "node_id"." > > That means, the source ([email protected]), who wants to send INVITE to > destination ([email protected]), needs to first ask enrollment server "what > is the ID of the destination?", and then sends out the request to the > overlay?"
No. You publish your mapping in the overlay. > RELOAD is about arranging for a channel to teh peer over which SIP > can then > flow. It doesn't seem to me that that subsumes most of SIP but YMMV. > > Yes, i agree. However, what i means is: SIP message in the upper layer > looks useless in the connection (It might be easier for interworking or > adopt with SIP UA.) For example, SIP protocol have a Via header, recording > the intermediate routes. In RELOAD solution, this "via" header would be > empty. And all the functions are migrated into the P2P layer. > > Sorry if i understand wrong. > There's a lot more to SIP than routing. -Ekr > Regards, > Xianghan > ________________________________________ > 发件人: Eric Rescorla [[email protected]] > 发送时间: 2010年7月6日 18:40 > 收件人: Xianghan Zheng > 抄送: [email protected] > 主题: Re: [P2PSIP] ID generation and P2P layer function questions > > 2010/7/6 Xianghan Zheng <[email protected]>: > > Hi All, > > > > I get questions when i quick review RELOAD v8 proposals: > > > > (1) RELOAD mention that central enrollment server is used for the > generation > > of Node-ID (Section 3.5.2), However, it looks not mention how it > > is calculated. By hashing the SIP URI? Or random assignment? > > > " One or more Node-IDs which MUST be cryptographically random > [RFC4086]. Each MUST be chosen by the enrollment server in such a > way that they are unpredictable to the requesting user. Each is > placed in the subjectAltName using the uniformResourceIdentifier > type and MUST contain RELOAD URIs as described in Section 13.13 > and MUST contain a Destination list with a single entry of type > "node_id"." > > > > (2) Can i understand RELOAD proposal is 95% P2P functions and with a > little > > bit 5% SIP usage, since most of the functions originally designed in SIP > > protocol have been migrated into P2P layer. > > I don't really know what that means. > > RELOAD is about arranging for a channel to teh peer over which SIP can then > flow. It doesn't seem to me that that subsumes most of SIP but YMMV. > > -Ekr >
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
