Hi Eric, For clarification: The "name" is the AOR (e.g. for the SIP usage "[email protected]"). Additionally, there's a node id in form of a URI following the syntax of 13.12..
Correct ? So coming back to the roots and the question of Neil: In 10.3., what is meant with the destination list in '... and MUST contain a Destination list with a single entry of type "node_id". ' Cheers, fpm On Wed, Feb 24, 2010 at 2:18 AM, Eric Rescorla <[email protected]> wrote: > On Tue, Feb 23, 2010 at 4:37 AM, neil.young <[email protected]> wrote: >> >>> Could you, or anyone else, clarify what is meant with that rfc822name >>> "to use in the overlay" ? Why is it there ? >>> >>> >> >> AFAIK the username is a human readable name for a given RELOAD peer or >> client. >> >>> Assume you have a central enrollment and a SIP usage, the client >>> (application) may want to know from this enrollment which AOR it >>> should use. I.e. you have a mobile device, within the enrollment >>> process, the AOR should be provided by enrollment since the Client >>> (user) does not want to configure it's AOR manually in the phone (you >>> never did that with you "old" mobile, right ?). >>> >>> >> >> Hmm. My understanding is that a SIP usage of RELOAD stores and fetches AORs >> on its own. This has nothing to do with the information provided in a >> certificate used at RELOAD transport level (hence nothing to do with the >> rfc822name and/or node_ids, used to manage the RELOAD functionality). But >> this is only my understanding. >> >> The SIP AOR is for me nothing special than a datum, stored in the DHT of the >> overlay, able to be retrieved from that. >> >> But I might be wrong. And because all experts prefer to not comment, we >> might stay stupid for a certain time :( > > My intention was always that the name in the certificate was the AOR. > obviously > the documents aren't clear on this point. Can you suggest some text that > would help? > > -Ekr > _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
