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?
A lookup for "user name" in the draft gives several hits, some of it
give a tendency for an AOR:
The most natural rule is that a certificate authorizes a user to
store data keyed with their user name X. This rule is used for all
the kinds defined in this specification. Thus, only a user with a
certificate for "[email protected]" could write to that location in
the overlay.
10.3.1
o A single name this user is allowed to use in the overlay, using
type rfc822Name.
12.3
When a user enrolls in the Overlay Instance, they request or are
assigned a unique name, such as "[email protected]".
Each certificate enables an entity to act in two sorts of roles:
o As a user, storing data at specific Resource-IDs in the Overlay
Instance corresponding to the user name.
and many more.
So for the user name is sort of AOR, but not especially meant to be used
for a SIP usage only. It is basically a RELOAD user name. It entitles a
user to store data in the overlay using the given user name. If
perpended with "sip:" it forms an AOR, ready to be used by a SIP usage.
Am I correct?
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
