2.5.12 Session Initiation Proposal Investigation (sipping)

NOTE: This charter is a snapshot of the 74th IETF Meeting in San Francisco, CA USA. It may now be out-of-date.
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional SIPPING Web Page

Last Modified: 2009-05-01

Chair(s):

Mary Barnes <mary.barnes@nortel.com>
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>

Real-time Applications and Infrastructure Area Director(s):

Robert Sparks <rjsparks@nostrum.com>
Cullen Jennings <fluffy@cisco.com>

* The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65.

Real-time Applications and Infrastructure Area Advisor:

Robert Sparks <rjsparks@nostrum.com>

Secretary(ies):

Oscar Novo <Oscar.Novo@ericsson.com>

Mailing Lists:

General Discussion: sipping@ietf.org
To Subscribe: sipping-request@ietf.org
In Body: (un)subscribe
Archive: http://www.ietf.org/mail-archive/web/sipping/index.html

Description of Working Group:

The Session Initiation Protocol Project INvestiGation (SIPPING)
working group is chartered to document the use of SIP for several
applications related to telephony and multimedia, and to develop
requirements for extensions to SIP needed for those applications.
Such requirements will be referred to the SIP working group for
development of any new SIP method, header, or option-tag as described
in Change Policy for SIP (RFC 3467).

Guiding principles for the performance of SIPPING's work will include:

1. Documenting the requirements of specific chartered tasks.

2. Documenting the usage of SIP to solve real problems that need
to be solved in a standardized way. Examples of important
topics identified are the session policy architecture, allowing
network entities to convey policy into an User Agent's
activity; requirements analysis for session border
controllers to determine how best such devices can
operate with SIP usage; guidance on IPv4-IPv6
co-existence support by SIP and SIP-supported media; and
inclusion of real-time text conversation (ToIP), service
invocations benefitting hearing and speech impaired users,
and other SIP equal access services as requirements are proposed.

3. Looking for commonalities among the chartered tasks and ongoing
SIP-related development, as commonalities may indicate for general,
reusable functionality in SIP.

4. Describing the requirements for any extension determined to pass
there hurdles, and handing the development task to the SIP WG.

5. Developing procedures and requirements for configuration and
delivery of SIP User Profiles

Besides performing needed specification of several applications
of SIP, SIPPING can be seen as also working out use cases that
clarify the role of SIP in the Internet, and help to ensure that
Occam's razor is appropriately applied to SIP usage.

The security of all the deliverables will be of special importance.
The technology for security will be keyed from the SIP Security
specification within RFC 3261, and additional SIP specifications
as they apply.

Goals and Milestones:

Done  Submit Internet-Draft on SIP-Telephony Framework to IESG for consideration as a BCP
Done  Submit Internet-Draft on ISUP-SIP Mapping to IESG for consideration as Proposed Standard
Done  Submit Internet-Draft on Requirements for use of SIP to support telephony for the Hearing-Impaired to IESG for consideration as an Informational RFC
Done  Submit SIP 3rd party call control to IESG for consideration as BCP
Done  Submit Internet-Draft on 3G Requirements to IESG for consideration as an Informational RFC
Done  Submit Internet-Draft on Mapping ISUP Overlap Signaling to SIP to IESG for consideration as a Proposed Standard
Done  Submit Internet-Draft on Usage Guideline for Events (Subscribe-Notify) to IESG for consideration as an Informational RFC
Done  Submit Internet-Drafts Basic and PSTN Call Flows to IESG fro consideration as BCPs
Done  Requirements for Content Indirection in SIP
Done  Submit Message Waiting SIP event package to IESG for consideration as PS
Done  Using ENUM with SIP Applications to IESG for consideration as an Informational RFC
Done  Requirements for Reuse of Connections in SIP
Done  Submit Internet-Draft on T.38 Fax Call Flows to IESG for consideration as a BCP
Done  Requirements for SIP Request History
Done  Submit Internet-Draft on Requirements for AAA Application in SIP Telephony to IESG for consideration as an Informational RFC
Done  Sip Interworking with QSIG
Done  3pcc Transcoding to IESG as Info
Done  KPML to IESG as PS
Done  Conferencing Requirements to IESG as Info
Done  Conferencing Framework to IESG as Info
Done  Conferencing Call Control-Conferencing to IESG as BCP
Done  End-to-Middle Security Requirements to IESG as Info
Done  Configuration Framework to the IESG as a PS
Done  Revise Charter
Done  Requirements for Consent-based Communications in SIP to IESG as Info
Done  Framework for Consent-based Communications in SIP to IESG
Done  Submit URI List Transport Mechanism to the IESG as PS
Done  Requirements on Trait-Based Authorization to IESG as Info
Done  Transcoding Framework to IESG as Info
Done  Transcoding with Conf Bridge to IESG as Info
Done  Service Quality Reporting to IESG as PS
Done  IPv6 Transition in SIP to the IESG as Info
Done  WGLC SIP Service Examples
Done  WGLC IPv6 Transition
Done  Framework for Realtime Text over IP to IESG as Informational
Done  WGLC Multiple Dialog Usages
Done  SIP Service Examples to IESG as Info
Done  Format Extension for Capacity Attributes in Resource Lists to the IESG as PS
Done  WGLC SPAM problems in SIP
Done  WGLC Session Border Controller requirements
Done  Multiple Dialog Usages to IESG as Info
Done  WGLC User Agent Profile for Media Policy
Done  WGLC Session Policy package
Done  SPAM problems in SIP to IESG as Info
Done  Session Border Controller requirements to IESG as Info
Done  WGLC SIP Torture Tests for IPv6
Done  WGLC Call Control Framework
Done  Session Policy package to the IESG as PS
Done  SIP Torture Tests for IPv6 to the IESG as Info
Done  SIP Call Control - Transfer to IESG as Info
Done  WGLC SIP Offer/Answer Examples
Done  WGLC Requirements for Management of Overload in SIP
Done  WGLC SIP Race Condition Examples
Done  Requirements for Management of Overload in SIP to IESG as Info
Done  SIP Race Condition Examples to IESG as Info
Done  SIP Offer/Answer Examples to IESG as Info
Done  Call Control Framework to the IESG as Info
Done  WGLC NAT scenarios
Aug 2008  Presence Scaling Requirements WGLC
Sep 2008  Service Identification to IESG as INFO
Done  Service Identification WGLC
Done  Updates to Asserted Identity in SIP WGLC
Oct 2008  Schema and Guidelines for SIP User Agent Profile Datasets WGLC
Nov 2008  Presence Scaling Requirements to IESG as Info
Dec 2008  Updates to Asserted Identity in SIP to IESG as Info
Jan 2009  User Agent Profile for Media Policy to the IESG as PS
Jan 2009  Schema and Guidelines for SIP User Agent Profile Datasets to IESG as PS
Jan 2009  Overload Design Considerations WGLC
Mar 2009  NAT Scenarios to IESG as Info
Mar 2009  Revise Charter
Apr 2009  Overload Design Considerations to IESG as Info

Internet-Drafts:

  • draft-ietf-sipping-app-interaction-framework-05.txt
  • draft-ietf-sipping-v6-transition-07.txt
  • draft-ietf-sipping-gruu-reg-event-09.txt

    Request For Comments:

    RFCStatusTitle
    RFC3324 I Short Term Requirements for Network Asserted Identity
    RFC3351 I User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired individuals
    RFC3372 BCP Session Initiation Protocol (SIP) for Telephones (SIP-T): Context and Architectures
    RFC3398 PS Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
    RFC3485 PS The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
    RFC3578 PS Mapping of of Integrated Services Digital Network (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)
    RFC3665 BCP Session Initiation Protocol Basic Call Flow Examples
    RFC3666 BCP Session Initiation Protocol PSTN Call Flows
    RFC3680 Standard A Session Initiation Protocol (SIP) Event Package for Registrations
    RFC3702 I Authentication, Authorization and Accounting Requirements for the Session Initiation Protocol
    RFC3725 BCP Best Current Practices for Third Party Call Control in the Session Initiation Protocol
    RFC3824 I Using E.164 numbers with the Session Initiation Protocol (SIP)
    RFC3842 Standard A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
    RFC3959 Standard The Early Session Disposition Type for the Session Initiation Protocol (SIP)
    RFC3960 I Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)
    RFC4083 I Input 3rd-Generation Partnership Project (3GPP) Release 5 requirements on the Session Initiation Protocol (SIP)
    RFC4117 I Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)
    RFC4189 I Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)
    RFC4235 Standard An INVITE-Inititiated Dialog Event Package for the Session Initiation Protocol (SIP)
    RFC4245 I High-Level Requirements for Tightly Coupled SIP Conferencing
    RFC4353 I A Framework for Conferencing with the Session Initiation Protocol (SIP)
    RFC4411 PS Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events
    RFC4453 I Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)
    RFC4475 I Session Initiation Protocol (SIP) Torture Test Messages
    RFC4484 I Trait-based Authorization Requirements for the Session Initiation Protocol (SIP)
    RFC4497 BCP Interworking between the Session Initiation Protocol (SIP) and QSIG
    RFC4569 I Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag
    RFC4575 PS A Session Initiation Protocol (SIP) Event Package for Conference State
    RFC4579 BCP Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents
    RFC4596 I Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension
    RFC4730 PS A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)
    RFC5039 I The Session Initiation Protocol (SIP) and Spam
    RFC5057 I Multiple Dialog Usages in the Session Initiation Protocol
    RFC5118 I Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)
    RFC5194 I Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)
    RFC5359 BCP Session Initiation Protocol Service Examples
    RFC5361 PS A Document Format for Requesting Consent
    RFC5362 PS The Session Initiation Protocol (SIP) Pending Additions Event Package
    RFC5363 PS Framework and Security Considerations for Session Initiation Protocol (SIP) Uniform Resource Identifier (URI)-List Services
    RFC5364 PS Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists
    RFC5369 I Framework for Transcoding with the Session Initiation Protocol (SIP)
    RFC5370 PS The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
    RFC5390 I Requirements for Management of Overload in the Session Initiation Protocol
    RFC5407 BCP Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)

    Meeting Minutes


    Slides

    Agenda Status
    Re-INVITE Handling in SIP & Media State under Preconditions in SIP
    Reject Offer in PRACK
    Identity
    Profile Datasets
    SIP Overload Control
    Event Throttle
    RFC3427bis