{"draft":"draft-ietf-sipcore-proxy-feature-12","doc_id":"RFC6809","title":"Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)","authors":["C. Holmberg","I. Sedlacek","H. Kaplan"],"format":["ASCII","HTML"],"page_count":"19","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Session Initiation Protocol Core RAI","abstract":"This specification defines a new SIP header field, Feature-Caps.  The\r\nFeature-Caps header field conveys feature-capability indicators that\r\nare used to indicate support of features and capabilities for SIP\r\nentities that are not represented by the Uniform Resource Identifier\r\n(URI) of the Contact header field.\r\n\r\nSIP entities that are represented by the URI of the SIP Contact\r\nheader field can convey media feature tags in the Contact header\r\nfield to indicate support of features and capabilities.\r\n\r\nThis specification also defines feature-capability indicators and\r\ncreates a new IANA registry, \"Proxy-Feature Feature-Capability\r\nIndicator Trees\", for registering feature-capability indicators.\r\n[STANDARDS-TRACK]","pub_date":"November 2012","keywords":["[--------]","proxy","feature","feature tag","feature-capability indicator","Feature-Caps","capability"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC6809","errata_url":null}