Media Feature Tags - iso.org.dod.internet.features (1.3.6.1.8)

Last Updated
2014-11-12
Available Formats

XML

HTML

Plain text

Registries included below

iso.org.dod.internet.features.ietf-tree (1.3.6.1.8.1)

Registration Procedure(s)
IETF Consensus [RFC2534]
Reference
[RFC2506]
Available Formats

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

CSV
Decimal Name Description Reference
1 g.3gpp.cs-voice This feature-tag indicates that the device supports circuit switched voice when combining circuit switched calls and IM sessions. [John_M_Meredith][ETSI TS 124 279]
2 g.3gpp.cs-video This feature-tag indicates that the device supports circuit switched video when combining circuit switched video calls and IM sessions. [John_M_Meredith][ETSI TS 124 279]
3 g.3gpp.smsip This feature-tag indicates that the device is capable of accepting SMS messages via SIP as specified by ETSI TS 124 341. [John_M_Meredith][ETSI TS 124 341]
4 g.3gpp.icsi-ref 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 media feature tag is defined to fulfil the requirements for 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. [Frederic_Firmin][3GPP TS 24.229]
5 g.3gpp.iari-ref 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 media feature tag is defined to fulfil the requirements for 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. [Frederic_Firmin][3GPP TS 24.229]
6 g.3gpp.ics This feature-tag when used in a SIP REGISTER request indicates that the function is ICS capability and may operate in ICS mode. This feature-tag when used is a none SIP REGISTER method indicates that the function wants to invoke ICS functionality. [Frederic_Firmin][3GPP TS 24.292]
7 g.3gpp.accesstype This feature-tag when used in a SIP REGISTER request indicates access network technology used by the device and the particular registration flow that the device is using to register over. [Frederic_Firmin][3GPP TS 24.292]
8 g.3gpp.pne-id This media feature-tag when used in a SIP request or a SIP response indicates the identifier of a PNE other than a UE. [Frederic_Firmin][3GPP TS 24.259]
9 g.3gpp.iut-controller This media feature-tag when used in a SIP request or a SIP response indicates that the function sending the SIP message supports the IUT Controller functionality.This media feature tag does not imply that the controller UE capabilities are handled in the same protocol manner. [Frederic_Firmin][3GPP TS 24.337]
10 g.3gpp.iut-focus 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 indicates that the function sending the SIP message supports anchoring a IUT session and/or the SIP message is an inter-UE transfer operation. [Frederic_Firmin][3GPP TS 24.337]
11 g.3gpp.current-iut-controller This media feature-tag when used in a Contact header field of SIP request or SIP response indicates that the UA is the currently active IUT controller for the collaborative session or is a controllee in the collaborative. The values of the feature tag are "active" and "passive". [Frederic_Firmin][3GPP TS 24.337]
12 g.3gpp.mid-call This feature-tag when used in a SIP request or a SIP response indicates that the function sending the SIP message supports the MSC server assisted mid-call feature. [Frederic_Firmin][3GPP TS 24.237]
13 g.3gpp.srvcc-alerting 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 SRVCC access transfer for calls in alerting phase, i.e. for calls whith early dialog. [Frederic_Firmin][3GPP TS 24.237]
14 g.3gpp.cs2ps-srvcc-alerting 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 CS to PS SRVCC access transfer for calls in alerting phase. [Frederic_Firmin][3GPP TS 24.237 11.10.0]
15 g.3gpp.path This media feature tag when used in a Contact header field in SIP REGISTER request or SIP response to the SIP REGISTER request indicates capability of identifying the registration path and binding SRVCC related information to it. [Frederic_Firmin][3GPP TS 24.237 11.10.0]
16 g.3gpp.cs2ps-srvcc This media feature tag when included in Contact header field indicates support of the CS to PS single radio voice call continuity as specified in 3GPP TS 24.237. [Frederic_Firmin][3GPP TS 24.237 11.10.0]
17 g.3gpp.pstops-sti 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 use of the PS to PS STI URI. [Frederic_Firmin][3GPP TS 24.237 11.10.0]
18 g.3gpp.ti This media feature tag when used in a Contact header field as specified in IETF RFC 3840 in SIP INVITE request or SIP response to the SIP INVITE request indicates the capability of associating a CS call with dialog created by the SIP INVITE request. [Frederic_Firmin][3GPP TS 24.237 11.10.0]

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 Consensus
Reference
[RFC3840]
Available Formats

CSV
Decimal Name Description Reference
1 sip.audio This feature tag indicates that the device supports audio as a streaming media type. [RFC3840]
2 sip.application This feature tag indicates that 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. [RFC3840]
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 a voicemail server, conference server, IVR, or recording device) or a human. [RFC3840]
8 sip.class This feature tag indicates the setting, business or personal, in which a communications device is used. [RFC3840]
9 sip.duplex The sip.duplex media feature tag 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"). [RFC3840]
10 sip.mobility The sip.mobility feature tag 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. [RFC3840]
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 event package names that are registered by each event package. [RFC3840]
13 sip.priority The sip.priority feature tag 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. [RFC3840]
14 sip.methods Each value of the sip.methods (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. [RFC3840]
15 sip.extensions Each value of the sip.extensions 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. [RFC3840]
16 sip.schemes Each value of the sip.schemes (note 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. [RFC3840]
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 the media for all calls to the same URI. [RFC3840]
19 sip.byeless The feature tag is a boolean flag. When set it indicates that the device is incapable of terminating a session autonomously. [RFC4235]
20 sip.rendering This feature tag contains one of three 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"). [RFC4235]
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]
23 sip.instance 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 relationship). The feature tag is intended primarily for use in the following applications, protocols, 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. [RFC5626]
24 sip.app-subtype This feature tag indicates the MIME application sub-types supported by the agent for purposes of streaming media. [RFC5688]
25 sip.fax This feature tag indicates whether a communications device supports the ITU-T T.38 fax protocol ("t38") or the passthrough method of fax transmission using the ITU-T G.711 audio codec ("passthrough"). [RFC6913]
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 the entity sending the SIP message supports the package "uui-isdn". [RFC-ietf-cuss-sip-uui-isdn-11]

People

ID Name Contact URI Last Updated
[Frederic_Firmin] Frederic Firmin mailto:frederic.firmin&etsi.org 2014-04-16
[John_M_Meredith] John M Meredith mailto:john.meredith&etsi.org 2007-08-29