draft-ietf-sipcore-proxy-feature-06.txt   draft-ietf-sipcore-proxy-feature-07.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: February 25, 2013 H. Kaplan Expires: February 26, 2013 H. Kaplan
Acme Packet Acme Packet
August 24, 2012 August 25, 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-06.txt draft-ietf-sipcore-proxy-feature-07.txt
Abstract Abstract
This specification defines a new SIP header field, Feature-Caps, to This specification defines a new SIP header field, Feature-Caps, to
convey feature capability indicators, which are used by SIP entities convey feature capability indicators, which are used by SIP entities
not represented by the URI of the Contact header field to indicate not represented by the URI of the Contact header field to indicate
support of features and capabilities, where media feature tags cannot support of features and capabilities, where media feature tags cannot
be used to indicate the support. be used to indicate the support.
This specification also defines feature capability indicators, and This specification also defines feature capability indicators, and
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 February 25, 2013. This Internet-Draft will expire on February 26, 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 37 skipping to change at page 2, line 37
4.3.3. SIP Registration (REGISTER) . . . . . . . . . . . . . 8 4.3.3. SIP Registration (REGISTER) . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . 11
5.3.3. Feature Capability Indicator Values . . . . . . . . . 11 5.3.3. Feature Capability Indicator Values . . . . . . . . . 11
5.3.4. Usage Restrictions . . . . . . . . . . . . . . . . . . 11 5.3.4. Usage Restrictions . . . . . . . . . . . . . . . . . . 11
5.3.5. Interoperability Considerations . . . . . . . . . . . 11 5.3.5. Interoperability Considerations . . . . . . . . . . . 12
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 . 14
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 . . . . . . . . . . . . . . . . . . . . . . . . . 14
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 . . . . . . 17 8. Feature Capability Indicator Registration Template . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 18 11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 18
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
skipping to change at page 6, line 11 skipping to change at page 6, line 11
SIP entity that inserted the feature capability indicator supports SIP entity that inserted the feature capability indicator supports
the features and capabilities associated with the "foo" and "bar" the features and capabilities associated with the "foo" and "bar"
feature capability indicators. feature capability indicators.
4.2.2. B2BUA Behavior 4.2.2. B2BUA Behavior
The procedures in this Section applies to UAs that are part of B2BUAs The procedures in this Section applies to UAs that are part of B2BUAs
that are referenced in the message by a Record-Route header field that are referenced in the message by a Record-Route header field
rather than by the URI of the Contact header field. rather than by the URI of the Contact header field.
When such UA sends a SIP request, if the UA wants to indicate support When such a UA sends a SIP request, if the UA wants to indicate
of features and capabilities towards its downstream SIP entities, it support of features and capabilities towards its downstream SIP
inserts a Feature-Caps header field to the request, containing one or entities, it inserts a Feature-Caps header field to the request,
more feature capability indicators associated with the supported containing one or more feature capability indicators associated with
features and capabilities, before it forwards the request. the supported features and capabilities, before it forwards the
request.
If the SIP request is triggered by another SIP request that the B2BUA If the SIP request is triggered by another SIP request that the B2BUA
has received, the UA MAY forward received Feature-Caps header fields has received, the UA MAY forward received Feature-Caps header fields
by copying them to the outgoing SIP request, similar to a SIP proxy, by copying them to the outgoing SIP request, similar to a SIP proxy,
before it inserts its own Feature-Caps header field to the SIP before it inserts its own Feature-Caps header field to the SIP
request. request.
When such UA receives a SIP response, if the UA wants to indicate When such a UA receives a SIP response, if the UA wants to indicate
support of features and capabilities towards its upstream SIP support of features and capabilities towards its upstream SIP
entities, it inserts a Feature-Caps header field to the response, entities, it inserts a Feature-Caps header field to the response,
containing one or more feature capability indicators associated with containing one or more feature capability indicators associated with
the supported features and capabilities, before it forwards the the supported features and capabilities, before it forwards the
response. response.
If the SIP response is triggered by another SIP response that the If the SIP response is triggered by another SIP response that the
B2BUA has received, the UA MAY forward received Feature-Caps header B2BUA has received, the UA MAY forward received Feature-Caps header
field by copying them to the outgoing SIP response, similar to a SIP field by copying them to the outgoing SIP response, similar to a SIP
proxy, before it inserts its own Feature-Caps header field to the SIP proxy, before it inserts its own Feature-Caps header field to the SIP
skipping to change at page 10, line 6 skipping to change at page 10, line 6
by the IANA after review by a designated expert. That review will by the IANA after review by a designated expert. That review will
serve to ensure that the definition of the feature capability serve to ensure that the definition of the feature capability
indicator meets the technical requirements of this specification. indicator meets the technical requirements of this specification.
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.".
When a feature capability indicator is registered in the sip tree, it
needs to meet the "IETF Consensus" policies defined in RFC 5226. An
RFC, which contains the registration of the feature capability
indicator, MUST be published.
5.3. Feature Capability Indicator Specification Requirements 5.3. Feature Capability Indicator Specification Requirements
5.3.1. General 5.3.1. General
A feature capability indicator specification MUST address the issues A feature capability indicator specification MUST address the issues
defined in the following subsections, or document why an issue is not defined in the following subsections, or document why an issue is not
applicable for the specific feature capability indicator. A applicable for the specific feature capability indicator. A
reference to the specification MUST be provided when the feature reference to the specification MUST be provided when the feature
capability indicator is registered with IANA (see Section 8). capability indicator is registered with IANA (see Section 8).
skipping to change at page 13, line 39 skipping to change at page 13, line 44
7. IANA Considerations 7. IANA Considerations
7.1. Registration of the Feature-Caps header field 7.1. Registration of the Feature-Caps header field
This specification registers a new SIP header field, Feature-Caps, This specification registers a new SIP header field, Feature-Caps,
according to the process of RFC 3261 [RFC3261]. according to the process of RFC 3261 [RFC3261].
The following is the registration for the Feature-Caps header field: The following is the registration for the Feature-Caps header field:
RFC Number: RFC XXXX (IANA: Replace XXXX with the assigned RFC number RFC Number: RFC XXXX
of this specification)
Header Field Name: Feature-Caps Header Field Name: Feature-Caps
7.2. Registration of the Feature-Caps header field parameter 7.2. Registration of the Feature-Caps header field parameter
This specification adds the Feature-Caps header field to the IANA This specification adds the Feature-Caps header field to the IANA
"Header Field Parameters and Parameter Values" registry, according to "Header Field Parameters and Parameter Values" registry, according to
the process of RFC 3968 [RFC3968]. the process of RFC 3968 [RFC3968].
Header Field Parameter Name Predefined Values Reference Predefined
Header Field Parameter Name Values Reference
Feature-Caps +<fcap-name> * No [XXXX] ------------------------------------------------------------------
* <fcap-name> denotes parameter names conforming to the Feature-Caps +<fcap-name> * No [RFC &rfc.number;]
syntax <fcap-name> defined in [xxx]. Valid feature capability
indicators are registered in [IANA: insert reference to the new
Proxy-Feature Feature Capability Indicator Trees registry].
(IANA: Replace XXXX with the assigned RFC number of this * <fcap-name> denotes parameter names conforming to the
specification) syntax <fcap-name> defined in RFC &rfc.number;. Valid
feature capability indicators are registered in [IANA:
insert reference to the new Proxy-Feature Feature
Capability Indicator Trees registry].
Figure 3: SIP Parameter Header Field Figure 3: SIP Parameter Header Field
(IANA: please sort the "Feature-Caps" line into the table and place (IANA: please sort the "Feature-Caps" line into the table and place
the remainder of the above as a footnote to the table.) the remainder of the above as a footnote to the table.)
7.3. Proxy-Feature Feature Capability Indicator Trees 7.3. Proxy-Feature Feature Capability Indicator Trees
7.3.1. Introduction 7.3.1. Introduction
skipping to change at page 14, line 40 skipping to change at page 14, line 45
Feature Feature Capability Indicator Trees". Feature Feature Capability Indicator Trees".
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.
The addition of entries into this tree occurs through the Expert When a feature capability indicator is registered in the global tree,
Review policy, as defined in RFC 5226. A designated area expert will it needs to meet the "Specification Required" policies defined in RFC
review the proposed feature capability indicator, and consult with 5226. A designated area expert will review the proposed feature
members of related mailing lists. The information required in the capability indicator, and consult with members of related mailing
registration is defined in Section 5.3 of RFC XXXX (IANA: Replace lists. The information required in the registration is defined in
XXXX with the assigned RFC number of this specification). Section 5.3 of RFC XXXX.
Note that all feature capability indicators registered in the global Note that all feature capability indicators registered in the global
tree will have names with a leading facet "g.". No leading "+" is tree will have names with a leading facet "g.". 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 global tree is as described below: The format of the global tree is as described below:
Decimal Name Description Reference Name Description Reference
--------------------------------------------------- ------------------------------
Decimal contains an integer value, incremented by IANA every
time a new feature capability indicator is added to the table.
Name contains the Feature Capability Indicator Name, provided Name contains the Feature Capability Indicator Name, provided
in the registration feature capability indication registration in the registration feature capability indication registration
template. template.
Description contains the Abstract, provided in the registration Description contains the Abstract, provided in the registration
feature capability indication registration template. feature capability indication registration template.
Reference contains the Feature Capability Indicator Specification Reference contains the Feature Capability Indicator Specification
Reference, provided in the registration feature capability Reference, provided in the registration feature capability
indication registration template." indication registration template.
Figure 4 Figure 4
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.
The addition of entries into this tree occurs through the IETF When a feature capability indicator is registered in the sip tree, it
Consensus, as defined in RFC 5226. This requires the publication of needs to meet the "IETF Consensus" policies defined in RFC 5226. An
an RFC that contains the registration. The information required in RFC, which contains the registration of the feature capability
the registration is defined in Section 5.3 of RFC XXXX (IANA: Replace indicator, MUST be published. The information required in the
XXXX with the assigned RFC number of this specification). registration is defined in Section 5.3 of 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:
Decimal Name Description Reference Name Description Reference
--------------------------------------------------- ------------------------------
Decimal contains an integer value, incremented by IANA every
time a new feature capability indicator is added to the table.
Name contains the Feature Capability Indicator Name, provided Name contains the Feature Capability Indicator Name, provided
in the registration feature capability indication registration in the registration feature capability indication registration
template. template.
Description contains the Abstract, provided in the registration Description contains the Abstract, provided in the registration
feature capability indication registration template. feature capability indication registration template.
Reference contains the Feature Capability Indicator Specification Reference contains the Feature Capability Indicator Specification
Reference, provided in the registration feature capability Reference, provided in the registration feature capability
indication registration template." indication registration template.
Figure 5 Figure 5
8. Feature Capability Indicator Registration Template 8. Feature Capability Indicator Registration Template
Registration requests for the global tree are submitted Registration requests for the global tree are submitted
by e-mail to iana@iana.org. by e-mail to iana@iana.org.
Registration requests for the sip tree requires submitting Registration requests for the sip tree requires submitting
an Internet-Draft to the IESG. an Internet-Draft to the IESG.
skipping to change at page 17, line 26 skipping to change at page 17, line 26
Description: Description:
| The description should be no longer than 4 lines. More | The description should be no longer than 4 lines. More
| detailed information can be provided in the feature | detailed information can be provided in the feature
| capability indicator specification. | capability indicator specification.
Feature capability indicator name: Feature capability indicator name:
| The referenced specification MUST contain the information | The referenced specification MUST contain the information
| listed in Section 5.3 of XXXX (IANA: Replace XXXX with | listed in Section 5.3 of RFC &rfc.number;.
| the assigned RFC number of this specification).
Feature capability indicator specification reference: Feature capability indicator specification reference:
| The referenced specification MUST contain the information | The referenced specification MUST contain the information
| listed in Section 5.3 of XXXX (IANA: Replace XXXX with | listed in Section 5.3 of RFC &rfc.number;.
| the assigned RFC number of this specification).
Contact: Contact:
| Name(s) & email address(es) of person(s) to | Name(s) & email address(es) of person(s) to
| contact for further information." | contact for further information."
Figure 6: Registration Template Figure 6: Registration Template
9. Security Considerations 9. Security Considerations
skipping to change at page 18, line 33 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-06
o Editorial changes.
Changes from draft-holmberg-sipcore-proxy-feature-05 Changes from draft-holmberg-sipcore-proxy-feature-05
o AD comments from Robert Sparks o AD comments from Robert Sparks
o Additional text added to the Security Considerations section. o Additional text added to the Security Considerations section.
o IANA registration template modified. o IANA registration template modified.
o IANA registration procedures clarified. o IANA registration procedures clarified.
o Feature Capability Indicator specification requirements modified. o Feature Capability Indicator specification requirements modified.
o Note regarding SUBSCRIBE 200 responses added. o Note regarding SUBSCRIBE 200 responses added.
o Editorial modifications. o Editorial modifications.
Changes from draft-holmberg-sipcore-proxy-feature-04 Changes from draft-holmberg-sipcore-proxy-feature-04
 End of changes. 24 change blocks. 
51 lines changed or deleted 57 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/