[rfc-dist] RFC 6567 on Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP

[rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org)]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6567

        Title:      Problem Statement and Requirements for 
                    Transporting User-to-User Call Control Information in 
                    SIP 
        Author:     A. Johnston, L. Liess
        Status:     Informational
        Stream:     IETF
        Date:       April 2012
        Mailbox:    alan.b.johnston at gmail.com, 
                    laura.liess.dt at gmail.com
        Pages:      11
        Characters: 25981
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cuss-sip-uui-reqs-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6567.txt

This document introduces the transport of call control User-to-User
Information (UUI) using the Session Initiation Protocol (SIP) and
develops several requirements for a new SIP mechanism.  Some SIP
sessions are established by or related to a non-SIP application.
This application may have information that needs to be transported
between the SIP User Agents during session establishment.  In
addition to interworking with the Integrated Services Digital Network
(ISDN) UUI Service, this extension will also be used for native SIP
endpoints requiring application UUI.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

This document is a product of the Call Control UUI Service for SIP Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC