Internet Assigned Numbers Authority Media Feature Tags - iso.org.dod.internet.features (1.3.6.1.8) Last Updated 2023-03-13 Available Formats [IMG] XML [IMG] HTML [IMG] Plain text Registries included below • iso.org.dod.internet.features.ietf-tree (1.3.6.1.8.1) • iso.org.dod.internet.features.global-tree (1.3.6.1.8.2) • iso.org.dod.internet.features.uri-tree (1.3.6.1.8.3) • iso.org.dod.internet.features.sip-tree (1.3.6.1.8.4) iso.org.dod.internet.features.ietf-tree (1.3.6.1.8.1) Registration Procedure(s) IETF Review Reference [RFC2506][RFC2534] Available Formats [IMG] CSV 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 [RFC2879] 8 size-y size-y [RFC2879] 9 dpi-xyratio dpi-xyratio [RFC2879] 10 color-levels color-levels [RFC2879] 11 color-space color-space [RFC2879] 12 CIELAB-L-depth CIELAB-L-depth [RFC2879] 13 CIELAB-A-depth CIELAB-A-depth [RFC2879] 14 CIELAB-B-depth CIELAB-B-depth [RFC2879] 15 CIELAB-L-min CIELAB-L-min [RFC2879] 16 CIELAB-L-max CIELAB-L-max [RFC2879] 17 CIELAB-a-min CIELAB-a-min [RFC2879] 18 CIELAB-a-max CIELAB-a-max [RFC2879] 19 CIELAB-b-min CIELAB-b-min [RFC2879] 20 CIELAB-b-max CIELAB-b-max [RFC2879] 21 image-file-structure image-file-structure [RFC2879] 22 image-coding image-coding [RFC2879] 23 image-coding-constraint image-coding-constraint [RFC2879] 24 JBIG-stripe-size JBIG-stripe-size [RFC2879] 25 image-interleave image-interleave [RFC2879] 26 color-subsampling color-subsampling [RFC2879] 27 MRC-mode MRC-mode [RFC2879] 28 MRC-max-stripe-size MRC-max-stripe-size [RFC2879] 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 [RFC5259] iso.org.dod.internet.features.global-tree (1.3.6.1.8.2) Registration Procedure(s) Expert Review Expert(s) Paul Kyzivat Reference [RFC2506] Available Formats [IMG] CSV Decimal Name Description Reference This feature-tag indicates that the device supports circuit 1 g.3gpp.cs-voice switched voice when combining circuit switched calls and IM [ETSI TS 124 279][John_M_Meredith] sessions. This feature-tag indicates that the device supports circuit 2 g.3gpp.cs-video switched video when combining circuit switched video calls and [ETSI TS 124 279][John_M_Meredith] IM sessions. 3 g.3gpp.smsip This feature-tag indicates that the device is capable of [ETSI TS 124 341][John_M_Meredith] accepting SMS messages via SIP as specified by ETSI TS 124 341. Each value of the Service Reference media feature-tag indicates the software applications supported by the agent. The values for this tag equal the IMS communication Service Identifier (ICSI) values supported by the agent. The Service Reference 4 g.3gpp.icsi-ref media feature tag is defined to fulfil the requirements for [3GPP TS 24.229][Frederic_Firmin] forking to an appropriate UE when multiple UEs are registered and dispatch to an appropriate application within the UE based upon the IMS communication Service Identifier (ICSI) values as stated in 3GPP TS 23.228. Each value of the Application Reference media feature-tag indicates the software applications supported by the agent. The values for this tag equal IMS Application Reference Identifier (IARI) values supported by the agent The Application Reference 5 g.3gpp.iari-ref media feature tag is defined to fulfil the requirements for [3GPP TS 24.229][Frederic_Firmin] forking to an appropriate UE when multiple UEs are registered and dispatch to an appropriate application within the UE based upon and IMS Application Reference Identifier (IARI) values as stated in 3GPP TS 23.228. This feature-tag when used in a SIP REGISTER request indicates 6 g.3gpp.ics that the function is ICS capability and may operate in ICS [3GPP TS 24.292][Frederic_Firmin] mode. This feature-tag when used is a none SIP REGISTER method indicates that the function wants to invoke ICS functionality. This feature-tag when used in a SIP REGISTER request indicates 7 g.3gpp.accesstype access network technology used by the device and the particular [3GPP TS 24.292][Frederic_Firmin] registration flow that the device is using to register over. 8 g.3gpp.pne-id This media feature-tag when used in a SIP request or a SIP [3GPP TS 24.259][Frederic_Firmin] response indicates the identifier of a PNE other than a UE. This media feature-tag when used in a SIP request or a SIP response indicates that the function sending the SIP message 9 g.3gpp.iut-controller supports the IUT Controller functionality.This media feature [3GPP TS 24.337][Frederic_Firmin] tag does not imply that the controller UE capabilities are handled in the same protocol manner. This media feature-tag when used in a Contact header field or a Accept-Contact header field of a SIP request or a SIP response 10 g.3gpp.iut-focus indicates that the function sending the SIP message supports [3GPP TS 24.337][Frederic_Firmin] anchoring a IUT session and/or the SIP message is an inter-UE transfer operation. This media feature-tag when used in a Contact header field of SIP request or SIP response indicates that the UA is the 11 g.3gpp.current-iut-controller currently active IUT controller for the collaborative session [3GPP TS 24.337][Frederic_Firmin] or is a controllee in the collaborative. The values of the feature tag are "active" and "passive". This feature-tag when used in a SIP request or a SIP response 12 g.3gpp.mid-call indicates that the function sending the SIP message supports [3GPP TS 24.237][Frederic_Firmin] the MSC server assisted mid-call feature. This media feature-tag when used in a Contact header field of a 13 g.3gpp.srvcc-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237][Frederic_Firmin] entity sending the SIP message supports SRVCC access transfer for calls in alerting phase, i.e. for calls whith early dialog. This media feature-tag when used in a Contact header field of a 14 g.3gpp.cs2ps-srvcc-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports CS to PS SRVCC access 11.10.0][Frederic_Firmin] transfer for calls in alerting phase. This media feature tag when used in a Contact header field in 15 g.3gpp.path SIP REGISTER request or SIP response to the SIP REGISTER [3GPP TS 24.237 request indicates capability of identifying the registration 11.10.0][Frederic_Firmin] path and binding SRVCC related information to it. This media feature tag when included in Contact header field [3GPP TS 24.237 16 g.3gpp.cs2ps-srvcc indicates support of the CS to PS single radio voice call 11.10.0][Frederic_Firmin] continuity as specified in 3GPP TS 24.237. This media feature-tag when used in a Contact header field of a 17 g.3gpp.pstops-sti SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the use of the PS to PS 11.10.0][Frederic_Firmin] STI URI. This media feature tag when used in a Contact header field as specified in IETF RFC 3840 in SIP INVITE request or SIP [3GPP TS 24.237 18 g.3gpp.ti response to the SIP INVITE request indicates the capability of 11.10.0][Frederic_Firmin] associating a CS call with dialog created by the SIP INVITE request. This media feature-tag when used in a Contact header field of a 19 g.3gpp.drvcc-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the PS to CS dual radio 12.8.0][Frederic_Firmin] access transfer for calls in alerting phase. This media feature-tag when used in a Contact header field of a [3GPP TS 24.237 20 g.3gpp.dynamic-stn SIP request or a SIP response indicates that the functional 12.8.0][Frederic_Firmin] entity sending the SIP message supports the use of dynamic STN. This media feature-tag when used in a Contact header field of a 21 g.3gpp.ps2cs-drvcc-orig-pre-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the PS to CS dual radio 12.8.0][Frederic_Firmin] access transfer for originating calls in pre-alerting phase. This media feature tag when used in a Contact header field of a 22 g.3gpp.ps2cs-srvcc-orig-pre-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the PS to CS SRVCC for 12.8.0][Frederic_Firmin] originating calls in pre-alerting phase. This media feature-tag, when used in a Contact header field of 23 g.3gpp.cs2ps-drvcc-alerting a SIP request or a SIP response, indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the CS to PS dual radio v12.9.0][Frederic_Firmin] access transfer for calls in alerting phase. This media feature-tag when used in a Contact header field of a 24 g.3gpp.cs2ps-drvcc-orig-pre-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237 entity sending the SIP message supports the CS to PS dual radio v12.9.0][Frederic_Firmin] access transfer for originating calls in pre-alerting phase. This media feature-tag when used in a Contact header field of a 25 g.3gpp.smsip-msisdn-less SIP request or a SIP response indicates that the functional [3GPP TS 24.341 entity sending the SIP message supports MSISDN less operation v12.6.0][Frederic_Firmin] of SMS via SIP MESSAGE request. 26 g.3gpp.nw-init-ussi This feature-tag indicates support of user equipment procedures [3GPP TS 24.390 for the network initiated USSD over IMS. v12.6.0][Frederic_Firmin] This media feature tag, when included in a third party SIP REGISTER request, indicates the support of using a token to identify the registration used for the request. The [3GPP TS 24.229 27 g.3gpp.registration-token mediafeature tag is assigned a value that can be used by the v12.16.0][Frederic_Firmin] receiving AS to later identify the used registration for initial requests from an originating user or dialog forming responses from a terminating user. This media feature tag when used in a SIP request or a SIP [3GPP TS 24.379 28 g.3gpp.mcptt response indicates that the function sending the SIP message v13.5.0][Frederic_Firmin] supports Mission Critical Push To Talk (MCPTT) communication. This media feature tag when used in a SIP request or a SIP 29 g.3gpp.mcdata.sds response indicates that the function sending the SIP message [3GPP TS 24.282 supports Mission Critical Data (MCData) communications Short 14.3.0][Frederic_Firmin] Data Service (SDS). This media feature tag when used in a SIP request or a SIP 30 g.3gpp.mcdata.fd response indicates that the function sending the SIP message [3GPP TS 24.282 supports Mission Critical Data (MCData) communications File 14.3.0][Frederic_Firmin] Distribution (FD). This media feature tag when used in a SIP request or a SIP [3GPP TS 24.281 31 g.3gpp.mcvideo response indicates that the function sending the SIP message Rel-14][Frederic_Firmin] supports Mission Critical Video (MCVideo) communication. This media feature-tag when used in a Contact header field of a 32 g.3gpp.dynamic-e-stn-drvcc SIP request or a SIP response indicates that the functional [3GPP TS 24.237][Frederic_Firmin] entity sending the SIP message supports the use of dynamic-e-stn-drvcc. This media feature-tag, when used in a Contact header field of a SIP request or a SIP response, indicates that the functional entity sending the SIP message supports the PS to CS SRVCC for 33 g.3gpp.ps2cs-srvcc-mid-call-emergency emergency session in early dialog state with active speech [3GPP TS 24.237][Frederic_Firmin] media component when both the emergency session in early dialog state with active speech media component and a non-emergency call in confirmed dialog state with inactive speech media component exists. This media feature tag when used in a Contact header field of a 34 g.3gpp.ps2cs-srvcc-term-pre-alerting SIP request or a SIP response indicates that the functional [3GPP TS 24.237][Frederic_Firmin] entity sending the SIP message supports the PS to CS SRVCC for terminating calls in pre-alerting phase. This media feature tag when included in a Contact header field in a REGISTER request indicates the status of the 3GPP PS data off for the registration time. This media feature tag, when 35 g.3gpp.ps-data-off included in the Contact header field in a REGISTER request [3GPP TS 24.229][Frederic_Firmin] indicates that the UE supports the 3GPP PS data off. The g.3gpp.ps-data-off media feature tag can take a value that indicates whether the 3GPP PS data off has been activated or deactivated by the user at the UE. This media feature tag when used in a SIP request or a SIP 36 g.3gpp.mcdata.ipconn response indicates that the function sending the SIP message [3GPP TS 24.282][Kiran_Kapale] supports Mission Critical Data (MCData) communications IP Connectivity (IPCONN). This feature-tag when used in a SIP REGISTER request indicates 37 g.3gpp.rlos that the function sending the SIP message supports restricted [3GPP TS 24.229] local operator service. iso.org.dod.internet.features.uri-tree (1.3.6.1.8.3) Registration Procedure(s) Unregistered (formed from uri) Reference [RFC2506] Decimal Name Description Reference No registrations at this time. iso.org.dod.internet.features.sip-tree (1.3.6.1.8.4) Registration Procedure(s) IETF Review Reference [RFC3840] Available Formats [IMG] CSV Decimal Name Description Reference 1 sip.audio This feature tag indicates that the device supports audio as a streaming media type. [RFC3840] This feature tag indicates that the device supports application as a streaming media type. This feature tag 2 sip.application exists primarily for completeness. Since so many MIME types are underneath application, indicating the ability [RFC3840] to support applications provides little useful information. 3 sip.data This feature tag indicates that the device supports data as a streaming media type. [RFC3840] 4 sip.control This feature tag indicates that the device supports control as a streaming media type. [RFC3840] 5 sip.video This feature tag indicates that the device supports video as a streaming media type. [RFC3840] 6 sip.text This feature tag indicates that the device supports text as a streaming media type. [RFC3840] 7 sip.automata The sip.automata feature tag is a boolean value that indicates whether the UA represents an automata (such as [RFC3840] a voicemail server, conference server, IVR, or recording device) or a human. 8 sip.class This feature tag indicates the setting, business or personal, in which a communications device is used. [RFC3840] The sip.duplex media feature tag indicates whether a communications device can simultaneously send and receive 9 sip.duplex media ("full"), alternate between sending and receiving ("half"), can only receive ("receive-only") or only [RFC3840] send ("send-only"). The sip.mobility feature tag indicates whether the device is fixed (meaning that it is associated with a fixed 10 sip.mobility point of contact with the network), or mobile (meaning that it is not associated with a fixed point of [RFC3840] contact). Note that cordless phones are fixed, not mobile, based on this definition. 11 sip.description The sip.description feature tag provides a textual description of the device. [RFC3840] 12 sip.events Each feature tag value indicates a SIP event package supported by a SIP UA. The values for this tag equal the [RFC3840] event package names that are registered by each event package. The sip.priority feature tag indicates the call priorities the device is willing to handle. A value of X means 13 sip.priority that the device is willing to take requests with priority X and higher. This does not imply that a phone has [RFC3840] to reject calls of lower priority. As always, the decision on handling of such calls is a matter of local policy. Each value of the sip.methods (note the plurality) feature tag indicates a SIP method supported by this UA. In 14 sip.methods this case, "supported" means that the UA can receive requests with this method. In that sense, it has the same [RFC3840] connotation as the Allow header field. Each value of the sip.extensions feature tag is a SIP extension (each of which is defined by an option-tag 15 sip.extensions registered with IANA) that is understood by the UA. Understood, in this context, means that the option tag [RFC3840] would be included in a Supported header field in a request. Each value of the sip.schemes (note the plurality) media feature tag indicates a URI scheme that is supported 16 sip.schemes by a UA. Supported implies, for example, that the UA would know how to handle a URI of that scheme in the [RFC3840] Contact header field of a redirect response. 17 sip.actor This feature tag indicates the type of entity that is available at this URI. [RFC3840] 18 sip.isfocus This feature tag indicates that the UA is a conference server, also known as a focus, and will mix together [RFC3840] the media for all calls to the same URI. 19 sip.byeless The feature tag is a boolean flag. When set it indicates that the device is incapable of terminating a session [RFC4235] autonomously. This feature tag contains one of three tokens indicating if the device is rendering any media from the current 20 sip.rendering session ("yes"), none of the media from the current session ("no"), or if this status is not known to the [RFC4235] device ("unknown"). 21 sip.message This feature tag indicates that the device supports message as a streaming media type. [RFC4569] 22 sip.ice This feature tag indicates that the device supports Interactive Connectivity Establishment (ICE). [RFC5768] This feature tag contains a string containing a URN that indicates a unique identifier associated with the UA instance registering the Contact. Values appropriate for use with this feature tag: String (equality 23 sip.instance relationship). The feature tag is intended primarily for use in the following applications, protocols, [RFC5626] services, or negotiation mechanisms: This feature tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA. 24 sip.app-subtype This feature tag indicates the MIME application sub-types supported by the agent for purposes of streaming [RFC5688] media. 25 sip.fax This feature tag indicates whether a communications device supports the ITU-T T.38 fax protocol ("t38") or the [RFC6913] passthrough method of fax transmission using the ITU-T G.711 audio codec ("passthrough"). 26 sip.uui-isdn This media feature tag when used in a Contact header field of a SIP request or a SIP response indicates that [RFC7434] the entity sending the SIP message supports the package "uui-isdn". 27 sip.src This feature tag indicates that the UA is a Session Recording Client for the purpose of an RS. [RFC7866] 28 sip.srs This feature tag indicates that the UA is a Session Recording Server for the purpose of an RS. [RFC7866] This media feature tag, when inserted in the Contact header field of a SIP REGISTER request, conveys that the 29 sip.pnsreg SIP UA associated with the tag is able to send binding-refresh REGISTER requests associated with the [RFC8599] registration without being awakened by push notifications. This feature tag indicates that the device supports CLUE-controlled media. Values appropriate for use with this feature tag: Boolean. The feature tag is intended primarily for use in the following applications, 30 sip.clue protocols, services, or negotiation mechanisms: This feature tag is most useful in a communications [RFC8848] application for describing the capabilities of a device to use the CLUE control protocol to negotiate the use of multiple media streams. Contact Information ID Name Contact URI Last Updated [Kiran_Kapale] Kiran Kapale mailto:kiran.kapale&samsung.com 2023-02-27 [Frederic_Firmin] Frederic Firmin mailto:frederic.firmin&etsi.org 2017-08-02 [John_M_Meredith] John M Meredith mailto:john.meredith&etsi.org 2007-08-29 Licensing Terms