draft-ietf-sipcore-proxy-feature-08.txt   draft-ietf-sipcore-proxy-feature-09.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 26, 2013 H. Kaplan Expires: March 8, 2013 H. Kaplan
Acme Packet Acme Packet
August 25, 2012 September 4, 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-08.txt draft-ietf-sipcore-proxy-feature-09.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 26, 2013. This Internet-Draft will expire on March 8, 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 7, line 36 skipping to change at page 7, line 36
any 18x or 2xx response associated with such requests. any 18x or 2xx response associated with such requests.
If a feature capability indicator is inserted in a Feature-Caps If a feature capability indicator is inserted in a Feature-Caps
header field of an initial request for a dialog, or within a response header field of an initial request for a dialog, or within a response
of such request, it indicates to the receivers of the request (or of such request, it indicates to the receivers of the request (or
response) that the feature associated with the feature capability response) that the feature associated with the feature capability
indicator is supported for the duration of the dialog, until a target indicator is supported for the duration of the dialog, until a target
refresh request is sent for the dialog, or the dialog is terminated. refresh request is sent for the dialog, or the dialog is terminated.
Unless a feature capability indicator is inserted in a Feature-Caps Unless a feature capability indicator is inserted in a Feature-Caps
header field or a target refresh request, or within a response of header field of a target refresh request, or within a response of
such request, it indicates to the receivers of the request (or such request, it indicates to the receivers of the request (or
response) that the feature is no longer supported for the dialog. response) that the feature is no longer supported for the dialog.
For a given dialog a SIP entity MUST insert the same feature For a given dialog a SIP entity MUST insert the same feature
capability indicators in all 18x and 2xx responses associated with a capability indicators in all 18x and 2xx responses associated with a
given transaction. given transaction.
NOTE: As it cannot be guaranteed that 2xx responses associated with NOTE: As it cannot be guaranteed that 2xx responses associated with
SIP SUBSCRIBE requests will reach the UAC, due to forking of the SIP SUBSCRIBE requests will reach the UAC, due to forking of the
request, entities need to indicate supported features and request, entities need to indicate supported features and
skipping to change at page 11, line 48 skipping to change at page 11, line 48
semantics of the values are the same. semantics of the values are the same.
5.3.4. Usage Restrictions 5.3.4. Usage Restrictions
If there are restrictions on how SIP entities can insert a feature If there are restrictions on how SIP entities can insert a feature
capability indicator, the feature capability indicator specification capability indicator, the feature capability indicator specification
MUST document such restrictions. MUST document such restrictions.
There might be restrictions related to whether entities are allowed There might be restrictions related to whether entities are allowed
to insert a feature capability indicator in registration related to insert a feature capability indicator in registration related
messages, standalone transaction messages, or dialog related messages, standalone transaction messages, dialog related messages,
messages, whether entities are allowed to insert a feature capability whether entities are allowed to insert a feature capability indicator
indicator in requests or responses, whether entities also need to in requests or responses, whether entities also need to support other
support other features and capabilities in order to insert a feature features and capabilities in order to insert a feature capability
capability indicator, and whether entities are allowed to indicate indicator, and whether entities are allowed to indicate support of a
support of a feature in conjunction with another feature. feature in conjunction with another feature.
5.3.5. Interoperability Considerations 5.3.5. Interoperability Considerations
If there are specific interoperability considerations that apply to If there are specific interoperability considerations that apply to
the feature capability indicator, the feature capability indicator the feature capability indicator, the feature capability indicator
specification MUST document such considerations. specification MUST document such considerations.
5.3.6. Security Considerations 5.3.6. Security Considerations
If there are specific security considerations that apply to the If there are specific security considerations that apply to the
skipping to change at page 15, line 19 skipping to change at page 15, line 19
The format of the global tree is as described below: The format of the global tree is as described below:
Name Description Reference Name Description Reference
------------------------------ ------------------------------
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, provided in the registration feature capability
feature capability indication registration template. 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
skipping to change at page 16, line 12 skipping to change at page 16, line 12
The format of the SIP tree is as described below: The format of the SIP tree is as described below:
Name Description Reference Name Description Reference
------------------------------ ------------------------------
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, provided in the registration feature capability
feature capability indication registration template. 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
skipping to change at page 18, line 34 skipping to change at page 18, line 34
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-08
o Comments from Atle Mondrad.
Changes from draft-holmberg-sipcore-proxy-feature-06 Changes from draft-holmberg-sipcore-proxy-feature-06
o Editorial changes. 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.
 End of changes. 9 change blocks. 
15 lines changed or deleted 18 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/