draft-ietf-sipcore-proxy-feature-10.txt   draft-ietf-sipcore-proxy-feature-11.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft I. Sedlacek Internet-Draft I. Sedlacek
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: March 25, 2013 H. Kaplan Expires: April 1, 2013 H. Kaplan
Acme Packet Acme Packet
September 21, 2012 September 28, 2012
Mechanism to indicate support of features and capabilities in the Mechanism to indicate support of features and capabilities in the
Session Initiation Protocol (SIP) Session Initiation Protocol (SIP)
draft-ietf-sipcore-proxy-feature-10.txt draft-ietf-sipcore-proxy-feature-11.txt
Abstract Abstract
This specification defines a new SIP header field, Feature-Caps. The This specification defines a new SIP header field, Feature-Caps. The
Feature-Caps header field conveys feature capability indicators that Feature-Caps header field conveys feature capability indicators that
are used to indicate support of features and capabilities for SIP are used to indicate support of features and capabilities for SIP
entities that are not represented by the Uniform Resource Identifier entities that are not represented by the Uniform Resource Identifier
(URI) of the Contact header field. (URI) of the Contact header field.
SIP entities that are represented by the URI of the SIP Contact SIP entities that are represented by the URI of the SIP Contact
header field can convey media feature tags in the header field to header field can convey media feature tags in the Contact header
indicate support of features and capabilities. field to indicate support of features and capabilities.
This specification also defines feature capability indicators, and This specification also defines feature capability indicators, and
creates a new IANA registry, "Proxy-Feature Feature Capability creates a new IANA registry, "Proxy-Feature Feature Capability
Indicator Trees", for registering feature capability indicators. Indicator Trees", for registering feature capability indicators.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 25, 2013. This Internet-Draft will expire on April 1, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 42 skipping to change at page 2, line 42
4.3.4. SIP Stand-Alone Transactions . . . . . . . . . . . . . 8 4.3.4. SIP Stand-Alone Transactions . . . . . . . . . . . . . 8
5. Feature Capability Indicators . . . . . . . . . . . . . . . . 9 5. Feature Capability Indicators . . . . . . . . . . . . . . . . 9
5.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Registration Trees . . . . . . . . . . . . . . . . . . . . 9 5.2. Registration Trees . . . . . . . . . . . . . . . . . . . . 9
5.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 9 5.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 9
5.2.2. Global Tree . . . . . . . . . . . . . . . . . . . . . 9 5.2.2. Global Tree . . . . . . . . . . . . . . . . . . . . . 9
5.2.3. SIP Tree . . . . . . . . . . . . . . . . . . . . . . . 10 5.2.3. SIP Tree . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Feature Capability Indicator Specification Requirements . 10 5.3. Feature Capability Indicator Specification Requirements . 10
5.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 10 5.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 10
5.3.2. Overall Description . . . . . . . . . . . . . . . . . 10 5.3.2. Overall Description . . . . . . . . . . . . . . . . . 10
5.3.3. Feature Capability Indicator Values . . . . . . . . . 11 5.3.3. Feature Capability Indicator Values . . . . . . . . . 10
5.3.4. Usage Restrictions . . . . . . . . . . . . . . . . . . 11 5.3.4. Usage Restrictions . . . . . . . . . . . . . . . . . . 11
5.3.5. Interoperability Considerations . . . . . . . . . . . 11 5.3.5. Interoperability Considerations . . . . . . . . . . . 11
5.3.6. Security Considerations . . . . . . . . . . . . . . . 12 5.3.6. Security Considerations . . . . . . . . . . . . . . . 12
5.3.7. Examples . . . . . . . . . . . . . . . . . . . . . . . 12 5.3.7. Examples . . . . . . . . . . . . . . . . . . . . . . . 12
5.3.8. Other Information . . . . . . . . . . . . . . . . . . 12 5.3.8. Other Information . . . . . . . . . . . . . . . . . . 12
6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2. Syntax: Feature-Caps header field . . . . . . . . . . . . 12 6.2. Syntax: Feature-Caps header field . . . . . . . . . . . . 12
6.2.1. ABNF . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.2.1. ABNF . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.3. Syntax: feature capability indicator . . . . . . . . . . . 13 6.3. Syntax: feature capability indicator . . . . . . . . . . . 13
6.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 13 6.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 13
6.3.2. ABNF . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.3.2. ABNF . . . . . . . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7.1. Registration of the Feature-Caps header field . . . . . . 13 7.1. Registration of the Feature-Caps header field . . . . . . 13
7.2. Registration of the Feature-Caps header field parameter . 13 7.2. Registration of the Feature-Caps header field parameter . 13
7.3. Proxy-Feature Feature Capability Indicator Trees . . . . . 14 7.3. Proxy-Feature Feature Capability Indicator Trees . . . . . 14
7.3.1. Introduction . . . . . . . . . . . . . . . . . . . . . 14 7.3.1. Introduction . . . . . . . . . . . . . . . . . . . . . 14
7.3.2. Global Feature Capability Indicator Registration 7.3.2. Global Feature Capability Indicator Registration
Tree . . . . . . . . . . . . . . . . . . . . . . . . . 14 Tree . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.3.3. SIP Feature Capability Indicator Registration Tree . . 15 7.3.3. SIP Feature Capability Indicator Registration Tree . . 15
8. Feature Capability Indicator Registration Template . . . . . . 16 8. Feature Capability Indicator Registration Template . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 18
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
12.1. Normative References . . . . . . . . . . . . . . . . . . . 19 12.1. Normative References . . . . . . . . . . . . . . . . . . . 20
12.2. Informative References . . . . . . . . . . . . . . . . . . 19 12.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [RFC3261] "Caller Preferences" The Session Initiation Protocol (SIP) [RFC3261] "Caller Preferences"
extension, defined in RFC 3840 [RFC3840], provides a mechanism that extension, defined in RFC 3840 [RFC3840], provides a mechanism that
allows a SIP message to convey information relating to the allows a SIP message to convey information relating to the
originator's features and capabilities, using the Contact header originator's features and capabilities, using the Contact header
field. field.
This specification defines a new SIP header field, Feature-Caps. The This specification defines a new SIP header field, Feature-Caps. The
skipping to change at page 4, line 26 skipping to change at page 4, line 26
entities that are not represented by the Uniform Resource Identifier entities that are not represented by the Uniform Resource Identifier
(URI) of the Contact header field. Such cases are: (URI) of the Contact header field. Such cases are:
o - The SIP entity acts as a SIP proxy. o - The SIP entity acts as a SIP proxy.
o - The SIP entity acts as a SIP registrar. o - The SIP entity acts as a SIP registrar.
o - The SIP entity acts as a Back-to-Back User Agent (B2BUA) o - The SIP entity acts as a Back-to-Back User Agent (B2BUA)
[RFC3261], where the Contact header field URI represents another [RFC3261], where the Contact header field URI represents another
SIP entity. SIP entity.
SIP entities that are represented by the URI of the SIP Contact SIP entities that are represented by the URI of the SIP Contact
header field can convey media feature tags in the header field to header field can convey media feature tags in the Contact header
indicate support of features and capabilities. field to indicate support of features and capabilities.
Unlike media feature tags, feature capability indicators are intended Unlike media feature tags, feature capability indicators are intended
to only be used with the SIP protocol. to only be used with the SIP protocol.
This specification also defines feature capability indicators, and This specification also defines feature capability indicators, and
creates a new IANA registry, "Proxy-Feature Feature Capability creates a new IANA registry, "Proxy-Feature Feature Capability
Indicator Trees", for registering feature capability indicators. Indicator Trees", for registering feature capability indicators.
2. Conventions 2. Conventions
skipping to change at page 9, line 50 skipping to change at page 10, line 5
The global feature capability indicator tree is similar to the media The global feature capability indicator tree is similar to the media
feature tag global tree defined in RFC 2506 [RFC2506]. feature tag global tree defined in RFC 2506 [RFC2506].
A feature capability indicator in the global tree will be A feature capability indicator in the global tree will be
distinguished by the leading facet "g.". An organization can propose distinguished by the leading facet "g.". An organization can propose
either a designation indicative of the feature, (e.g., "g.blinktags") either a designation indicative of the feature, (e.g., "g.blinktags")
or a faceted designation including the organization name (e.g., or a faceted designation including the organization name (e.g.,
"g.organization.blinktags"). "g.organization.blinktags").
When a feature capability indicator is registered in the global tree,
it needs to meet the "Specification Required" policies defined in RFC
5226 [RFC5226]. A designated area expert will review the proposed
feature capability indicator, and consult with members of related
mailing lists.
5.2.3. SIP Tree 5.2.3. SIP Tree
The sip feature capability indicator tree is similar to the media The sip feature capability indicator tree is similar to the media
feature tag sip tree defined in RFC 3840. feature tag sip tree defined in RFC 3840.
A feature capability indicator in the sip tree will be distinguished A feature capability indicator in the sip tree will be distinguished
by the leading facet "sip.". by the leading facet "sip.".
5.3. Feature Capability Indicator Specification Requirements 5.3. Feature Capability Indicator Specification Requirements
skipping to change at page 14, line 29 skipping to change at page 14, line 29
7.3. Proxy-Feature Feature Capability Indicator Trees 7.3. Proxy-Feature Feature Capability Indicator Trees
7.3.1. Introduction 7.3.1. Introduction
This specification creates a new sub registry to the IANA "Session This specification creates a new sub registry to the IANA "Session
Initiation Protocol (SIP) Parameters" Protocol Registry, according to Initiation Protocol (SIP) Parameters" Protocol Registry, according to
the process of RFC 5226. The name of the sub registry is "Proxy- the process of RFC 5226. The name of the sub registry is "Proxy-
Feature Feature Capability Indicator Trees". Feature Feature Capability Indicator Trees".
Feature capability indicators are categorized by the "leading facet"
of their name. The leading facet is a prefix of the name consisting
of all characters up to and including the first ".". Feature
capability indicator names that contain no "." characters are
considered to have an empty ("") leading facet.
The "Proxy-Feature Feature Capability Indicator Trees" registry
contains sub registries for subsets (called 'trees') of feature
capability indicators sharing the same leading facet. Each feature
capability indicator is registered within the tree that matches its
leading facet. If no tree matches its leading facet then the feature
capability indicator can not be registered.
New feature capability indicator sub registries (trees) can be
registered. The registration must meet the "Standards Action"
policies defined in RFC 5226. A new name, unique leading facet, and
registration policies (as defined in RFC 5226) for feature capability
indicators within this tree need to be provided.
This document defines the first two feature capability indicator
trees ("g." and "sip."). It does not define a tree for the empty
leading facet.
7.3.2. Global Feature Capability Indicator Registration Tree 7.3.2. Global Feature Capability Indicator Registration Tree
This specification creates a new feature capability indicator tree in This specification creates a new feature capability indicator tree in
the IANA "Proxy-Feature Feature Capability Indicator Trees" registry. the IANA "Proxy-Feature Feature Capability Indicator Trees" registry.
The name of the tree is "Global Feature Capability Indicator The name of the tree is "Global Feature Capability Indicator
Registration Tree", and its leading facet is "g.". It is used for Registration Tree", and its leading facet is "g.". It is used for
the registration of feature capability indicators. the registration of feature capability indicators.
When a feature capability indicator is registered in the global tree, When a feature capability indicator is registered in the global tree,
it needs to meet the "Specification Required" policies defined in RFC it needs to meet the "Specification Required" policies defined in RFC
skipping to change at page 15, line 28 skipping to change at page 15, line 50
7.3.3. SIP Feature Capability Indicator Registration Tree 7.3.3. SIP Feature Capability Indicator Registration Tree
This specification creates a new feature capability indicator tree in This specification creates a new feature capability indicator tree in
the IANA "Proxy-Feature Feature Capability Indicator Trees" registry. the IANA "Proxy-Feature Feature Capability Indicator Trees" registry.
The name of the tree is "SIP Feature Capability Indicator The name of the tree is "SIP Feature Capability Indicator
Registration Tree", and its leading facet is "sip.". It is used for Registration Tree", and its leading facet is "sip.". It is used for
the registration of feature capability indicators. the registration of feature capability indicators.
When a feature capability indicator is registered in the sip tree, it When a feature capability indicator is registered in the sip tree, it
needs to meet the "IETF Consensus" policies defined in RFC 5226. The needs to meet the "IETF Review" policies defined in RFC 5226. The
information required in the registration is defined in Section 5.3 of information required in the registration is defined in Section 5.3 of
RFC XXXX. RFC XXXX.
Note that all feature capability indicators registered in the SIP Note that all feature capability indicators registered in the SIP
tree will have names with a leading facet "sip.". No leading "+" is tree will have names with a leading facet "sip.". No leading "+" is
used in the registrations in any of the feature capability indicator used in the registrations in any of the feature capability indicator
registration trees. registration trees.
The format of the SIP tree is as described below: The format of the SIP tree is as described below:
skipping to change at page 17, line 37 skipping to change at page 18, line 31
10. Acknowledgements 10. Acknowledgements
The authors wish to thank everyone in the SIP community that provided The authors wish to thank everyone in the SIP community that provided
input and feedback on the work of this specification. input and feedback on the work of this specification.
11. Change Log 11. Change Log
[RFC EDITOR NOTE: Please remove this Section when publishing] [RFC EDITOR NOTE: Please remove this Section when publishing]
Changes from draft-holmberg-sipcore-proxy-feature-10
o Editorial changes.
o 'IETF Consensus' changed to 'IETF Review' (section 7.3.3)
Changes from draft-holmberg-sipcore-proxy-feature-09 Changes from draft-holmberg-sipcore-proxy-feature-09
o Editorial changes based on SECDIR comments from Radia Perlman. o Editorial changes based on SECDIR comments from Radia Perlman.
o Editorial changes based on Gen-Art comments from Brian E o Editorial changes based on Gen-Art comments from Brian E
Carpenter. Carpenter.
o Editorial changes based on OPSDIR comments from Jouni Korhonen. o Editorial changes based on OPSDIR comments from Jouni Korhonen.
o Change in security considerations indicating that, if sensitive o Change in security considerations indicating that, if sensitive
information is conveyed, mechanisms for guaranteeing information is conveyed, mechanisms for guaranteeing
confidentiality and authenticity must be provided. confidentiality and authenticity must be provided.
Changes from draft-holmberg-sipcore-proxy-feature-08 Changes from draft-holmberg-sipcore-proxy-feature-08
 End of changes. 13 change blocks. 
24 lines changed or deleted 45 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/