Mechanism to indicate support of features and capabilities in the Session Initiation Protocol (SIP)
draft-ietf-sipcore-proxy-feature-11

The information below is for an old version of the document
Document Type Active Internet-Draft (sipcore WG)
Last updated 2012-10-16 (latest revision 2012-09-28)
Replaces draft-holmberg-sipcore-proxy-feature
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document Dec 2012
Consensus Unknown
Document shepherd None
IESG IESG state RFC Ed Queue
Telechat date
Responsible AD Robert Sparks
IESG note Paul Kyzivat (pkyzivat@alum.mit.edu) is the Document Shepherd
Send notices to sipcore-chairs@tools.ietf.org, draft-ietf-sipcore-proxy-feature@tools.ietf.org
RFC Editor RFC Editor state AUTH
SIPCORE Working Group                                        C. Holmberg
Internet-Draft                                               I. Sedlacek
Intended status: Standards Track                                Ericsson
Expires: April 1, 2013                                         H. Kaplan
                                                             Acme Packet
                                                      September 28, 2012

   Mechanism to indicate support of features and capabilities in the
                   Session Initiation Protocol (SIP)
                draft-ietf-sipcore-proxy-feature-11.txt

Abstract

   This specification defines a new SIP header field, Feature-Caps.  The
   Feature-Caps header field conveys feature capability indicators that
   are used to indicate support of features and capabilities for SIP
   entities that are not represented by the Uniform Resource Identifier
   (URI) of the Contact header field.

   SIP entities that are represented by the URI of the SIP Contact
   header field can convey media feature tags in the Contact header
   field to indicate support of features and capabilities.

   This specification also defines feature capability indicators, and
   creates a new IANA registry, "Proxy-Feature Feature Capability
   Indicator Trees", for registering feature capability indicators.

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 April 1, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Holmberg, et al.          Expires April 1, 2013                 [Page 1]
Internet-Draft                proxy feature               September 2012

   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (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.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Feature-Caps Header Field  . . . . . . . . . . . . . . . . . .  5
     4.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . .  5
     4.2.  User Agent and Proxy Behavior  . . . . . . . . . . . . . .  5
       4.2.1.  General  . . . . . . . . . . . . . . . . . . . . . . .  5
       4.2.2.  B2BUA Behavior . . . . . . . . . . . . . . . . . . . .  6
       4.2.3.  Registrar Behavior . . . . . . . . . . . . . . . . . .  6
       4.2.4.  Proxy behavior . . . . . . . . . . . . . . . . . . . .  6
     4.3.  SIP Message Type and Response Code Semantics . . . . . . .  7
       4.3.1.  General  . . . . . . . . . . . . . . . . . . . . . . .  7
       4.3.2.  SIP Dialog . . . . . . . . . . . . . . . . . . . . . .  7
       4.3.3.  SIP Registration (REGISTER)  . . . . . . . . . . . . .  8
       4.3.4.  SIP Stand-Alone Transactions . . . . . . . . . . . . .  8
   5.  Feature Capability Indicators  . . . . . . . . . . . . . . . .  9
     5.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . .  9
     5.2.  Registration Trees . . . . . . . . . . . . . . . . . . . .  9
       5.2.1.  General  . . . . . . . . . . . . . . . . . . . . . . .  9
       5.2.2.  Global Tree  . . . . . . . . . . . . . . . . . . . . .  9
       5.2.3.  SIP Tree . . . . . . . . . . . . . . . . . . . . . . . 10
     5.3.  Feature Capability Indicator Specification Requirements  . 10
       5.3.1.  General  . . . . . . . . . . . . . . . . . . . . . . . 10
       5.3.2.  Overall Description  . . . . . . . . . . . . . . . . . 10
       5.3.3.  Feature Capability Indicator Values  . . . . . . . . . 10
       5.3.4.  Usage Restrictions . . . . . . . . . . . . . . . . . . 11
Show full document text