draft-ietf-radext-digest-auth; SIP-AOR

["Beck01, Wolfgang" <BeckW@t-systems.com>]

Here's a text proposal for the SIP-AOR attribute, which is relevant
for the Diameter draft

2.20  SIP-AOR

   This attribute is for the authorization of SIP messages.

   Type
         [IANA:use 121 if possible] for SIP-AOR
   Length
         >=3
   String
         The syntax of this attribute corresponds either to a SIP URI
         (with the format defined in [RFC3261] or a TEL URI (with the
         format defined in [RFC3966]).
         The RADIUS client (SIP server) uses the value found in a SIP
         Request-URI or a particular header field value of the SIP
         request to construct the SIP-AOR attribute.  The selection of a
         Request-URI or a particular header field depends on the
         semantics of the SIP message and whether the SIP server is
         acting for originating or terminating requests.  For instance,
         when the SIP server receives an REGISTER request addressed from
         the served user, it maps the To header field value of the SIP
         request to this attribute.  However, when the SIP server
         receives an INVITE request originated by the served user, it
         maps either the P-Asserted-Identity or the From header field
         values to this attribute.
         This attribute MUST only be used when the RADIUS client wants
         to authorize SIP users and MUST only be used in Access-Request
         messages.

Wolfgang

--
T-Systems
Business Unit Technologiezentrum
+49 6151 9372863
Am Kavalleriesand 3
64295 Darmstadt



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>