SIPPING Working Group IETF 67

1
SIPPING Working GroupIETF 67

• Mary Barnes
• Gonzalo Camarillo

2
Note Well

• Any submission to the IETF intended by the
  Contributor for publication as all or part of an
  IETF Internet-Draft or RFC and any statement made
  within the context of an IETF activity is
  considered an "IETF Contribution". Such
  statements include oral statements in IETF
  sessions, as well as written and electronic
  communications made at any time or place, which
  are addressed to
• the IETF plenary session,
• any IETF working group or portion thereof,
• the IESG, or any member thereof on behalf of the
  IESG,
• the IAB or any member thereof on behalf of the
  IAB,
• any IETF mailing list, including the IETF list
  itself, any working group or design team list, or
  any other list functioning under IETF auspices,
• the RFC Editor or the Internet-Drafts function
• All IETF Contributions are subject to the rules
  of RFC 3978 (updated by RFC 4878) and RFC 3979.
  Statements made outside of an IETF session,
  mailing list or other function, that are clearly
  not intended to be input to an IETF activity,
  group or function, are not IETF Contributions in
  the context of this notice.
• Please consult RFC 3978 (updated by RFC
  4878) for details.

3
Other Notes

• Need a Note Taker
• Need a scribe for Jabber session
• MP3 streaming
• Use the microphone, and state your name
• Wireless Make sure your computer is not in
  adhoc mode

4
Supplementary Web Page

• http//www.softarmor.com/sipping
• Using WGLC Process page to track WG documents,
  including WG reviews, assignments and status,
  with proposed WGLC dates for all WG documents.
• Updated monthly

5
Updated Charter (Proposed)

• Done WGLC SIP Service Examples ---New---
• Done WGLC IPv6 Transition ---New---
• Done WGLC Multiple Dialog Usages ---New---
• Done Framework for Realtime Text over IP to
  IESG as Informational ---New---
• Done WGLC Framework for Consent-based
  Communications in SIP ---New---
• Done WGLC XML Format Extension for Capacity
  Attributes in Resource Lists ---New---
• Nov 2006 SIP Service Examples to IESG as Info
• Done IPv6 Transition in SIP to the IESG as
  PS
• Done Service Quality Reporting to IESG as PS
• Nov 2006 XML Format Extension for Capacity
  Attributes in Resource Lists to the IESG as PS
  ---New---
• Dec 2006 WGLC Session Border Controller
  requirements ---New---
• Dec 2006 WGLC SPAM problems in SIP ---New---

6
Updated Charter (Proposed)

• Jan 2007 WGLC Session Policy package ---New---
• Jan 2007 WGLC User Agent Profile for Media
  Policy ---New---
• Jan 2007 Multiple Dialog Usages to IESG as Info
  ---New---
• Feb 2007 WGLC Call Control Framework ---New---
• Feb 2007 WGLC SIP Torture Tests for IPv6
  ---New---
• Feb 2007 Session Border Controller requirements
  to IESG as Info ---New---
• Feb 2007 SPAM problems in SIP to IESG as Info
  ---New---
• Mar 2007 WGLC NAT scenarios ---New---
• Mar 2007 Session Policy package to the IESG as
  PS ---New---
• Mar 2007 User Agent Profile for Media Policy to
  the IESG as PS ---New---

7
Updated Charter (Proposed)

• Apr 2007 WGLC Requirements for Management of
  Overload in SIP ---New---
• Apr 2007 WGLC SIP Offer/Answer Examples
  ---New---
• Apr 2007 SIP Call Control - Transfer to IESG as
  Info ---New---
• Apr 2007 Call Control Framework to the IESG as
  Info ---New---
• Apr 2007 SIP Torture Tests for IPv6 to the IESG
  as Info ---New---
• May 2007 WGLC SIP Race Condition Examples
  ---New---
• May 2007 NAT Scenarios to IESG as Info ---New---
• June 2007 Requirements for Management of Overload
  in SIP to IESG as Info ---New---
• June 2007 SIP Offer/Answer Examples to IESG as
  Info ---New---
• July 2007 SIP Race Condition Examples to IESG as
  Info ---New---
• Aug 2007 Revise Charter

8
RFCs Published since IETF 67

• RFC 4596 - draft-ietf-sipping-callerprefs-usecases
  (Informational)
• RFC 4579 - draft-ietf-sipping-cc-conferencing
  (BCP)
• RFC 4575 - draft-ietf-sipping-conference-package
  (PS)
• RFC 4569 - draft-ietf-sipping-message-tag
  (Informational)
• RFC 4484 - draft-ietf-sipping-trait-authz
  (Informational)

9
RFC Editors Queue

• draft-ietf-sipping-app-interaction-framework (PS)
• draft-ietf-sipping-kpml (PS)
• draft-ietf-sipping-transc-conf (PS)

10
Post-Publication Request

• draft-ietf-sipping-uri-services (PS)
• draft-ietf-sipping-transc-framework (Info)
• draft-ietf-sipping-rtcp-summary (PS)
• draft-ietf-sipping-gruu-reg-event (PS)

11
Publication Requested

• draft-ietf-sipping-v6-transition (PS)
• draft-ietf-sipping-toip (Info)

12
WGLC Completed

• draft-ietf-sipping-v6-transition (July 20)
• draft-ietf-sipping-capacity-attribute (Sept 19)
• draft-ietf-sipping-dialogusage-04 (Oct 2)
• draft-ietf-sipping-consent-format (Oct 17)
• draft-ietf-sipping-pending-additions (Oct 17)
• draft-ietf-sipping-config-framework (Oct 31)

13
WG items moved to SIP WG

• Due to normative SIP changes, the following
  documents moved to SIP WG for completion
• draft-ietf-sipping-consent-framework
• draft-ietf-sipping-session-policy-framework
• draft-ietf-sipping-uri-list-message
• draft-ietf-sipping-uri-list-subscribe
• draft-ietf-sipping-multiple-refer
• draft-ietf-sipping-uri-list-conferencing
• draft-ietf-sipping-xcap-config

14
New proposed WG items

• Based on past agreements, adding the following
  to the charter
• SBC requirements
• Race Condition examples
• Overload Requirements
• Offer/answer examples
• IPv6 Torture test examples

15
Monday Agenda

• 0900 Chairs - Status and Agenda Bash 
• 0915 Volker Hilt - Session Policies
• 0945 Jonathan Rosenberg - Overload Requirements
• 1000 Volker Hilt - Overload Control
• 1015 Daryl Malas - SIP End-to-end Performance
  Metrics
• 1030 Mayumi Munakata - Clarification of Privacy
  Mechanism
• 1045 Jani Hautakorpi - Method for URI-List
  Servers to Refuse the Handling of a URI-List
• 1100 Brian Stucker - Early Media

16
Tuesday Agenda

• 1850 Chairs - Status and Agenda Bash 
• 1855 Adam Roach - Call Completion Service
• 1920 Paul Kyzivat - Offer/answer usage
• 1935 Jun Koshiko - Race Conditions

17
SIP Torture Test Messages for IPv6

• -03 fairly complete.
• Some pending comments will be folded into next
  revision after San Diego.
• One open issue around representing IPv6 literals
  in Via received parameter use and ? Or not?
• Via SIP/2.0/TCP foo.example.comreceived2001
  db8branch...
• OR
• Via SIP/2.0/TCP foo.example.comreceived2001d
  b8branch...
• At 18th SIPit (April 2006), we observed
• Those testing IPv6 made different assumptions
  about enclosing  literal v6 addresses in Vias in
  . By the end of the event, most implementations
  were  accepting either. Its about 50/50 on what
  gets sent. RjS.

18
SIP Torture Test Messages for IPv6 - Draft Update

• Currently authors prefer using and .
  However, no consensus on the list.
• Therefore Following the Robustness Principle of
  RFC1122, S3.4 of 03 contains two test cases one
  using and , and the other without.
  Implementations are expected to pass both.

19
draft-littlefield-sipping-mgmt-event-01

• What?
• Defines a Management Request Event Package to
  trigger UA establishment of management sessions
• Why?
• Difficult to reach UAs behind NAT and Firewall
  devices for management
• Key Features
• UAs can indicate supported management protocols
  SUBSCRIBE to a compatible Management System
• Allows Management System to NOTIFY client when a
  management session is needed