Media Feature Tags Prefix: iso.org.dod.internet.features (1.3.6.1.8) (last updated 2008-09-29) Registries included below: Prefix: iso.org.dod.internet.features.ietf-tree (1.3.6.1.8.1) Prefix: iso.org.dod.internet.features.global-tree (1.3.6.1.8.2) Prefix: iso.org.dod.internet.features.uri-tree (1.3.6.1.8.3) Prefix: iso.org.dod.internet.features.sip-tree (1.3.6.1.8.4) Prefix: iso.org.dod.internet.features.ietf-tree (1.3.6.1.8.1) Reference: [RFC2506] Registration Procedures: IETF Consensus Registry: Decimal Name Description Reference ------- ------------------------------ ------------------------------ --------- 1 pix-x horizontal pixels [RFC2534] 2 pix-y vertical pixels [RFC2534] 3 dpi dots-per-inch [RFC2534] 4 ua-media ua-media [RFC2534] 5 paper-size paper-size [RFC2534] 6 color color [RFC2534] 7 size-x size-x [RFC2531] 8 size-y size-y [RFC2531] 9 dpi-xyratio dpi-xyratio [RFC2531] 10 color-levels color-levels [RFC2531] 11 color-space color-space [RFC2531] 12 CIELAB-L-depth CIELAB-L-depth [RFC2531] 13 CIELAB-A-depth CIELAB-A-depth [RFC2531] 14 CIELAB-B-depth CIELAB-B-depth [RFC2531] 15 CIELAB-L-min CIELAB-L-min [RFC2531] 16 CIELAB-L-max CIELAB-L-max [RFC2531] 17 CIELAB-a-min CIELAB-a-min [RFC2531] 18 CIELAB-a-max CIELAB-a-max [RFC2531] 19 CIELAB-b-min CIELAB-b-min [RFC2531] 20 CIELAB-b-max CIELAB-b-max [RFC2531] 21 image-file-structure image-file-structure [RFC2531] 22 image-coding image-coding [RFC2531] 23 image-coding-constraint image-coding-constraint [RFC2531] 24 JBIG-stripe-size JBIG-stripe-size [RFC2531] 25 image-interleave image-interleave [RFC2531] 26 color-subsampling color-subsampling [RFC2531] 27 MRC-mode MRC-mode [RFC2531] 28 MRC-max-stripe-size MRC-max-stripe-size [RFC2531] 29 color-illuminant color-illuminant [RFC2879] 30 type type [RFC2913] 31 charset charset [RFC2987] 32 language language [RFC2987] 33 unknown-character-replacement unknown-character-replacement [RFC-ietf-lemonade-convert-20.txt] Prefix: iso.org.dod.internet.features.global-tree (1.3.6.1.8.2) Reference: [RFC2506] Registration Procedures: Expert Review Registry: Decimal Name Description References ------- ---------------- ------------------------------------- --------------------------- 1 g.3gpp.cs-voice This feature-tag indicates that [Meredith][ETSI TS 124 279] the device supports circuit switched voice when combining circuit switched calls and IM sessions. 2 g.3gpp.cs-video This feature-tag indicates that [Meredith][ETSI TS 124 279] the device supports circuit switched video when combining circuit switched video calls and IM sessions. 3 g.3gpp.smsip This feature-tag indicates that [Meredith][ETSI TS 124 341] the device is capable of accepting SMS messages via SIP as specified by ETSI TS 124 341. Prefix: iso.org.dod.internet.features.uri-tree (1.3.6.1.8.3) Reference: [RFC2506] Registration Procedures: Unregistered (formed from uri) Registry: Decimal Name Description Reference ------- ---- --------------- ---------- There are no registrations at this time Prefix: iso.org.dod.internet.features.sip-tree (1.3.6.1.8.4) Reference: [RFC3840] Registration Procedures: IETF Consensus Registry: Decimal Name Description Reference ------- --------------- ---------------------------------------------- --------- 1 sip.audio This feature tag indicates that [RFC3840] the device supports audio as a streaming media type. 2 sip.application This feature tag indicates that [RFC3840] the device supports application as a streaming media type. This feature tag exists primarily for completeness. Since so many MIME types are underneath application, indicating the ability to support applications provides little useful information. 3 sip.data This feature tag indicates that [RFC3840] the device supports data as a streaming media type. 4 sip.control This feature tag indicates that [RFC3840] the device supports control as a streaming media type. 5 sip.video This feature tag indicates that [RFC3840] the device supports video as a streaming media type. 6 sip.text This feature tag indicates that [RFC3840] the device supports text as a streaming media type. 7 sip.automata The sip.automata feature tag is a [RFC3840] boolean value that indicates whether the UA represents an automata (such as a voicemail server, conference server, IVR, or recording device) or a human. 8 sip.class This feature tag indicates the [RFC3840] setting, business or personal, in which a communications device is used. 9 sip.duplex The sip.duplex media feature tag [RFC3840] indicates whether a communications device can simultaneously send and receive media ("full"), alternate between sending and receiving ("half"), can only receive ("receive-only") or only send ("send-only"). 10 sip.mobility The sip.mobility feature tag [RFC3840] indicates whether the device is fixed (meaning that it is associated with a fixed point of contact with the network), or mobile (meaning that it is not associated with a fixed point of contact). Note that cordless phones are fixed, not mobile, based on this definition. 11 sip.description The sip.description feature tag [RFC3840] provides a textual description of the device. 12 sip.events Each feature tag value indicates [RFC3840] a SIP event package supported by a SIP UA. The values for this tag equal the event package names that are registered by each event package. 13 sip.priority The sip.priority feature tag [RFC3840] indicates the call priorities the device is willing to handle. A value of X means that the device is willing to take requests with priority X and higher. This does not imply that a phone has to reject calls of lower priority. As always, the decision on handling of such calls is a matter of local policy. 14 sip.methods Each value of the sip.methods [RFC3840] (note the plurality) feature tag indicates a SIP method supported by this UA. In this case, "supported" means that the UA can receive requests with this method. In that sense, it has the same connotation as the Allow header field. 15 sip.extensions Each value of the sip.extensions [RFC3840] feature tag is a SIP extension (each of which is defined by an option-tag registered with IANA) that is understood by the UA. Understood, in this context, means that the option tag would be included in a Supported header field in a request. 16 sip.schemes Each value of the sip.schemes (note [RFC3840] the plurality) media feature tag indicates a URI scheme that is supported by a UA. Supported implies, for example, that the UA would know how to handle a URI of that scheme in the Contact header field of a redirect response. 17 sip.actor This feature tag indicates the type [RFC3840] of entity that is available at this URI. 18 sip.isfocus This feature tag indicates that the [RFC3840] UA is a conference server, also known as a focus, and will mix together the media for all calls to the same URI. 19 sip.byeless The feature tag is a boolean flag. [RFC4235] When set it indicates that the device is incapable of terminating a session autonomously. 20 sip.rendering This feature tag contains one of three [RFC4235] tokens indicating if the device is rendering any media from the current session ("yes"), none of the media from the current session ("no"), or if this status is not known to the device ("unknown"). 21 sip.message This feature tag indicates that the device [RFC4569] supports message as a streaming media type. 22 sip.ice This feature tag indicates that the device [RFC-ietf-sip-ice-option-tag-02.txt] supports Interactive Connectivity Establishment (ICE). References ---------- [ETSI TS 124 279] http://www.etsi.org/services_products/freestandard/home.htm [ETSI TS 124 341] http://www.etsi.org/services_products/freestandard/home.htm [RFC2506] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag Registration Procedure", BCP 31, RFC 2506, March 1999. [RFC2531] Klyne, G., and L. McIntyre, "Content Feature Schema for Internet Fax", RFC 2531, March 1999. [RFC2534] Masinter, L., Holtman, K., Mutz, A., and D. Wing, "Media Features for Display, Print, and Fax", RFC 2534, March 1999. [RFC2879] Klyne, G. and L. McIntyre, "Content Feature Schema for Internet Fax (V2)", RFC 2879, August 2000. [RFC2913] Klyne, G., "MIME Content Types in Media Feature Expressions", RFC 2913, September 2000. [RFC2987] Hoffman, P., "Registration of Charset and Languages Media Features Tags", RFC 2987, November 2000. [RFC3840] J. Rosenberg, H. Schulzrinne, and P. Kyzivat, "Indicating User Agent Capabilities in the Session Initiation Protocol", RFC 3840, August 2004. [RFC4235] J. Rosenberg, H. Schulzrinne, and R. Mahy, Ed., "An INVITE Inititiated Dialog Event Package for the Session Initiation Protocol (SIP)", RFC 4235, November 2005. [RFC4569] G. Camarillo, "Internet Assigned Numbers Authority (IANA) Registration of the Message Media Feature Tag", RFC 4569, July 2006. [RFC-ietf-lemonade-convert-20.txt] A. Melnikov, Ed., P. Coates, Ed., "IMAP CONVERT extension", RFC XXXX, Month Year. [RFC-ietf-sip-ice-option-tag-02.txt] J. Rosenberg, "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)", RFC XXXX, Month Year. People ------ [Meredith] John M Meredith, , 2007-04-20, 2007-08-29. []