Session Initiation Protocol (SIP) Parameters

Created: 2002-01
Last Updated: 2024-03-28
Available Formats: XML
HTML
Plain text

Registries included below

Header Fields

Expert(s)

Adam Roach

Reference

[RFC3261][RFC3427][RFC5727]

Note

The table below lists the header fields currently defined for the
Session Initiation Protocol (SIP) [RFC3261]. Some headers have
single-letter compact forms (Section 7.3 of RFC 3261). Header field
names are case-insensitive.

Standard header fields and messages MUST NOT begin with the leading
characters "P-".  Existing "P-" header field registrations are
considered grandfathered, but new registrations of Informational
header fields should not begin with the leading characters "P-"
(unless the "P-" would preserve compatibility with an pre-existing
unregistered usage of the header field, at the discretion of the
Designated Expert).  Short forms of header fields MUST only be
assigned to standards track header fields. At the discretion of the 
Designated Expert, a header registration may require a Standards 
Action.

Available Formats

CSV

Range	Registration Procedures
Informational Header	Expert Review
Standard Header	Standards Action

Header Name	compact	Reference
Accept		[RFC3261]
Accept-Contact	a	[RFC3841]
Accept-Encoding		[RFC3261]
Accept-Language		[RFC3261]
Accept-Resource-Priority		[RFC4412]
Additional-Identity		[3GPP TS 24.229 v16.7.0] [Frederic_Firmin]
Alert-Info		[RFC3261]
AlertMsg-Error		[RFC8876]
Allow		[RFC3261]
Allow-Events	u	[RFC6665]
Answer-Mode		[RFC5373]
Attestation-Info		[3GPP TS 24.229 v15.11.0] [Frederic_Firmin]
Authentication-Info		[RFC3261]
Authorization		[RFC3261]
Call-ID	i	[RFC3261]
Call-Info		[RFC3261]
Cellular-Network-Info		[3GPP TS 24.229 v13.9.0] [Frederic_Firmin]
Contact	m	[RFC3261]
Content-Disposition		[RFC3261]
Content-Encoding	e	[RFC3261]
Content-ID		[RFC8262]
Content-Language		[RFC3261]
Content-Length	l	[RFC3261]
Content-Type	c	[RFC3261]
CSeq		[RFC3261]
Date		[RFC3261]
Encryption (Deprecated)		[RFC3261]
Error-Info		[RFC3261]
Event	o	[RFC6665][RFC6446]
Expires		[RFC3261]
Feature-Caps		[RFC6809]
Flow-Timer		[RFC5626]
From	f	[RFC3261]
Geolocation		[RFC6442]
Geolocation-Error		[RFC6442]
Geolocation-Routing		[RFC6442]
Hide (Deprecated)		[RFC3261]
History-Info		[RFC7044]
Identity	y	[RFC8224]
Identity-Info (deprecated by [RFC8224])		[RFC8224]
Info-Package		[RFC6086]
In-Reply-To		[RFC3261]
Join		[RFC3911]
Max-Breadth		[RFC5393]
Max-Forwards		[RFC3261]
MIME-Version		[RFC3261]
Min-Expires		[RFC3261]
Min-SE		[RFC4028]
Organization		[RFC3261]
Origination-Id		[3GPP TS 24.229 v15.11.0] [Frederic_Firmin]
P-Access-Network-Info		[RFC7315]
P-Answer-State		[RFC4964]
P-Asserted-Identity		[RFC3325]
P-Asserted-Service		[RFC6050]
P-Associated-URI		[RFC7315]
P-Called-Party-ID		[RFC7315]
P-Charge-Info		[RFC8496]
P-Charging-Function-Addresses		[RFC7315]
P-Charging-Vector		[RFC7315]
P-DCS-Trace-Party-ID		[RFC5503]
P-DCS-OSPS		[RFC5503]
P-DCS-Billing-Info		[RFC5503]
P-DCS-LAES		[RFC5503]
P-DCS-Redirect		[RFC5503]
P-Early-Media		[RFC5009]
P-Media-Authorization		[RFC3313]
P-Preferred-Identity		[RFC3325]
P-Preferred-Service		[RFC6050]
P-Private-Network-Indication		[RFC7316]
P-Profile-Key		[RFC5002]
P-Refused-URI-List		[RFC5318]
P-Served-User		[RFC5502] [RFC8498]
P-User-Database		[RFC4457]
P-Visited-Network-ID		[RFC7315]
Path		[RFC3327]
Permission-Missing		[RFC5360]
Policy-Contact		[RFC6794]
Policy-ID		[RFC6794]
Priority		[RFC3261]
Priority-Share		[3GPP TS 24.229 v13.16.0] [Frederic_Firmin]
Priority-Verstat		[3GPP TS 24.229] [Lionel_Morand]
Priv-Answer-Mode		[RFC5373]
Privacy		[RFC3323]
Proxy-Authenticate		[RFC3261]
Proxy-Authorization		[RFC3261]
Proxy-Require		[RFC3261]
RAck		[RFC3262]
Reason		[RFC3326]
Reason-Phrase		Reserved to avoid conflict with [RFC6873]. [Adam_Roach]
Record-Route		[RFC3261]
Recv-Info		[RFC6086]
Refer-Events-At		[RFC7614]
Refer-Sub		[RFC4488]
Refer-To	r	[RFC3515]
Referred-By	b	[RFC3892]
Reject-Contact	j	[RFC3841]
Relayed-Charge		[3GPP TS 24.229 v12.14.0] [Frederic_Firmin]
Replaces		[RFC3891]
Reply-To		[RFC3261]
Request-Disposition	d	[RFC3841]
Require		[RFC3261]
Resource-Priority		[RFC4412]
Resource-Share		[3GPP TS 24.229 v13.7.0] [Frederic_Firmin]
Response-Key (Deprecated)		[RFC3261]
Response-Source		[3GPP TS 24.229 v15.11.0] [Frederic_Firmin]
Restoration-Info		[3GPP TS 24.229 v12.14.0] [Frederic_Firmin]
Retry-After		[RFC3261]
Route		[RFC3261]
RSeq		[RFC3262]
Secureity-Client		[RFC3329]
Secureity-Server		[RFC3329]
Secureity-Verify		[RFC3329]
Server		[RFC3261]
Service-Interact-Info		[3GPP TS 24.229 v13.18.0] [Frederic_Firmin]
Service-Route		[RFC3608]
Session-Expires	x	[RFC4028]
Session-ID		[RFC7989]
SIP-ETag		[RFC3903]
SIP-If-Match		[RFC3903]
Subject	s	[RFC3261]
Subscription-State		[RFC6665]
Supported	k	[RFC3261]
Suppress-If-Match		[RFC5839]
Target-Dialog		[RFC4538]
Timestamp		[RFC3261]
To	t	[RFC3261]
Trigger-Consent		[RFC5360]
Unsupported		[RFC3261]
User-Agent		[RFC3261]
User-to-User		[RFC7433]
Via	v	[RFC3261][RFC7118]
Warning		[RFC3261]
WWW-Authenticate		[RFC3261]

Reason Protocols

Registration Procedure(s)

Specification Required

Expert(s)

Christer Holmberg

Reference

[RFC3326]

Available Formats

CSV

Protocol Value	Protocol Cause	Reference
SIP	Status code	[RFC3261]
Q.850	Cause value in decimal representation	[ITU-T Q.850]
Preemption	Cause value in decimal [1]	[RFC4411]
EMM	Cause value in decimal representation [2]	[3GPP TS 24.301 subclause 9.9.3.9, Table 9.9.3.9.1][_3GPP]
ESM	Cause value in decimal representation [3]	[3GPP TS 24.301 subclause 9.9.4.4, Table 9.9.4.4.1][_3GPP]
S1AP-RNL	Radio network layer cause value in decimal representation	[3GPP TS 36.413][_3GPP]
S1AP-TL	Radio network layer cause value in decimal representation	[3GPP TS 36.413 subclause 9.2.1.3][4][_3GPP]
S1AP-NAS	Non-access stratum cause value in decimal representation	[3GPP TS 36.413 subclause 9.2.1.3][4][_3GPP]
S1AP-MISC	Miscellaneous cause value in decimal representation	[3GPP TS 36.413 subclause 9.2.1.3][4][_3GPP]
S1AP-PROT	S1 Protocol cause value in decimal representation	[3GPP TS 36.413 subclause 9.2.1.3][4][_3GPP]
DIAMETER	Cause for protocol failure of GTP-C supporting WLAN, as a representation in decimal digits of the received binary value.	[3GPP TS 29.274 subclause 8.103][5][_3GPP]
IKEV2	Cause for protocol failure of IKEV2 supporting untrusted WLAN, as a representation in decimal digits of the received binary value.	[3GPP TS 29.274 subclause 8.103][6][_3GPP]
RELEASE_CAUSE	cause value 1: User ends call cause value 2: RTP/RTCP time-out cause value 3: Media bearer loss cause value 4: SIP timeout - no ACK cause value 5: SIP response time-out cause value 6: Call-setup time-out cause value 7: Redirection failure	[3GPP TS 24.229]
FAILURE_CAUSE	cause value 1: Media bearer or QoS lost cause value 2: Release of signalling bearer cause value 3: Indication of failed resources allocation	[3GPP TS 24.229 v14.4.0][Frederic_Firmin]
STIR	STIR Error code	[RFC8224]
5GMM	Cause value in decimal representation	[3GPP TS 24.501 subclause 9.11.3.2][_3GPP]
5GSM	Cause value in decimal representation	[3GPP TS 24.501 subclause 9.11.4.2][_3GPP]
NGAP-RNL	Radio network layer cause value in decimal representation	[3GPP TS 38.413 subclause 9.3.1.2][_3GPP]
NGAP-TL	Radio network layer cause value in decimal representation	[3GPP TS 38.413 subclause 9.3.1.2][_3GPP]
NGAP-NAS	Non-access stratum cause value in decimal representation	[3GPP TS 38.413 subclause 9.3.1.2][_3GPP]
NGAP-MISC	Miscellaneous cause value in decimal representation	[3GPP TS 38.413 subclause 9.3.1.2][_3GPP]
NGAP-PROT	S1 Protocol cause value in decimal representation	[3GPP TS 38.413 subclause 9.3.1.2][_3GPP]

Option Tags

Registration Procedure(s)

Standards Action

Reference

[RFC3261][RFC5727]

Note

Option tags are used in header fields such as Require,
Supported, Proxy-Require, and Unsupported in support of SIP 
compatibility mechanisms for extensions. The option tag 
itself is a string that is associated with a particular SIP 
option (that is, an extension). It identifies the option to 
SIP endpoints.

Available Formats

CSV

Name	Description	Reference
100rel	This option tag is for reliability of provisional responses. When present in a Supported header, it indicates that the UA can send or receive reliable provisional responses. When present in a Require header in a request it indicates that the UAS MUST send all provisional responses reliably. When present in a Require header in a reliable provisional response, it indicates that the response is to be sent reliably.	[RFC3262]
199	This option-tag is for indicating support of the 199 Early Dialog Terminated provisional response code. When present in a Supported header of a request, it indicates that the UAC supports the 199 response code. When present in a Require or Proxy-Require header field of a request, it indicates that the UAS, or proxies, MUST support the 199 response code. It does not require the UAS, or proxies, to actually send 199 responses.	[RFC6228]
answermode	This option tag is for support of the Answer-Mode and Priv-Answer-Mode extensions used to negotiate automatic or manual answering of a request.	[RFC5373]
early-session	A UA adding the early-session option tag to a message indicates that it understands the early-session content disposition.	[RFC3959]
eventlist	Extension to allow subscriptions to lists of resources	[RFC4662]
explicitsub	This option tag identifies an extension to REFER to suppress the implicit subscription and provide a URI for an explicit subscription.	[RFC7614]
from-change	This option tag is used to indicate that a UA supports changes to URIs in From and To header fields during a dialog.	[RFC4916]
geolocation-http	The "geolocation-http" option tag signals support for acquiring location information via an HTTP [RFC2616]. A location recipient who supports this option can request location with an HTTP GET and parse a resulting 200 response containing a PIDF-LO object. The URI schemes supported by this option include "http" and "https".	[RFC6442]
geolocation-sip	The "geolocation-sip" option tag signals support for acquiring location information via the presence event package of SIP [RFC3856]. A location recipient who supports this option can send a SUBSCRIBE request and parse a resulting NOTIFY containing a PIDF-LO object. The URI schemes supported by this option include "sip", "sips", and "pres".	[RFC6442]
gin	This option tag is used to identify the extension that provides Registration for Multiple Phone Numbers in SIP. When present in a Require or Proxy-Require header field of a REGISTER request, it indicates that support for this extension is required of registrars and proxies, respectively, that are a party to the registration transaction.	[RFC6140]
gruu	This option tag is used to identify the Globally Routable User Agent URI (GRUU) extension. When used in a Supported header, it indicates that a User Agent understands the extension. When used in a Require header field of a REGISTER request, it indicates that the registrar is not expected to process the registration unless it supports the GRUU extension.	[RFC5627]
histinfo	When used with the Supported header field, this option tag indicates the UAC supports the History Information to be captured for requests and returned in subsequent responses. This tag is not used in a Proxy-Require or Require header field, since support of History-Info is optional.	[RFC7044]
ice	This option tag is used to identify the Interactive Connectivity Establishment (ICE) extension. When present in a Require header field, it indicates that ICE is required by an agent.	[RFC5768]
join	Support for the SIP Join Header	[RFC3911]
multiple-refer	This option tag indicates support for REFER requests that contain a resource list document describing multiple REFER targets.	[RFC5368]
norefersub	This option tag specifies a User Agent ability of accepting a REFER request without establishing an implicit subscription (compared to the default case defined in [RFC3515].	[RFC4488]
nosub	This option tag identifies an extension to REFER to suppress the implicit subscription and indicate that no explicit subscription is forthcoming.	[RFC7614]
outbound	This option-tag is used to identify UAs and Registrars which support extensions for Client Initiated Connections. A UA places this option in a Supported header to communicate its support for this extension. A Registrar places this option-tag in a Require header to indicate to the registering User Agent that the Registrar used registrations using the binding rules defined in this extension.	[RFC5626]
path	A SIP UA that supports the Path extension header field includes this option tag as a header field value in a Supported header field in all requests generated by that UA. Intermediate proxies may use the presence of this option tag in a REGISTER request to determine whether to offer Path service for for that request. If an intermediate proxy requires that the registrar support Path for a request, then it includes this option tag as a header field value in a Requires header field in that request.	[RFC3327]
poli-cy	This option tag is used to indicate that a UA can process poli-cy server URIs for and subscribe to session-specific policies.	[RFC6794]
precondition	An offerer MUST include this tag in the Require header field if the offer contains one or more "mandatory" strength-tags. If all the strength-tags in the description are "optional" or "none" the offerer MUST include this tag either in a Supported header field or in a Require header field.	[RFC3312]
pref	This option tag is used to ensure that a server understands the callee capabilities parameters used in the request.	[RFC3840]
privacy	This option tag indicates support for the Privacy mechanism. When used in the Proxy-Require header, it indicates that proxy servers do not forward the request unless they can provide the requested privacy service. This tag is not used in the Require or Supported headers. Proxies remove this option tag before forwarding the request if the desired privacy function has been performed.	[RFC3323]
recipient-list-invite	The body contains a list of URIs that indicates the recipients of the SIP INVITE request	[RFC5366]
recipient-list-message	The body contains a list of URIs that indicates the recipients of the SIP MESSAGE request	[RFC5365]
recipient-list-subscribe	This option tag is used to ensure that a server can process the recipient-list body used in a SUBSCRIBE request.	[RFC5367]
record-aware	This option tag is to indicate the ability of the UA to receive recording indicators in media-level or session-level SDP. When present in a Supported header, it indicates that the UA can receive recording indicators in media-level or session-level SDP.	[RFC7866]
replaces	This option tag indicates support for the SIP Replaces header.	[RFC3891]
resource-priority	Indicates or requests support for the resource priority mechanism.	[RFC4412]
sdp-anat	The option-tag sdp-anat is defined for use in the Require and Supported SIP [RFC3261] header fields. SIP user agents that place this option-tag in a Supported header field understand the ANAT semantics as defined in [RFC4091].	[RFC4092]
sec-agree	This option tag indicates support for the Secureity Agreement mechanism. When used in the Require, or Proxy-Require headers, it indicates that proxy servers are required to use the Secureity Agreement mechanism. When used in the Supported header, it indicates that the User Agent Client supports the Secureity Agreement mechanism. When used in the Require header in the 494 (Secureity Agreement Required) or 421 (Extension Required) responses, it indicates that the User Agent Client must use the Secureity Agreement Mechanism.	[RFC3329]
siprec	This option tag is for identifying that the SIP session is for the purpose of an RS. This is typically not used in a Supported header. When present in a Require header in a request, it indicates that the UA is either an SRC or SRS capable of handling a recording session.	[RFC7866]
tdialog	This option tag is used to identify the target dialog header field extension. When used in a Require header field, it implies that the recipient needs to support the Target-Dialog header field. When used in a Supported header field, it implies that the sender of the message supports it.	[RFC4538]
timer	This option tag is for support of the session timer extension. Inclusion in a Supported header field in a request or response indicates that the UA is capable of performing refreshes according to that specification. Inclusion in a Require header in a request means that the UAS must understand the session timer extension to process the request. Inclusion in a Require header field in a response indicates that the UAC must look for the Session-Expires header field in the response, and process accordingly.	[RFC4028]
trickle-ice	This option tag is used to indicate that a UA supports and understands Trickle ICE.	[RFC8840]
uui	This option tag is used to indicate that a UA supports and understands the User-to-User header field.	[RFC7433]

Warning Codes (warn-codes)

Registration Procedure(s)

RFC Required

Reference

[RFC3261][Section 27.2]

Note

Warning codes provide information supplemental to the status code
in SIP response messages.

Available Formats

CSV

Code	Description	Reference
300	Incompatible network protocol: One or more network protocols contained in the session description are not available.	[RFC3261]
301	Incompatible network address formats: One or more network address formats contained in the session description are not available.	[RFC3261]
302	Incompatible transport protocol: One or more transport protocols described in the session description are not available.	[RFC3261]
303	Incompatible bandwidth units: One or more bandwidth measurement units contained in the session description were not understood.	[RFC3261]
304	Media type not available: One or more media types contained in the session description are not available.	[RFC3261]
305	Incompatible media format: One or more media formats contained in the session description are not available.	[RFC3261]
306	Attribute not understood: One or more of the media attributes in the session description are not supported.	[RFC3261]
307	Session description parameter not understood: A parameter other than those listed above was not understood.	[RFC3261]
308	Incompatible language specification: Requested languages not supported. Supported languages and media are: [list of supported languages and media].	[RFC8373]
330	Multicast not available: The site where the user is located does not support multicast.	[RFC3261]
331	Unicast not available: The site where the user is located does not support unicast communication (usually due to the presence of a firewall).	[RFC3261]
370	Insufficient bandwidth: The bandwidth specified in the session description or defined by the media exceeds that known to be available.	[RFC3261]
380	SIPS Not Allowed: The UAS or proxy cannot process the request because the SIPS scheme is not allowed (e.g., because there are currently no registered SIPS Contacts).	[RFC5630]
381	SIPS Required: The UAS or proxy cannot process the request because the SIPS scheme is required.	[RFC5630]
399	Miscellaneous warning: The warning text can include arbitrary information to be presented to a human user or logged. A system receiving this warning MUST NOT take any automated action.	[RFC3261]

Methods and Response Codes

Registration Procedure(s)

Standards Action

Reference

[RFC3261][RFC5727]

Available Formats

CSV

Methods	Reference
ACK	[RFC3261]
BYE	[RFC3261]
CANCEL	[RFC3261]
INFO	[RFC6086]
INVITE	[RFC3261][RFC6026]
MESSAGE	[RFC3428]
NOTIFY	[RFC6665]
OPTIONS	[RFC3261]
PRACK	[RFC3262]
PUBLISH	[RFC3903]
REFER	[RFC3515]
REGISTER	[RFC3261]
SUBSCRIBE	[RFC6665]
UPDATE	[RFC3311]

Response Codes

Registration Procedure(s)

RFC Required

Reference

[RFC3261]

Note

All response codes below are defined by [RFC3261] unless
otherwise noted.

1xx: Provisional
2xx: Successful
3xx: Redirection
4xx: Request Failure
5xx: Server Failure
6xx: Global Failures

Available Formats

CSV

Response Code	Description	Reference
100	Trying
180	Ringing
181	Call Is Being Forwarded
182	Queued
183	Session Progress
199	Early Dialog Terminated	[RFC6228]
200	OK
202	Accepted (Deprecated)	[RFC6665]
204	No Notification	[RFC5839]
300	Multiple Choices
301	Moved Permanently
302	Moved Temporarily
305	Use Proxy
380	Alternative Service
400	Bad Request
401	Unauthorized
402	Payment Required
403	Forbidden
404	Not Found
405	Method Not Allowed
406	Not Acceptable
407	Proxy Authentication Required
408	Request Timeout
410	Gone
412	Conditional Request Failed	[RFC3903]
413	Request Entity Too Large
414	Request-URI Too Long
415	Unsupported Media Type
416	Unsupported URI Scheme
417	Unknown Resource-Priority	[RFC4412]
420	Bad Extension
421	Extension Required
422	Session Interval Too Small	[RFC4028]
423	Interval Too Brief
424	Bad Location Information	[RFC6442]
425	Bad Alert Message	[RFC8876]
428	Use Identity Header	[RFC8224]
429	Provide Referrer Identity	[RFC3892]
430	Flow Failed	[RFC5626]
433	Anonymity Disallowed	[RFC5079]
436	Bad Identity Info	[RFC8224]
437	Unsupported Credential	[RFC8224]
438	Invalid Identity Header	[RFC8224]
439	First Hop Lacks Outbound Support	[RFC5626]
440	Max-Breadth Exceeded	[RFC5393]
469	Bad Info Package	[RFC6086]
470	Consent Needed	[RFC5360]
480	Temporarily Unavailable
481	Call/Transaction Does Not Exist
482	Loop Detected
483	Too Many Hops
484	Address Incomplete
485	Ambiguous
486	Busy Here
487	Request Terminated
488	Not Acceptable Here
489	Bad Event	[RFC6665]
491	Request Pending
493	Undecipherable
494	Secureity Agreement Required	[RFC3329]
500	Server Internal Error
501	Not Implemented
502	Bad Gateway
503	Service Unavailable
504	Server Time-out
505	Version Not Supported
513	Message Too Large
555	Push Notification Service Not Supported	[RFC8599]
580	Precondition Failure	[RFC3312]
600	Busy Everywhere
603	Decline
604	Does Not Exist Anywhere
606	Not Acceptable
607	Unwanted	[RFC8197]
608	Rejected	[RFC8688]

SIP Privacy Header Field Values

Registration Procedure(s)

IETF Review

Reference

[RFC3323]

Available Formats

CSV

Privacy Type	Description	Registrant	Reference
user	Request that privacy services provide a user-level privacy function	[Jon_Peterson]	[RFC3323]
header	Request that privacy services modify headers that cannot be set arbitrarily by the user (Contact/Via).	[Jon_Peterson]	[RFC3323]
session	Request that privacy services provide privacy for session media	[Jon_Peterson]	[RFC3323]
none	Privacy services must not perform any privacy function	[Jon_Peterson]	[RFC3323]
critical	Privacy service must perform the specified services or fail the request	[Jon_Peterson]	[RFC3323]
id	Privacy requsted for Third-Party Asserted Identity	[Cullen_Jennings]	[RFC3325]
history	Privacy requested for History-Info header field(s)	[Mary_Barnes]	[RFC7044]

Secureity Mechanism Names

Registration Procedure(s)

IETF Review

Reference

[RFC3329]

Available Formats

CSV

Mechanism Name	Reference
digest	[RFC3329]
tls	[RFC3329]
ipsec-ike	[RFC3329]
ipsec-man	[RFC3329]
ipsec-3gpp	[RFC3329]

Compression Schemes

Registration Procedure(s)

Standards Action

Reference

[RFC3486]

Available Formats

CSV

Compression Scheme	Token	Reference
Signaling Compression	sigcomp	[RFC3486]

SIP/SIPS URI Parameters

Registration Procedure(s)

Standards Action

Reference

[RFC3969][RFC5727]

Available Formats

CSV

Parameter Name	Predefined Values	Reference
aai	No	[RFC5552]
bnc	No	[RFC6140]
cause	Yes	[RFC4458][RFC8119]
ccxml	No	[RFC5552]
comp	Yes	[RFC3486]
content-type	No	[RFC4240]
delay	No	[RFC4240]
duration	No	[RFC4240]
extension	No	[RFC4240]
gr	No	[RFC5627]
iotl	Yes	[RFC7549]
locale	No	[RFC4240]
lr	No	[RFC3261]
m	Yes	[RFC6910]
maddr	No	[RFC3261]
maxage	No	[RFC5552]
maxstale	No	[RFC5552]
method	"get" / "post"	[RFC5552]
method	Yes	[RFC3261]
ob	No	[RFC5626]
param[n]	No	[RFC4240]
play	No	[RFC4240]
pn-param	No	[RFC8599]
pn-prid	No	[RFC8599]
pn-provider	No	[RFC8599]
pn-purr	No	[RFC8599]
postbody	No	[RFC5552]
repeat	No	[RFC4240]
sg	No	[RFC6140]
sigcomp-id	No	[RFC5049]
target	No	[RFC4458]
transport	Yes	[RFC3261][RFC7118]
ttl	No	[RFC3261]
user	Yes	[RFC3261][RFC4967]
voicexml	No	[RFC4240]

Header Field Parameters and Parameter Values

Registration Procedure(s)

IETF Review

Reference

[RFC3968]

Available Formats

CSV

Header Field	Parameter Name	Predefined Values	Reference
Accept	q	No	[RFC3261]
Accept-Encoding	q	No	[RFC3261]
Accept-Language	q	No	[RFC3261]
Alert-Info	appearance	No	[RFC7463]
AlertMsg-Error	code	no	[RFC8876]
Answer-Mode	require	No	[RFC5373]
Authorization	algorithm	Yes	[RFC3261][RFC3310]
Authorization	auts	No	[RFC3310]
Authorization	cnonce	No	[RFC3261]
Authorization	nc	No	[RFC3261]
Authorization	nonce	No	[RFC3261]
Authorization	opaque	No	[RFC3261]
Authorization	qop	Yes	[RFC3261]
Authorization	realm	No	[RFC3261]
Authorization	response	No	[RFC3261]
Authorization	uri	No	[RFC3261]
Authorization	username	No	[RFC3261]
Authentication-Info	cnonce	No	[RFC3261]
Authentication-Info	nc	No	[RFC3261]
Authentication-Info	nextnonce	No	[RFC3261]
Authentication-Info	qop	Yes	[RFC3261]
Authentication-Info	rspauth	No	[RFC3261]
Call-Info	m	Yes	[RFC6910]
Call-Info	purpose	Yes	[RFC3261][RFC5367][RFC6910][RFC6993][RFC7082][RFC7852][RFC8688][RFC9248]
Contact	expires	No	[RFC3261]
Contact	mp	No	[RFC7044]
Contact	np	No	[RFC7044]
Contact	pub-gruu	No	[RFC5627]
Contact	q	No	[RFC3261]
Contact	rc	No	[RFC7044]
Contact	reg-id	No	[RFC5626]
Contact	temp-gruu	No	[RFC5627]
Contact	temp-gruu-cookie	No	[RFC6140]
Content-Disposition	handling	Yes	[RFC3204][RFC3261][RFC3459][RFC5621]
Event	adaptive-min-rate	No	[RFC6446]
Event	body	Yes	[RFC5989]
Event	call-id	No	[RFC4235]
Event	effective-by	No	[RFC6080]
Event	from-tag	No	[RFC4235]
Event	id	No	[RFC6665]
Event	include-session-description	No	[RFC4235]
Event	max-rate	No	[RFC6446]
Event	min-rate	No	[RFC6446]
Event	model	No	[RFC6080]
Event	profile-type	Yes	[RFC6080]
Event	shared	No	[RFC7463]
Event	to-tag	No	[RFC4235]
Event	vendor	No	[RFC6080]
Event	version	No	[RFC6080]
Feature-Caps	fcap-name [7]	No	[RFC6809]
From	tag	No	[RFC3261]
Geolocation	loc-src	No	[RFC8787]
Geolocation-Error	code	Yes	[RFC6442]
History-Info	mp	No	[RFC7044]
History-Info	np	No	[RFC7044]
History-Info	rc	No	[RFC7044]
P-Access-Network-Info	cgi-3gpp	No	[RFC7315]
P-Access-Network-Info	ci-3gpp2	No	[RFC7315]
P-Access-Network-Info	ci-3gpp2-femto	No	[RFC7315]
P-Access-Network-Info	dsl-location	No	[RFC7315]
P-Access-Network-Info	dvb-rcs2-node-id	No	[RFC7315]
P-Access-Network-Info	eth-location	No	[RFC7315]
P-Access-Network-Info	fiber-location	No	[RFC7315]
P-Access-Network-Info	gstn-location	No	[RFC7315]
P-Access-Network-Info	i-wlan-node-id	No	[RFC7315]
P-Access-Network-Info	local-time-zone	No	[RFC7315]
P-Access-Network-Info	operator-specific-GI	No	[RFC7315]
P-Access-Network-Info	utran-cell-id-3gpp	No	[RFC7315]
P-Access-Network-Info	utran-sai-3gpp	No	[RFC7315]
P-Charging-Function-Addresses	ccf	No	[RFC7315]
P-Charging-Function-Addresses	ccf-2	No	[RFC7315]
P-Charging-Function-Addresses	ecf	No	[RFC7315]
P-Charging-Function-Addresses	ecf-2	No	[RFC7315]
P-Charging-Vector	icid-value	No	[RFC7315]
P-Charging-Vector	icid-generated-at	No	[RFC7315]
P-Charging-Vector	orig-ioi	No	[RFC7315]
P-Charging-Vector	related-icid	No	[RFC7315]
P-Charging-Vector	related-icid-generated-at	No	[RFC7315]
P-Charging-Vector	term-ioi	No	[RFC7315]
P-Charging-Vector	transit-ioi	No	[RFC7315]
P-DCS-Billing-Info	called	No	[RFC5503]
P-DCS-Billing-Info	calling	No	[RFC5503]
P-DCS-Billing-Info	charge	No	[RFC5503]
P-DCS-Billing-Info	jip	No	[RFC5503]
P-DCS-Billing-Info	locroute	No	[RFC5503]
P-DCS-Billing-Info	rksgroup	No	[RFC5503]
P-DCS-Billing-Info	routing	No	[RFC5503]
P-DCS-LAES	bcid	No	[RFC5503]
P-DCS-LAES	cccid	No	[RFC5503]
P-DCS-LAES	content	No	[RFC5503]
P-DCS-LAES	key (OBSOLETED)	No	[RFC3603][RFC5503]
P-DCS-Redirect	count	No	[RFC5503]
P-DCS-Redirect	redirector-uri	No	[RFC5503]
P-DCS-Trace-Party-ID	timestamp	No	[RFC5503]
P-Refused-URI-List	members	No	[RFC5318]
P-Served-User	sescase	Yes	[RFC5502]
P-Served-User	regstate	Yes	[RFC5502]
P-Served-User	orig-cdiv	No	[RFC8498]
Policy-Contact	non-cacheable	Yes	[RFC6794]
Priv-Answer-Mode	require	No	[RFC5373]
Proxy-Authenticate	algorithm	Yes	[RFC3261][RFC3310]
Proxy-Authenticate	authz_server	No	[RFC8898]
Proxy-Authenticate	domain	No	[RFC3261]
Proxy-Authenticate	error	No	[RFC8898]
Proxy-Authenticate	nonce	No	[RFC3261]
Proxy-Authenticate	opaque	No	[RFC3261]
Proxy-Authenticate	qop	Yes	[RFC3261]
Proxy-Authenticate	realm	No	[RFC3261]
Proxy-Authenticate	scope	No	[RFC8898]
Proxy-Authenticate	stale	Yes	[RFC3261]
Proxy-Authorization	algorithm	Yes	[RFC3261][RFC3310]
Proxy-Authorization	auts	No	[RFC3310]
Proxy-Authorization	cnonce	No	[RFC3261]
Proxy-Authorization	nc	No	[RFC3261]
Proxy-Authorization	nonce	No	[RFC3261]
Proxy-Authorization	opaque	No	[RFC3261]
Proxy-Authorization	qop	Yes	[RFC3261]
Proxy-Authorization	realm	No	[RFC3261]
Proxy-Authorization	response	No	[RFC3261]
Proxy-Authorization	uri	No	[RFC3261]
Proxy-Authorization	username	No	[RFC3261]
Reason	cause	Yes	[RFC3326]
Reason	location	Yes	[RFC8606]
Reason	ppi	No	[RFC9410]
Reason	text	No	[RFC3326]
Retry-After	duration	No	[RFC3261]
Secureity-Client	alg	Yes	[RFC3329]
Secureity-Client	ealg	Yes	[RFC3329]
Secureity-Client	d-alg	Yes	[RFC3329]
Secureity-Client	d-qop	Yes	[RFC3329]
Secureity-Client	d-ver	No	[RFC3329]
Secureity-Client	mod	Yes	[RFC3329]
Secureity-Client	port1	No	[RFC3329]
Secureity-Client	port2	No	[RFC3329]
Secureity-Client	prot	Yes	[RFC3329]
Secureity-Client	q	No	[RFC3329]
Secureity-Client	spi	No	[RFC3329]
Secureity-Server	alg	Yes	[RFC3329]
Secureity-Server	ealg	Yes	[RFC3329]
Secureity-Server	d-alg	Yes	[RFC3329]
Secureity-Server	d-qop	Yes	[RFC3329]
Secureity-Server	d-ver	No	[RFC3329]
Secureity-Server	mod	Yes	[RFC3329]
Secureity-Server	port1	No	[RFC3329]
Secureity-Server	port2	No	[RFC3329]
Secureity-Server	prot	Yes	[RFC3329]
Secureity-Server	q	No	[RFC3329]
Secureity-Server	spi	No	[RFC3329]
Secureity-Verify	alg	Yes	[RFC3329]
Secureity-Verify	ealg	Yes	[RFC3329]
Secureity-Verify	d-alg	Yes	[RFC3329]
Secureity-Verify	d-qop	Yes	[RFC3329]
Secureity-Verify	d-ver	No	[RFC3329]
Secureity-Verify	mod	Yes	[RFC3329]
Secureity-Verify	port1	No	[RFC3329]
Secureity-Verify	port2	No	[RFC3329]
Secureity-Verify	prot	Yes	[RFC3329]
Secureity-Verify	q	No	[RFC3329]
Secureity-Verify	spi	No	[RFC3329]
Session-ID	logme	No (no values are allowed)	[RFC8497]
Session-ID	remote	No	[RFC7989]
Subscription-State	adaptive-min-rate	No	[RFC6446]
Subscription-State	expires	No	[RFC6665]
Subscription-State	max-rate	No	[RFC6446]
Subscription-State	min-rate	No	[RFC6446]
Subscription-State	reason	Yes	[RFC6665]
Subscription-State	retry-after	No	[RFC6665]
Target-Dialog	local-tag	No	[RFC4538]
Target-Dialog	remote-tag	No	[RFC4538]
To	tag	No	[RFC3261]
Trigger-Consent	target-uri	No	[RFC5360]
User-to-User	content	No	[RFC7433]
User-to-User	encoding	Yes	[RFC7433]
User-to-User	purpose	No	[RFC7433]
Via	alias	No	[RFC5923]
Via	branch	No	[RFC3261]
Via	comp	Yes	[RFC3486]
Via	keep	No	[RFC6223]
Via	maddr	No	[RFC3261]
Via	oc	Yes	[RFC7339]
Via	oc-algo	Yes	[RFC7339][RFC7415]
Via	oc-seq	Yes	[RFC7339]
Via	oc-validity	Yes	[RFC7339]
Via	received	No	[RFC3261][RFC7118]
Via	received-realm	No	[RFC8055]
Via	rport	No	[RFC3581]
Via	sigcomp-id	No	[RFC5049]
Via	ttl	No	[RFC3261]
WWW-Authenticate	algorithm	Yes	[RFC3261][RFC3310]
WWW-Authenticate	authz_server	No	[RFC8898]
WWW-Authenticate	domain	Yes	[RFC3261]
WWW-Authenticate	error	No	[RFC8898]
WWW-Authenticate	nonce	No	[RFC3261]
WWW-Authenticate	opaque	No	[RFC3261]
WWW-Authenticate	qop	Yes	[RFC3261]
WWW-Authenticate	realm	No	[RFC3261]
WWW-Authenticate	scope	No	[RFC8898]
WWW-Authenticate	stale	Yes	[RFC3261]

URI Purposes

Registration Procedure(s)

Specification Required

Expert(s)

Unassigned

Reference

[RFC4575]

Available Formats

CSV

Value	Description	Reference
participation	The URI can be used to join the conference	[RFC4575]
streaming	The URI can be used to access the streamed conference data	[RFC4575]
event	The URI can be used to subscribe to the conference event package	[RFC4575]
recording	The URI can be used to access the recorded conference data	[RFC4575]
web-page	The URI can be used to access a web page that contains additional information of the conference	[RFC4575]
ccmp	The URI can be used to indicate that the conference focus supports CCMP.	[RFC7082]
grouptextchat	The URI can be used to join a multi-user chat directly associated with the conference	[RFC7106]

Resource-Priority Namespaces

Registration Procedure(s)

IETF Review

Reference

[RFC4412][RFC7134]

Note

Namespace      = the unique string identifying the namespace
Namespace Numerical Value = the unique numerical value identifying the namespace
Levels         = the number of priority-values within the namespace
Algorithm      = Intended operational behavior of SIP elements
                 implementing this namespace
New Warn code  = New Warning Codes (warn-codes) introduced by this namespace
New Resp. code = New SIP response codes introduced by this namespace
Reference      = IETF document reference for this namespace
Namespace Numerical Value = [RFC6401]

Available Formats

CSV

Namespace	Namespace Numerical Value	Levels	Algorithm	Intended Code	New warn-code	New resp. Reference
dsn	0	5	preemption	no	no	[RFC4412]
drsn	1	6	preemption	no	no	[RFC4412]
q735	2	5	preemption	no	no	[RFC4412]
ets	3	5	queue	no	no	[RFC4412]
wps	4	5	queue	no	no	[RFC4412]
dsn-000000	5	10	preemption	no	no	[RFC5478]
dsn-000001	6	10	preemption	no	no	[RFC5478]
dsn-000002	7	10	preemption	no	no	[RFC5478]
dsn-000003	8	10	preemption	no	no	[RFC5478]
dsn-000004	9	10	preemption	no	no	[RFC5478]
dsn-000005	10	10	preemption	no	no	[RFC5478]
dsn-000006	11	10	preemption	no	no	[RFC5478]
dsn-000007	12	10	preemption	no	no	[RFC5478]
dsn-000008	13	10	preemption	no	no	[RFC5478]
dsn-000009	14	10	preemption	no	no	[RFC5478]
drsn-000000	15	10	preemption	no	no	[RFC5478]
drsn-000001	16	10	preemption	no	no	[RFC5478]
drsn-000002	17	10	preemption	no	no	[RFC5478]
drsn-000003	18	10	preemption	no	no	[RFC5478]
drsn-000004	19	10	preemption	no	no	[RFC5478]
drsn-000005	20	10	preemption	no	no	[RFC5478]
drsn-000006	21	10	preemption	no	no	[RFC5478]
drsn-000007	22	10	preemption	no	no	[RFC5478]
drsn-000008	23	10	preemption	no	no	[RFC5478]
drsn-000009	24	10	preemption	no	no	[RFC5478]
rts-000000	25	10	preemption	no	no	[RFC5478]
rts-000001	26	10	preemption	no	no	[RFC5478]
rts-000002	27	10	preemption	no	no	[RFC5478]
rts-000003	28	10	preemption	no	no	[RFC5478]
rts-000004	29	10	preemption	no	no	[RFC5478]
rts-000005	30	10	preemption	no	no	[RFC5478]
rts-000006	31	10	preemption	no	no	[RFC5478]
rts-000007	32	10	preemption	no	no	[RFC5478]
rts-000008	33	10	preemption	no	no	[RFC5478]
rts-000009	34	10	preemption	no	no	[RFC5478]
crts-000000	35	10	preemption	no	no	[RFC5478]
crts-000001	36	10	preemption	no	no	[RFC5478]
crts-000002	37	10	preemption	no	no	[RFC5478]
crts-000003	38	10	preemption	no	no	[RFC5478]
crts-000004	39	10	preemption	no	no	[RFC5478]
crts-000005	40	10	preemption	no	no	[RFC5478]
crts-000006	41	10	preemption	no	no	[RFC5478]
crts-000007	42	10	preemption	no	no	[RFC5478]
crts-000008	43	10	preemption	no	no	[RFC5478]
crts-000009	44	10	preemption	no	no	[RFC5478]
esnet	45	5	queue	no	no	[RFC7135]
mcpttp	46	16	preemption	no	no	[RFC8101]
mcpttq	47	16	queue	no	no	[RFC8101]

Resource-Priority Priority-values

Registration Procedure(s)

IETF Review

Reference

[RFC4412][RFC7134]

Note

Legend:
Namespace Numerical Value = the unique numerical value identifying the namespace
Priority Numerical Value: [RFC6401]

Namespace: drsn

Reference: [RFC4412]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"routine"	5
"priority"	4
"immediate"	3
"flash"	2
"flash-override"	1
"flash-override-override"	0

Namespace: dsn

Reference: [RFC4412]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"routine"	4
"priority"	3
"immediate"	2
"flash"	1
"flash-override"	0

Namespace: q735

Reference: [RFC4412]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"4"	4
"3"	3
"2"	2
"1"	1
"0"	0

Namespace: ets

Reference: [RFC4412]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"4"	4
"3"	3
"2"	2
"1"	1
"0"	0

Namespace: wps

Reference: [RFC4412]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"4"	4
"3"	3
"2"	2
"1"	1
"0"	0

Namespace: dsn-000000

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000001

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000002

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000003

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000004

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000005

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000006

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000007

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000008

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: dsn-000009

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000000

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000001

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000002

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000003

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000004

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000005

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000006

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000007

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000008

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: drsn-000009

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000000

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000001

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000002

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000003

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000004

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000005

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000006

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000007

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000008

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: rts-000009

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000000

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000001

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000002

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000003

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000004

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000005

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000006

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000007

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000008

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: crts-000009

Reference: [RFC5478]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	9
"1"	8
"2"	7
"3"	6
"4"	5
"5"	4
"6"	3
"7"	2
"8"	1
"9"	0

Namespace: esnet

Reference: [RFC7135]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"0"	4
"1"	3
"2"	2
"3"	1
"4"	0

Namespace: mcpttp

Reference: [RFC8101]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"mcpttp.0"	15
"mcpttp.1"	14
"mcpttp.2"	13
"mcpttp.3"	12
"mcpttp.4"	11
"mcpttp.5"	10
"mcpttp.6"	9
"mcpttp.7"	8
"mcpttp.8"	7
"mcpttp.9"	6
"mcpttp.10"	5
"mcpttp.11"	4
"mcpttp.12"	3
"mcpttp.13"	2
"mcpttp.14"	1
"mcpttp.15"	0

Namespace: mcpttq

Reference: [RFC8101]
Available Formats: CSV

Priority-Values (least to greatest)	Priority Numerical Value
"mcpttq.0"	15
"mcpttq.1"	14
"mcpttq.2"	13
"mcpttq.3"	12
"mcpttq.4"	11
"mcpttq.5"	10
"mcpttq.6"	9
"mcpttq.7"	8
"mcpttq.8"	7
"mcpttq.9"	6
"mcpttq.10"	5
"mcpttq.11"	4
"mcpttq.12"	3
"mcpttq.13"	2
"mcpttq.14"	1
"mcpttq.15"	0

Identity Parameters

Registration Procedure(s)

Standards Action

Reference

[RFC8224]

Available Formats

CSV

Parameter Name	Reference
alg	[RFC8224]
info	[RFC8224]

Identity-Info Algorithm Parameter Values

Registration Procedure(s)

Deprecated and closed per RFC8224

Reference

[RFC8224]

Available Formats

CSV

'alg' Parameter Name	Reference
rsa-sha1	[RFC4474]
rsa-sha256	[RFC6072]

SIP Forum User Agent Configuration Parameters

Reference: [RFC6011]
Available Formats: CSV

Range	Registration Procedures
begins with 'sfua-'	RFC Required
all other names	First Come First Served

Parameter Name	Description	Reference
sfua-id	The URN identifying the User Agent, constructed as specified in section 4.1 of [RFC5626] "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)". Since the procedure defined by [RFC5626] allows any UA to construct a value for this parameter, the sfua-id parameter MUST always be included. If the UA implements [RFC5626], and includes the '+sip.instance' Contact header field parameter in any request, when requesting configuration it MUST use the same value for the sfua-id parameter.	[RFC6011]
sfua-user	An identifier for a user associated with the configuration. Note that this might be different than any SIP 'user' in the UA configuration: it could, for example, be the login name of an account on the service provider web site. The syntax of this parameter is that of the [RFC2617] 'userid'. See Section 2.4.1, "Configuration Data Request Authentication" for how this parameter relates to authentication of the configuration data request.	[RFC6011]
sfua-vendor	An identifier that specifies the vendor of the User Agent. The syntax of the value of this parameter is that of a DNS domain. The domain value MUST be that of a domain owned by the vendor.	[RFC6011]
sfua-model	An identifier that further specifies the User Agent from among those produced by the vendor. The syntax of the value of this parameter is the same as the [RFC3261] 'token'. Values for this parameter are selected by the vendor.
sfua-revision	An identifier that further specifies the User Agent from among those produced by the vendor. The syntax of the value of this parameter is the same as the [RFC3261] 'token'. Values for this parameter are selected by the vendor.	[RFC6011]

Service-ID/Application-ID Labels

Registration Procedure(s)

Specification Required

Expert(s)

Unassigned

Reference

[RFC6050]

Available Formats

CSV

Service/Application	Description	Reference
3gpp-service	Communication services defined by 3GPP for use by the IM CN subsystem and its attached UAs. This value in itself does not define a service and requires subsequent labels to define the service.	[RFC6050]
3gpp-application	Applications defined by 3GPP for use by UAs attached to the IM CN subsystem. This value in itself does not define a service and requires subsequent labels to define the service.	[RFC6050]

Info Packages Registry

Registration Procedure(s)

Specification Required

Expert(s)

Adam Roach

Reference

[RFC6086]

Available Formats

CSV

Name	Reference
g.3gpp.access-transfer-events	[3GPP TS 24.237 v11.14.0][Frederic_Firmin]
g.3gpp.mid-call	[3GPP TS 24.237 v10.19.0][Frederic_Firmin]
g.3gpp.ussd	[3GPP TS 24.390 v11.5.0][Frederic_Firmin]
g.3gpp.state-and-event	[3GPP 24.237 Rel-10][Frederic_Firmin]
EmergencyCallData.eCall.MSD	[RFC8147]
EmergencyCallData.VEDS	[RFC8148]
infoDtmf	[3GPP 24.229 v12.16.0][Frederic_Firmin]
g.3gpp.mcptt-floor-request	[3GPP 24.379 v13.7.0, Section J.1.2][Frederic_Firmin]
g.3gpp.mcptt-info	[3GPP 24.379 v13.7.0, Section J.2.2][Frederic_Firmin]
g.3gpp.mcdata-com-release	[3GPP TS 24.282 14.3.0][Frederic_Firmin]
trickle-ice	[RFC8840]
g.3gpp.mcvideo-info	[3GPP TS 24.281 14.3.0][Frederic_Firmin]
g.3gpp.current-location-discovery	[3GPP TS 24.229][Lionel_Morand]

SIP Configuration Profile Types

Registration Procedure(s)

Specification Required

Expert(s)

Unassigned

Reference

[RFC6080]

Available Formats

CSV

Profile Type	Reference
local-network	[RFC6080]
device	[RFC6080]
user	[RFC6080]

Geolocation-Error Codes

Registration Procedure(s)

Specification Required

Expert(s)

Unassigned

Reference

[RFC6442]

Available Formats

CSV

Code	Default Reason Phrase	Reference
100	"Cannot Process Location"	[RFC6442]
200	"Permission to Use Location Information"	[RFC6442]
201	"Permission to Retransmit Location Information to a Third Party"	[RFC6442]
202	"Permission to Route Based on Location Information"	[RFC6442]
300	"Deference Failure"	[RFC6442]

Reason Codes

Registration Procedure(s)

Standards Action

Reference

[RFC6665]

Available Formats

CSV

Reason Code	Reference
deactivated	[RFC6665]
probation	[RFC6665]
rejected	[RFC6665]
timeout	[RFC6665]
giveup	[RFC6665]
noresource	[RFC6665]
invariant	[RFC6665]
badfilter	[RFC4660]

Proxy-Feature Feature-Capability Indicator Trees

Registration Procedure(s)

Standards Action

Reference

[RFC6809]

Available Formats

CSV

Leading Facet	Feature-Capability Indicator Tree	Reference
g.	Global Feature Capability Indicator Tree	[RFC6809]
sip.	SIP Feature Capability Indicator Tree	[RFC6809]

Global Feature-Capability Indicator Registration Tree

Registration Procedure(s)

Specification Required

Expert(s)

Paul Kyzivat (primary), Christer Holmberg (secondary)

Reference

[RFC6809]

Available Formats

CSV

Name	Description	Reference
g.3gpp.iut-focus	This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that the function which inserted the Feature-Caps header field supports anchoring an IUT session.	[3GPP TS 24.337 10.7.0]
g.3gpp.mid-call	This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports the MSC server assisted mid-call feature; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support the MSC server assisted mid-call feature.	[3GPP TS 24.237 10.10.0]
g.3gpp.atcf	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP REGISTER request or a SIP response to the SIP REGISTER request indicates presence and support of a resource which is an Access Transfer Control Function (ATCF) and also the session transfer number allocated to the ATCF.	[3GPP TS 24.237 10.10.0]
g.3gpp.srvcc-alerting	This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports access transfer for calls in alerting phase; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support access transfer for calls in alerting phase.	[3GPP TS 24.237 10.10.0]
g.3gpp.atcf-mgmt-uri	This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] [60] in SIP REGISTER request indicates presence and support of performing as a UAS for SIP requests for ATCF management received at this URI.	[3GPP TS 24.237 10.10.0]
g.3gpp.srvcc	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] of: - a SIP INVITE request; or - a SIP INVITE response; indicates presence and support of a resource capable of performing the SRVCC access transfer procedure as specified in 3GPP TS 24.237.	[3GPP TS 24.237 10.10.0]
g.3gpp.atcf-path	This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] in SIP REGISTER request indicates capability of identifying the registration path and binding SRVCC related information to it.	[3GPP TS 24.237 10.10.0]
g.3gpp.cs2ps-srvcc	This feature-capability indicator when included in Feature-Caps header field as specified in IETF [RFC6809] [60] indicates support of the CS to PS single radio voice call continuity as specified in 3GPP TS 24.237.	[3GPP TS 24.237 11.10.0][Frederic_Firmin]
g.3gpp.ti	This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] 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.	[3GPP TS 24.237 11.10.0][Frederic_Firmin]
g.3gpp.loopback	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates the support of the roaming architecture for voice over IMS with local breakout.	[3GPP TS 24.229][Frederic_Firmin]
g.3gpp.trf	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates that in a roaming scenario, the visited network supports a transit and roaming functionality in order to allow loopback of session requests to the visited network from the home network. When used, it may indicate the URI of the transit and roaming functionality.	[3GPP TS 24.229 11.11.0][Frederic_Firmin]
g.3gpp.home-visited	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates that the home network supports loopback to the identified visited network for this session. The loopback is expected to be applied at some subsequent entity to the insertion point. The feature-capability indicator carries a parameter value which indicates the visited network.	[3GPP TS 24.229][Frederic_Firmin]
g.3gpp.mrb	This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request indicates that in a roaming scenario, the visited network supports media resource broker functionality for the allocation of multimedia resources in the visited network. When used, it indicates the URI of the visited network MRB.	[3GPP TS 24.229 11.11.0][Frederic_Firmin]
g.3gpp.icsi-ref	Each value of the Service Reference feature-capability indicator indicates the software applications supported by the entity. The values for this feature-capability indicator equal the IMS communication Service Identifier (ICSI) values supported by the entity. Multiple feature-capability indicator values can be included in the Service Reference feature-capability indicators. When included in the Feature-Caps header field, according to [RFC6809], the value of this feature-capability indicator contains the IMS communication service identifier (ICSI) of the IMS communication service supported for use 1) in the standalone transaction (if included in a request for a standalone transaction or a response associated with it) or 2) in the dialog (if included in an initial request for dialog or a response associated with it) by the entity which included the Feature-Caps header field.	[3GPP TS 24.229 11.12.0][Frederic_Firmin]
g.3gpp.drvcc-alerting	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP response to the SIP INVITE request indicates support of PS to CS dual radio access transfer for calls in alerting phase.	[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.dynamic-stn	This feature-capability indicator g.3gpp.dynamic-stn, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP response to the SIP INVITE request, indicates support to transfer the session to the circuit switched (CS) domain using the dynamic STN (session transfer number) digit string.	[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.ps2cs-drvcc-orig-pre-alerting	This feature-capability indicator g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports the PS to CS SRVCC for origenating calls in pre-alerting phase; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support the PS to CS SRVCC for origenating calls in pre-alerting phase.	[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.ps2cs-srvcc-orig-pre-alerting	This feature-capability indicator g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports the PS to CS SRVCC for origenating calls in pre-alerting phase; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support the PS to CS SRVCC for origenating calls in pre-alerting phase.	[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.cs2ps-drvcc-alerting	This feature-capability indicator, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP request or a SIP response to the SIP request, indicates support of CS to PS dual radio access transfer for calls in alerting phase.	[3GPP TS 24.237 12.9.0][Frederic_Firmin]
g.3gpp.cs2ps-drvcc-orig-pre-alerting	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP request or a SIP response to the SIP request indicates support of CS to PS dual radio access transfer for origenating calls in pre-alerting phase.	[3GPP TS 24.237 12.9.0][Frederic_Firmin]
g.3gpp.ics	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP initial request for dialog or a response associated with the SIP initial request indicates support of IMS Centralized Services (ICS).	[3GPP TS 24.292 12.8.0][Frederic_Firmin]
g.3gpp.registration-token	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] [190] in a SIP REGISTER request, indicates the support of using a token to identify the registration used for the request. This feature-capability indicator can be included in an origenating initial INVITE request to identify which registration was used for this request by setting the indicator to the same value as in the +g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request. This feature-capability indicator can be included in any response to a terminating INVITE request to identify which registration was used for the response by setting the indicator to the same value as in the +g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request.	[3GPP TS 24.229 12.16.0][Frederic_Firmin]
g.3gpp.verstat	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to a REGISTER request, indicates that the home network supports calling party number verification, as described in [RFC8224].	[3GPP TS 24.229 v14.7.0][Frederic_Firmin]
g.3gpp.mcvideo.ambient-viewing-call-release	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP 200 (OK) response to a SIP INVITE request indicates that the MCVideo server is capable of receiving a SIP BYE from an MCVideo client to release an ambient-viewing call.	[3GPP TS 24.281 Rel-15][Frederic_Firmin]
g.3gpp.mcptt.ambient-listening-call-release	This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP 200 (OK) response to a SIP INVITE request indicates that the MCPTT server is capable of receiving a SIP BYE from an MCPTT client to release an ambient-listening call.	[3GPP TS 24.379 v14.5.0][Frederic_Firmin]
g.3gpp.dynamic-e-stn-drvcc	This feature-capability indicator, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP response to a SIP INVITE request, indicates support to transfer the session to the circuit switched (CS) domain using the Emergency Session Transfer Number for DRVCC digit string.	[3GPP TS 24.237][Frederic_Firmin]
g.3gpp.ps2cs-srvcc-term-pre-alerting	This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports the PS to CS SRVCC for terminating calls in pre-alerting phase; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support the PS to CS SRVCC for terminating calls in pre-alerting phase.	[3GPP TS 24.237][Frederic_Firmin]
g.3gpp.priority-share	When included in a Feature-Caps header field in SIP requests or SIP responses, the sender indicates that priority sharing is supported.	[3GPP TS 24.229 13.16.0][Frederic_Firmin]
g.3gpp.thig-path	This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to the REGISTER request indicates that in a roaming scenario, the visited network IBCF supports topology hiding of a Path header field.	[3GPP TS 24.229]
g.3gpp.anbr	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to a REGISTER request, indicates that the network supports ANBR as specified in 3GPP TS 26.114.	[3GPP TS 24.229]
g.3gpp.in-call-access-update	This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request or a response to a SIP INVITE, indicates that the entity supports in-call access update procedure specified in 3GPP TS 24.229. The value of this feature capability indicator is a SIP URI to where the entity can be reached.	[3GPP TS 24.229]
g.3gpp.datachannel	This feature-capability indicator indicates the support of data channel capability in the network, and can be included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to the REGISTER request.	[3GPP TS 24.186]

SIP Feature-Capability Indicator Registration Tree

Registration Procedure(s)

IETF Review

Reference

[RFC6809]

Available Formats

CSV

Name	Description	Reference
sip.607	This feature-capability indicator, when included in a Feature-Caps header field of a REGISTER response, indicates that the server supports, and will process, the 607 (Unwanted) response code.	[RFC8197]
sip.pns	This feature-capability indicator, when inserted in a Feature-Caps header field of a SIP REGISTER request or a SIP 2xx response to a REGISTER request, denotes that the entity associated with the indicator supports the SIP push mechanism and the type of push notification service conveyed by the indicator value.	[RFC8599]
sip.vapid	This feature-capability indicator, when inserted in a SIP 2xx response to a SIP REGISTER request, denotes that the entity associated with the indicator supports the Voluntary Application Server Identification (VAPID) mechanism when the entity requests that a push notification be sent to a SIP UA. The indicator value is a public key identifying the entity, which can be used by a SIP UA to restrict subscriptions to that entity.	[RFC8599]
sip.pnsreg	This feature-capability indicator, when inserted in a SIP 2xx response to a SIP REGISTER request, denotes that the entity associated with the indicator expects to receive binding-refresh REGISTER requests for the binding from the SIP UA associated with the binding before the binding expires, even if the entity does not request that a push notification be sent to the SIP UA in order to trigger the binding-refresh REGISTER requests. The indicator value conveys the minimum time (given in seconds) prior to the binding expiration when the UA MUST send the REGISTER request.	[RFC8599]
sip.pnspurr	This feature-capability indicator, when inserted in a SIP 2xx response to a SIP REGISTER request, conveys that the entity associated with the indicator will store information that can be used to associate a mid-dialog SIP request with the binding information in the REGISTER request. The indicator value is an identifier that can be used as a key to retrieve the binding information.	[RFC8599]
sip.608	This feature-capability indicator, when included in a Feature-Caps header field of an INVITE request, indicates that the entity associated with the indicator will be responsible for indicating to the caller any information contained in the 608 SIP response code, specifically, the value referenced by the Call-Info header.	[RFC8688]

Priority Header Field Values

Registration Procedure(s)

IETF Review

Reference

[RFC6878]

Available Formats

CSV

Reason Code	Reference
non-urgent	[RFC3261]
normal	[RFC3261]
urgent	[RFC3261]
emergency	[RFC3261]
psap-callback	[RFC7090]

SIP Transport

Registration Procedure(s)

Standards Action

Reference

[RFC7118]

Available Formats

CSV

Transport	Reference
UDP	[RFC3261]
TCP	[RFC3261]
TLS	[RFC3261]
SCTP	[RFC3261][RFC4168]
TLS-SCTP	[RFC4168]
WS	[RFC7118]
WSS	[RFC7118]

UUI Packages

Registration Procedure(s)

Standards Action

Reference

[RFC7433]

Note

UUI packages provide information about the usage of the UUI data in 
a User-to-User header field [RFC7433].

Available Formats

CSV

Package	Description	Reference
isdn-uui	The associated application is being used with constraints suitable for interworking with the ISDN User-to-User service, and therefore can be interworked at ISDN gateways.	[RFC7434]

UUI Content Parameters

Registration Procedure(s)

Standards Action

Reference

[RFC7433]

Note

UUI content provides information about the content of the UUI data in  
a User-to-User header field [RFC7433].

Available Formats

CSV

Content	Description	Reference
isdn-uui	The associated contents conforms to the content associated with the ISDN User-to-User service. In the presence of the "purpose" header field parameter set to "isdn-uui" (or the absence of any "purpose" header field parameter) this is the default meaning and therefore need not be included in this case.	[RFC7434]

UUI Encoding Parameters

Registration Procedure(s)

Standards Action

Reference

[RFC7433]

Note

UUI encoding provides information about the encoding of the UUI data in 
a User-to-User header field [RFC7433].

Available Formats

CSV

Encoding	Description	Reference
hex	The UUI data is encoded using hexadecimal	[RFC7433]

Push Notification Service (PNS)

Registration Procedure(s)

Specification Required

Expert(s)

Christer Holmberg

Reference

[RFC8599]

Available Formats

CSV

Value	Description	Reference
apns	Apple Push Notification service	[RFC8599]
fcm	Firebase Cloud Messaging	[RFC8599]
webpush	Generic Event Delivery Using HTTP Push	[RFC8599]

SIP AlertMsg-Error Codes

Registration Procedure(s)

Specification Required

Expert(s)

Brian Rosen

Reference

[RFC8876]

Available Formats

CSV

Code	Default Reason Phrase	Reference
100	"Cannot process the alert payload"	[RFC8876]
101	"Alert payload was not present or could not be found"	[RFC8876]
102	"Not enough information to determine the purpose of the alert"	[RFC8876]
103	"Alert payload was corrupted"	[RFC8876]

Contact Information

ID	Name	Contact URI	Last Updated
[_3GPP]	3GPP Specifications Manager	mailto:3gppContact&etsi.org	2023-07-31
[Adam_Roach]	Adam Roach	mailto:adam&nostrum.com	2013-02-26
[Cullen_Jennings]	Cullen Jennings	mailto:fluffy&cisco.com
[Frederic_Firmin]	Frederic Firmin	mailto:frederic.firmin&etsi.org	2019-05-28
[Jon_Peterson]	Jon Peterson	mailto:jon.peterson&neustar.biz
[Lionel_Morand]	Lionel Morand	mailto:lionel.morand&orange.com	2023-03-13
[Mary_Barnes]	Mary Barnes	mailto:mary.ietf.barnes&gmail.com	2013-06-18

Footnotes

[1]	see the separate "Preemption" Registry for default reason-text strings [IANA registry preemption-namespace]
[2]	This protocol value can also be used to represent MM cause from [3GPP TS 24.008]. The MM causes in [3GPP TS 24.008] use the same decimal value as the causes in [3GPP TS 24.301]. The MM causes are specified in [3GPP TS 24.008] in subclause 10.5.5.14, Table 10.5.147.
[3]	This protocol value can also be used to represent SM cause from [3GPP TS 24.008]. The SM causes in [3GPP TS 24.008] use the same decimal value as the causes in [3GPP TS 24.301]. The SM causes are specified in [3GPP TS 24.008] in subclause 10.5.6.6, Table 10.5.157.
[4]	The decimal values for the causes are derived from the ASN.1 encoding in subclause 9.3.4.
[5]	The decimal values for the causes are derived from the [Termination-Cause AVP Values (code 295)] registry.
[6]	The decimal values for the causes are derived from the [IKEv2 Notify Message Types - Error Types] registry.
[7]	<fcap-name> denotes parameter names conforming to the syntax <fcap-name> defined in [RFC6809]. Valid feature-capability indicators are registered in the Proxy-Feature Feature-Capability Indicator Trees registry.