Session Initiation Protocol Core (sipcore)

Last Modified: 2009-07-09

Additional information is available at tools.ietf.org/wg/sipcore

Chair(s):

  • Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>

  • Adam Roach <adam@nostrum.com>

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

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

    Real-time Applications and Infrastructure Area Advisor:

  • Robert Sparks <rjsparks@nostrum.com>

    Secretary(ies):

  • Oscar Novo <Oscar.Novo@ericsson.com>

    Mailing Lists:

    General Discussion: sipcore@ietf.org
    To Subscribe: https://www.ietf.org/mailman/listinfo/sipcore
    Archive: http://www.ietf.org/mail-archive/web/sipcore/

    Description of Working Group:

    The Session Initiation Protocol Core (SIPCore) working group is
    chartered to maintain and continue the development of the core SIP
    specifications, currently defined as proposed standard RFCs 3261, 3262,
    3263, 3264, and 3265.

    The SIPCore working group will concentrate on specifications that
    update or replace the core SIP specifications. In this context,
    "update" means replacing or modifying protocol elements in the above
    listed RFCs in ways that would affect most or all implementations of
    those RFCs alone. Extensions to SIP that add new functionality that
    would not be required of all implementations will be done outside of
    this WG. The process and requirements for such extensions are
    documented in RFC 3427bis, "Change Process for the Session Initiation
    Protocol".

    Throughout its work, the group will strive to maintain the basic
    model and architecture defined by SIP. In particular:

    1. Services and features are provided end-to-end whenever possible.

    2. Reuse of existing Internet protocols and architectures and
    integrating with other Internet applications is crucial.

    The primary source of change requirements will be a) interoperability
    problems that stem from ambiguous, or under-defined specification,
    and b) requirements from other working groups in the RAI Area.

    Although in general the WG will not work on extensions to SIP, it
    may take on some previous work items from the SIP working group
    to allow for a smooth transition. The adoption of new items requires
    explicit agreement from the AD or rechartering.

    Goals and Milestones:

    Jul 2009  Delivering request-URI and parameters to UAS via proxy to IESG (PS)
    Jul 2009  INFO package framework to IESG (PS)
    Aug 2009  Termination of early dialog prior to final response to IESG (PS)
    Aug 2009  Location Conveyance with SIP to IESG (PS)
    Sep 2009  Essential corrections to RFC 3261 (1st batch) to IESG (PS)
    Oct 2009  Example security flows to IESG (Informational)
    Oct 2009  Extension for use in etags in conditional notification toIESG (PS)
    Dec 2009  SIP Events throttling mechanism to IESG (PS)
    Dec 2009  Mechanism for indicating support for keep-alives (PS)
    Dec 2009  Error corrections and clarifications to RFC3265 to IESG (PS)
    Jan 2010  Presence Scaling Requirements to IESG as Info

    Internet-Drafts:

    Scaling Requirements for Presence in SIP/SIMPLE (17871 bytes)
    An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification (51629 bytes)
    Response Code for Indication of Terminated Dialog (35751 bytes)
    Indication of support for keep-alive (23261 bytes)
    Example call flows using Session Initiation Protocol (SIP) security mechanisms (119797 bytes)
    Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control (48801 bytes)
    Location Conveyance for the Session Initiation Protocol (121613 bytes)
    Session Initiation Protocol (SIP) INFO Method and Package Framework (88296 bytes)

    No Request For Comments

    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.