draft-ietf-sipcore-proxy-feature-07.txt   draft-ietf-sipcore-proxy-feature-08.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: February 26, 2013 H. Kaplan
Acme Packet Acme Packet
August 25, 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-07.txt draft-ietf-sipcore-proxy-feature-08.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 14, line 15 skipping to change at page 14, line 15
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].
Predefined Predefined
Header Field Parameter Name Values Reference Header Field Parameter Name Values Reference
------------------------------------------------------------------ ------------------------------------------------------------------
Feature-Caps +<fcap-name> * No [RFC &rfc.number;] Feature-Caps +<fcap-name> * No [RFC XXXX]
* <fcap-name> denotes parameter names conforming to the * <fcap-name> denotes parameter names conforming to the
syntax <fcap-name> defined in RFC &rfc.number;. Valid syntax <fcap-name> defined in RFC XXXX. Valid
feature capability indicators are registered in [IANA: feature capability indicators are registered in [IANA:
insert reference to the new Proxy-Feature Feature insert reference to the new Proxy-Feature Feature
Capability Indicator Trees registry]. 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
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 RFC &rfc.number;. | listed in Section 5.3 of RFC XXXX.
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 RFC &rfc.number;. | listed in Section 5.3 of RFC XXXX.
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."
(IANA: Please replace XXXX with the assigned RFC number)
Figure 6: Registration Template Figure 6: Registration Template
9. Security Considerations 9. Security Considerations
The security issues for feature capability indicators are similar to The security issues for feature capability indicators are similar to
the ones defined in RFC 3840 for media feature tags. Media feature the ones defined in RFC 3840 for media feature tags. Media feature
tags can reveal information about end-users and end-user equipment, tags can reveal information about end-users and end-user equipment,
which can be used for industrial espionage. The knowledge about end- which can be used for industrial espionage. The knowledge about end-
user equipment capabilities can also be used to influence application user equipment capabilities can also be used to influence application
behavior. As feature capability indicators are not intended to behavior. As feature capability indicators are not intended to
 End of changes. 6 change blocks. 
5 lines changed or deleted 7 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/