90 likes | 102 Views
Diameter SIP Application. draft-ietf-aaa-diameter-sip-app-00.txt. 58th IETF meeting miguel.a.garcia@ericsson.com mccap@lucent.com. What is it? . A Diameter application born in the 3GPP IP Multimedia Subsystem (IMS), moving to solve a wider standard problem. Provides SIP servers with:
E N D
Diameter SIP Application draft-ietf-aaa-diameter-sip-app-00.txt 58th IETF meeting miguel.a.garcia@ericsson.com mccap@lucent.com
What is it? • A Diameter application born in the 3GPP IP Multimedia Subsystem (IMS), moving to solve a wider standard problem. • Provides SIP servers with: • Authentication • Authorization • Accounting information • Designed to be used in conjunction with SIP (RFC 3261) • Includes 6 new commands and a few AVPs • A solution for draft-ietf-sipping-aaa-req-03 (under IESG review)
Architecture PPR/PPA MAR/MAA SAR/SAA RTR/RTA AAA xyz.com UAR/UAA LIR/LIA SIP server abc.com SIP server xyz.com SIP server xyz.com SIP SIP SIP mobile
Changes from last version • This is the first version of the draft published as WG item. • Draft changed its name to reflect the dependency on SIP. • New definitions section added. • New applicability section added. • The problem of locating a Diameter server is addressed with the introduction of a new Diameter Subscriber Locator role.
Changes from last version (2) • A few AVPs have been renamed to accurately reflect the intention of the AVP. For instance, SIP-Server-Name becomes SIP-Server-URI, and SIP-Public-User-ID becomes SIP-AOR. • MAR command can be used more generically. Particularly, it does not assume a SIP REGISTER message. So we had to add a new SIP-Method AVP to indicate the SIP method that triggered the MAR command.
Changes from last version (3) • Added new scenarios to indicate usage in a more generic Internet environment in an effort to remove dependencies/assumptions from 3GPP. • User-Name is no longer mandatory in requests, as typically a SIP request will not contain a user name. • IANA section has been carefully rewritten to give detailed instructions to IANA on what is required to register.
Flow 1 The Diameter server Authenticates the request
Next steps • Address the remaining open issues documented in the draft • Add a clear description of the semantics of each command. • Add a missing Security Considerations section • Provide support to use SIP and Diameter in conjunction with other authentication methods that HTTP Digest (e.g, S/MIME, TLS, P-Asserted-Identity). • Deep review throughout the whole document