A Mechanism for Transporting User to User Call Control Information in SIP
draft-ietf-cuss-sip-uui-12

The information below is for an old version of the document
Document Type Active Internet-Draft (cuss WG)
Last updated 2014-01-27
Replaces draft-johnston-cuss-sip-uui
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Vijay Gurbani
Shepherd write-up Show (last changed 2012-09-24)
IESG IESG state Waiting for AD Go-Ahead::External Party
Telechat date
Responsible AD Gonzalo Camarillo
Send notices to cuss-chairs@tools.ietf.org, draft-ietf-cuss-sip-uui@tools.ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                        A. Johnston
Internet-Draft                                                     Avaya
Intended status: Standards Track                             J. Rafferty
Expires: July 29, 2014                              Human Communications
                                                        January 25, 2014

 A Mechanism for Transporting User to User Call Control Information in
                                  SIP
                       draft-ietf-cuss-sip-uui-12

Abstract

   There is a class of applications which benefit from using SIP to
   exchange User to User Information (UUI) data during session
   establishment.  This information, known as call control UUI data, is
   a small piece of data inserted by an application initiating the
   session, and utilized by an application accepting the session.  The
   rules which apply for a specific application are defined by a UUI
   package.  This UUI data is opaque to SIP and its function is
   unrelated to any basic SIP function.  This document defines a new SIP
   header field, User-to-User, to transport UUI data, along with an
   extension mechanism.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 29, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Johnston & Rafferty       Expires July 29, 2014                 [Page 1]
Internet-Draft               SIP UUI for CC                 January 2014

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Requirements Discussion  . . . . . . . . . . . . . . . . . . .  3
   4.  Normative Definition . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  Syntax for UUI Header Field  . . . . . . . . . . . . . . .  5
     4.2.  Hex Encoding Definition  . . . . . . . . . . . . . . . . .  7
     4.3.  Source Identity of UUI data  . . . . . . . . . . . . . . .  7
   5.  Guidelines for UUI Packages  . . . . . . . . . . . . . . . . .  9
     5.1.  Extensibility  . . . . . . . . . . . . . . . . . . . . . . 10
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
     6.1.  Registration of User-to-User Header Field  . . . . . . . . 11
     6.2.  Registration of User-to-User Header Field Parameters . . . 11
     6.3.  Registration of UUI Packages . . . . . . . . . . . . . . . 11
     6.4.  Registration of UUI Content Parameters . . . . . . . . . . 12
     6.5.  Registration of UUI Encoding Parameters  . . . . . . . . . 12
     6.6.  Registration of SIP Option Tag . . . . . . . . . . . . . . 13
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   8.  Appendix - Other Possible Mechanisms . . . . . . . . . . . . . 14
     8.1.  Why INFO is Not Used . . . . . . . . . . . . . . . . . . . 14
     8.2.  Why Other Protocol Encapsulation UUI Mechanisms are
           Not Used . . . . . . . . . . . . . . . . . . . . . . . . . 14
     8.3.  MIME body Approach . . . . . . . . . . . . . . . . . . . . 15
     8.4.  URI Parameter  . . . . . . . . . . . . . . . . . . . . . . 16
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     10.1. Informative References . . . . . . . . . . . . . . . . . . 17
     10.2. Normative References . . . . . . . . . . . . . . . . . . . 18
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18

Johnston & Rafferty       Expires July 29, 2014                 [Page 2]
Show full document text