MSRP ACM

1
MSRP ACM

• Draft-ietf-simple-msrp-acm
• IETF76, Hiroshima, Japan
• Christer Holmberg_at_ericsson.com

2
SINCE PREVIOUS IETF

• OPEN ISSUE Usage of aconnection attribute
• SOLUTION Attribute not used, existing MSRP
  connection re-use rules used.
• OPEN ISSUE c/m versus apath for routing
  information
• SOLUTION apath
• No change from RFC4975

3
OPEN ISSUE session matching

• Where to update the RFC 4975 session matching
  procedure?
• 7.3. Receiving Requests
• The receiving endpoint MUST first check the URI
  in the To-Path to make sure the request belongs
  to an existing session. When the request is
  received, the To-Path will have exactly one URI,
  of which the session-id component MUST map to an
  existing session that is associated with the
  connection on which the request arrived. If this
  is not true, then the receiver MUST generate a
  481 error and ignore the request. Note that if
  the Failure-Report header field had a value of
  "no", then no error report would be sent.

4
OPEN ISSUE SESSION MATCHING

• Where to update the RFC 4975 session matching
  procedure?
• Alt 1 4576bis?
• Alt 2 MSRP ACM draft??
• Alt 3 Separate draft?
• PROPOSAL Alternative 3 separate draft.

5
NEXT STEPS

• Submit new version of MSRP ACM draft
• Start WGLC or MSRP ACM draft
• Submit session-matching-update draft