Diameter SIP application

1
Diameter SIP application

• Miguel A. Garcia
• draft-ietf-aaa-diameter-sip-app-01.txt
• e-mail Miguel.An.Garcia_at_nokia.com

2
Changes in the last draft

• The SIP-Authentication-Info AVP type changed from
  OctetString to UTF8string (since SIP is encoded
  in UTF8).
• The SIP-Authentication-Context AVP type changed
  to become a grouped AVP.
• Now it contains a SIP-Entity-Body-Hash AVP
• Shorter messages.
• The Diameter server needs the hash, not the
  (long) body.
• Easier compatibility with Radius
• Added a descriptive text indicating the intention
  of each command/answer pair.
• Deleted references to PGP, since it is deprecated
  in SIP.

3
Changes in the last draft (2)

• The draft focuses on interacting with HTTP Digest
  authentication in SIP, since it is the mandatory
  authentication mechanism in SIP.
• Extensions can provide other support for other
  authentication mechanisms in SIP.
• Fixed an error in the scenario Diameter server
  authenticates the user
• It was impossible to download the user profile.
• The solution is to add a SAR/SAA messages, if the
  SIP server needs the user profile.
• Added a Redirect-Host-Usage and
  Redirect-Max-Cache-Time AVPs to all the answers.
• Added a Security considerations section.

4
Future plan

• Close the remaining open issues listed in the
  draft.
• Cross check that the draft fulfills all the
  requirements of RFC 3702.
• We will turn the Authorization-Info directive
  into a grouped AVP. Each of the AVPs will contain
  a Digest directive
• This relieves the Diameter server from doing SIP
  parsing.
• We will submit a new version in April and request
  WGLC.