remaining issues of draft-ietf-radext-digest-auth

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

During the meeting, Lionel Morand raised the question what parts
of the SIP URI should be put into a SIP-AOR attribute. We
(Lionel, Miguel Garcia, and I) had a discussion afterwards.
The conclusion was, that it is reasonable to include fetch
the entire SIP URI. To make this more obvious, I propose the
following text:

"The SIP-AOR attribute holds the complete URI, including
parameters and other parts. It is up to the RADIUS server
what components of the URI are regarded in the authorization
decision."

Jari: I think issue 11 is resolved in
http://bgp.potaroo.net/ietf/ids/draft-ietf-radext-digest-auth-01.txt.
Can you check this?


Wolfgang

--
T-Systems International GmbH
Technologiezentrum
Next Generation IP Services and Systems
+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/>