Internet Assigned Numbers Authority Session Initiation Protocol (SIP) Parameters Created 2002-01 Last Updated 2025-07-11 Available Formats [IMG] XML [IMG] HTML [IMG] Plain text Registries Included Below ??Header Fields ??Reason Protocols ??Option Tags ??Warning Codes (warn-codes) ??Methods and Response Codes ??Response Codes ??SIP Privacy Header Field Values ??Security Mechanism Names ??Compression Schemes ??SIP/SIPS URI Parameters ??Header Field Parameters and Parameter Values ??URI Purposes ??Resource-Priority Namespaces ??Resource-Priority Priority-values ??Namespace: drsn ??Namespace: dsn ??Namespace: q735 ??Namespace: ets ??Namespace: wps ??Namespace: dsn-000000 ??Namespace: dsn-000001 ??Namespace: dsn-000002 ??Namespace: dsn-000003 ??Namespace: dsn-000004 ??Namespace: dsn-000005 ??Namespace: dsn-000006 ??Namespace: dsn-000007 ??Namespace: dsn-000008 ??Namespace: dsn-000009 ??Namespace: drsn-000000 ??Namespace: drsn-000001 ??Namespace: drsn-000002 ??Namespace: drsn-000003 ??Namespace: drsn-000004 ??Namespace: drsn-000005 ??Namespace: drsn-000006 ??Namespace: drsn-000007 ??Namespace: drsn-000008 ??Namespace: drsn-000009 ??Namespace: rts-000000 ??Namespace: rts-000001 ??Namespace: rts-000002 ??Namespace: rts-000003 ??Namespace: rts-000004 ??Namespace: rts-000005 ??Namespace: rts-000006 ??Namespace: rts-000007 ??Namespace: rts-000008 ??Namespace: rts-000009 ??Namespace: crts-000000 ??Namespace: crts-000001 ??Namespace: crts-000002 ??Namespace: crts-000003 ??Namespace: crts-000004 ??Namespace: crts-000005 ??Namespace: crts-000006 ??Namespace: crts-000007 ??Namespace: crts-000008 ??Namespace: crts-000009 ??Namespace: esnet ??Namespace: mcpttp ??Namespace: mcpttq ??Identity Parameters ??Identity-Info Algorithm Parameter Values ??SIP Forum User Agent Configuration Parameters ??Service-ID/Application-ID Labels ??Info Packages Registry ??SIP Configuration Profile Types ??Geolocation-Error Codes ??Reason Codes ??Proxy-Feature Feature-Capability Indicator Trees ??Global Feature-Capability Indicator Registration Tree ??SIP Feature-Capability Indicator Registration Tree ??Priority Header Field Values ??SIP Transport ??UUI Packages ??UUI Content Parameters ??UUI Encoding Parameters ??Push Notification Service (PNS) ??SIP AlertMsg-Error Codes 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 [IMG] 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] Security-Client [RFC3329] Security-Server [RFC3329] Security-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 [IMG] 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 [3GPP?TS?29.274 subclause?8.103][5][_3GPP] representation in decimal digits of the received binary value. IKEV2 Cause for protocol failure of IKEV2 supporting untrusted WLAN, as a [3GPP?TS?29.274 subclause?8.103][6][_3GPP] representation in decimal digits of the received binary value. cause value 1: User ends call cause value 2: RTP/RTCP time-out cause value 3: Media bearer loss RELEASE_CAUSE cause value 4: SIP timeout - no ACK [3GPP?TS?24.229] cause value 5: SIP response time-out cause value 6: Call-setup time-out cause value 7: Redirection failure cause value 1: Media bearer or QoS lost FAILURE_CAUSE cause value 2: Release of signalling bearer [3GPP?TS?24.229 v14.4.0][Frederic_Firmin] cause value 3: Indication of failed resources allocation 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 [IMG] CSV Name Description Reference This option tag is for reliability of provisional responses. When present in a Supported header, it indicates 100rel that the UA can send or receive reliable provisional responses. When present in a Require header in a request [RFC3262] 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. This option-tag is for indicating support of the 199 Early Dialog Terminated provisional response code. When 199 present in a Supported header of a request, it indicates that the UAC supports the 199 response code. When [RFC6228] 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. answermode This option tag is for support of the Answer-Mode and Priv-Answer-Mode extensions used to negotiate automatic [RFC5373] or manual answering of a request. early-session A UA adding the early-session option tag to a message indicates that it understands the early-session content [RFC3959] disposition. 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 [RFC7614] an explicit subscription. from-change This option tag is used to indicate that a UA supports changes to URIs in From and To header fields during a [RFC4916] dialog. The "geolocation-http" option tag signals support for acquiring location information via an HTTP [RFC2616]. A geolocation-http location recipient who supports this option can request location with an HTTP GET and parse a resulting 200 [RFC6442] response containing a PIDF-LO object. The URI schemes supported by this option include "http" and "https". The "geolocation-sip" option tag signals support for acquiring location information via the presence event geolocation-sip package of SIP [RFC3856]. A location recipient who supports this option can send a SUBSCRIBE request and [RFC6442] parse a resulting NOTIFY containing a PIDF-LO object. The URI schemes supported by this option include "sip", "sips", and "pres". This option tag is used to identify the extension that provides Registration for Multiple Phone Numbers in gin SIP. When present in a Require or Proxy-Require header field of a REGISTER request, it indicates that support [RFC6140] for this extension is required of registrars and proxies, respectively, that are a party to the registration transaction. This option tag is used to identify the Globally Routable User Agent URI (GRUU) extension. When used in a gruu Supported header, it indicates that a User Agent understands the extension. When used in a Require header [RFC5627] field of a REGISTER request, it indicates that the registrar is not expected to process the registration unless it supports the GRUU extension. When used with the Supported header field, this option tag indicates the UAC supports the History Information histinfo to be captured for requests and returned in subsequent responses. This tag is not used in a Proxy-Require or [RFC7044] Require header field, since support of History-Info is optional. ice This option tag is used to identify the Interactive Connectivity Establishment (ICE) extension. When present [RFC5768] in a Require header field, it indicates that ICE is required by an agent. 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 [RFC5368] multiple REFER targets. norefersub This option tag specifies a User Agent ability of accepting a REFER request without establishing an implicit [RFC4488] subscription (compared to the default case defined in [RFC3515]. nosub This option tag identifies an extension to REFER to suppress the implicit subscription and indicate that no [RFC7614] explicit subscription is forthcoming. This option-tag is used to identify UAs and Registrars which support extensions for Client Initiated outbound Connections. A UA places this option in a Supported header to communicate its support for this extension. A [RFC5626] 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. 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 path this option tag in a REGISTER request to determine whether to offer Path service for for that request. If an [RFC3327] 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. policy This option tag is used to indicate that a UA can process policy server URIs for and subscribe to [RFC6794] session-specific policies. An offerer MUST include this tag in the Require header field if the offer contains one or more "mandatory" precondition strength-tags. If all the strength-tags in the description are "optional" or "none" the offerer MUST include [RFC3312] this tag either in a Supported header field or in a Require header field. pref This option tag is used to ensure that a server understands the callee capabilities parameters used in the [RFC3840] request. This option tag indicates support for the Privacy mechanism. When used in the Proxy-Require header, it privacy indicates that proxy servers do not forward the request unless they can provide the requested privacy [RFC3323] 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. 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 [RFC5367] request. This option tag is to indicate the ability of the UA to receive recording indicators in media-level or record-aware session-level SDP. When present in a Supported header, it indicates that the UA can receive recording [RFC7866] indicators in media-level or session-level SDP. replaces This option tag indicates support for the SIP Replaces header. [RFC3891] resource-priority Indicates or requests support for the resource priority mechanism. [RFC4412] The option-tag sdp-anat is defined for use in the Require and Supported SIP [RFC3261] header fields. SIP user sdp-anat agents that place this option-tag in a Supported header field understand the ANAT semantics as defined in [RFC4092] [RFC4091]. This option tag indicates support for the Security Agreement mechanism. When used in the Require, or Proxy-Require headers, it indicates that proxy servers are required to use the Security Agreement mechanism. sec-agree When used in the Supported header, it indicates that the User Agent Client supports the Security Agreement [RFC3329] mechanism. When used in the Require header in the 494 (Security Agreement Required) or 421 (Extension Required) responses, it indicates that the User Agent Client must use the Security Agreement Mechanism. This option tag is for identifying that the SIP session is for the purpose of an RS. This is typically not siprec used in a Supported header. When present in a Require header in a request, it indicates that the UA is either [RFC7866] an SRC or SRS capable of handling a recording session. This option tag is used to identify the target dialog header field extension. When used in a Require header tdialog field, it implies that the recipient needs to support the Target-Dialog header field. When used in a [RFC4538] Supported header field, it implies that the sender of the message supports it. 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. timer Inclusion in a Require header in a request means that the UAS must understand the session timer extension to [RFC4028] 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. 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 [IMG] 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 [RFC8373] languages and media]. 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 [RFC3261] a firewall). 370 Insufficient bandwidth: The bandwidth specified in the session description or defined by the media exceeds that known to be [RFC3261] available. 380 SIPS Not Allowed: The UAS or proxy cannot process the request because the SIPS scheme is not allowed (e.g., because there are [RFC5630] currently no registered SIPS Contacts). 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 [RFC3261] receiving this warning MUST NOT take any automated action. Methods and Response Codes Registration Procedure(s) Standards Action Reference [RFC3261][RFC5727] Available Formats [IMG] 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 [IMG] 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 Security 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 [IMG] 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] Security Mechanism Names Registration Procedure(s) IETF Review Reference [RFC3329] Available Formats [IMG] 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 [IMG] CSV Compression Scheme Token Reference Signaling Compression sigcomp [RFC3486] SIP/SIPS URI Parameters Registration Procedure(s) Standards Action Reference [RFC3969][RFC5727] Available Formats [IMG] 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 [IMG] CSV Header Field Parameter Name Predefined Reference Values 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 call-reason No [RFC9796] Call-Info integrity No [RFC9796] Call-Info m Yes [RFC6910] Call-Info purpose Yes [RFC3261][RFC5367][RFC6910][RFC6993][RFC7082][RFC7852][RFC8688][RFC9248][RFC9796] Call-Info verified Yes [RFC9796] 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] Security-Client alg Yes [RFC3329] Security-Client ealg Yes [RFC3329] Security-Client d-alg Yes [RFC3329] Security-Client d-qop Yes [RFC3329] Security-Client d-ver No [RFC3329] Security-Client mod Yes [RFC3329] Security-Client port1 No [RFC3329] Security-Client port2 No [RFC3329] Security-Client prot Yes [RFC3329] Security-Client q No [RFC3329] Security-Client spi No [RFC3329] Security-Server alg Yes [RFC3329] Security-Server ealg Yes [RFC3329] Security-Server d-alg Yes [RFC3329] Security-Server d-qop Yes [RFC3329] Security-Server d-ver No [RFC3329] Security-Server mod Yes [RFC3329] Security-Server port1 No [RFC3329] Security-Server port2 No [RFC3329] Security-Server prot Yes [RFC3329] Security-Server q No [RFC3329] Security-Server spi No [RFC3329] Security-Verify alg Yes [RFC3329] Security-Verify ealg Yes [RFC3329] Security-Verify d-alg Yes [RFC3329] Security-Verify d-qop Yes [RFC3329] Security-Verify d-ver No [RFC3329] Security-Verify mod Yes [RFC3329] Security-Verify port1 No [RFC3329] Security-Verify port2 No [RFC3329] Security-Verify prot Yes [RFC3329] Security-Verify q No [RFC3329] Security-Verify spi No [RFC3329] No (no Session-ID logme values are [RFC8497] allowed) 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] CSV 'alg' Parameter Name Reference rsa-sha1 [RFC4474] rsa-sha256 [RFC6072] SIP Forum User Agent Configuration Parameters Reference [RFC6011] Available Formats [IMG] CSV Range Registration Procedures begins with 'sfua-' RFC Required all other names First Come First Served Parameter Name Description Reference 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 sfua-id construct a value for this parameter, the sfua-id parameter MUST always be included. If the UA implements [RFC5626], [RFC6011] 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. An identifier for a user associated with the configuration. Note that this might be different than any SIP 'user' in sfua-user the UA configuration: it could, for example, be the login name of an account on the service provider web site. The [RFC6011] 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. 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 [RFC6011] domain. The domain value MUST be that of a domain owned by the vendor. 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 [RFC6011] this parameter is the same as the [RFC3261] 'token'. Values for this parameter are selected by the vendor. Service-ID/Application-ID Labels Registration Procedure(s) Specification Required Expert(s) Unassigned Reference [RFC6050] Available Formats [IMG] 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 [RFC6050] does not define a service and requires subsequent labels to define the service. 3gpp-application Applications defined by 3GPP for use by UAs attached to the IM CN subsystem. This value in itself does not define [RFC6050] a service and requires subsequent labels to define the service. Info Packages Registry Registration Procedure(s) Specification Required Expert(s) Adam Roach Reference [RFC6086] Available Formats [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] 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 [IMG] CSV Name Description Reference This feature-capability indicator when used in a Feature-Caps g.3gpp.iut-focus header field of a SIP request or a SIP response indicates that the [3GPP TS 24.337 10.7.0] function which inserted the Feature-Caps header field supports anchoring an IUT session. 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 g.3gpp.mid-call in the SIP message supports the MSC server assisted mid-call [3GPP TS 24.237 10.10.0] 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. This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP REGISTER g.3gpp.atcf request or a SIP response to the SIP REGISTER request indicates [3GPP TS 24.237 10.10.0] presence and support of a resource which is an Access Transfer Control Function (ATCF) and also the session transfer number allocated to the ATCF. 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 g.3gpp.srvcc-alerting in the SIP message supports access transfer for calls in alerting [3GPP TS 24.237 10.10.0] 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. This feature-capability indicator when used in a Feature-Caps g.3gpp.atcf-mgmt-uri header field as specified in IETF [RFC6809] [60] in SIP REGISTER [3GPP TS 24.237 10.10.0] request indicates presence and support of performing as a UAS for SIP requests for ATCF management received at this URI. This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] of: - a SIP INVITE g.3gpp.srvcc request; or - a SIP INVITE response; indicates presence and [3GPP TS 24.237 10.10.0] support of a resource capable of performing the SRVCC access transfer procedure as specified in 3GPP TS 24.237. This feature-capability indicator when used in a Feature-Caps g.3gpp.atcf-path header field as specified in IETF [RFC6809] in SIP REGISTER [3GPP TS 24.237 10.10.0] request indicates capability of identifying the registration path and binding SRVCC related information to it. This feature-capability indicator when included in Feature-Caps g.3gpp.cs2ps-srvcc header field as specified in IETF [RFC6809] [60] indicates support [3GPP TS 24.237 of the CS to PS single radio voice call continuity as specified in 11.10.0][Frederic_Firmin] 3GPP TS 24.237. This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] in SIP INVITE request [3GPP TS 24.237 g.3gpp.ti or SIP response to the SIP INVITE request indicates the capability 11.10.0][Frederic_Firmin] of associating a CS call with dialog created by the SIP INVITE request. This feature-capability indicator, when included in a Feature-Caps g.3gpp.loopback header field as specified in [RFC6809] in a SIP INVITE request, [3GPP TS 24.229][Frederic_Firmin] indicates the support of the roaming architecture for voice over IMS with local breakout. 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 [3GPP TS 24.229 g.3gpp.trf a transit and roaming functionality in order to allow loopback of 11.11.0][Frederic_Firmin] session requests to the visited network from the home network. When used, it may indicate the URI of the transit and roaming functionality. 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 g.3gpp.home-visited identified visited network for this session. The loopback is [3GPP TS 24.229][Frederic_Firmin] 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. This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request g.3gpp.mrb indicates that in a roaming scenario, the visited network supports [3GPP TS 24.229 media resource broker functionality for the allocation of 11.11.0][Frederic_Firmin] multimedia resources in the visited network. When used, it indicates the URI of the visited network MRB. 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. g.3gpp.icsi-ref When included in the Feature-Caps header field, according to [3GPP TS 24.229 [RFC6809], the value of this feature-capability indicator contains 11.12.0][Frederic_Firmin] 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. This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE [3GPP TS 24.237 g.3gpp.drvcc-alerting request or a SIP response to the SIP INVITE request indicates 12.8.0][Frederic_Firmin] support of PS to CS dual radio access transfer for calls in alerting phase. This feature-capability indicator g.3gpp.dynamic-stn, when included in a Feature-Caps header field as specified in IETF g.3gpp.dynamic-stn [RFC6809] in a SIP INVITE request or a SIP response to the SIP [3GPP TS 24.237 INVITE request, indicates support to transfer the session to the 12.8.0][Frederic_Firmin] circuit switched (CS) domain using the dynamic STN (session transfer number) digit string. 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 g.3gpp.ps2cs-drvcc-orig-pre-alerting in the SIP message supports the PS to CS SRVCC for originating [3GPP TS 24.237 calls in pre-alerting phase; and 2. all entities of which the 12.8.0][Frederic_Firmin] 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 originating calls in pre-alerting phase. 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 g.3gpp.ps2cs-srvcc-orig-pre-alerting in the SIP message supports the PS to CS SRVCC for originating [3GPP TS 24.237 calls in pre-alerting phase; and 2. all entities of which the 12.8.0][Frederic_Firmin] 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 originating calls in pre-alerting phase. This feature-capability indicator, when included in a Feature-Caps g.3gpp.cs2ps-drvcc-alerting header field as specified in IETF [RFC6809] in a SIP request or a [3GPP TS 24.237 SIP response to the SIP request, indicates support of CS to PS 12.9.0][Frederic_Firmin] dual radio access transfer for calls in alerting phase. This feature-capability indicator when included in a Feature-Caps g.3gpp.cs2ps-drvcc-orig-pre-alerting header field as specified in IETF [RFC6809] in a SIP request or a [3GPP TS 24.237 SIP response to the SIP request indicates support of CS to PS dual 12.9.0][Frederic_Firmin] radio access transfer for originating calls in pre-alerting phase. This feature-capability indicator when included in a Feature-Caps g.3gpp.ics header field as specified in IETF [RFC6809] in a SIP initial [3GPP TS 24.292 request for dialog or a response associated with the SIP initial 12.8.0][Frederic_Firmin] request indicates support of IMS Centralized Services (ICS). 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 originating initial INVITE request to identify which registration was used for this request by g.3gpp.registration-token setting the indicator to the same value as in the [3GPP TS 24.229 +g.3gpp.registration-token media feature tag in the Contact header 12.16.0][Frederic_Firmin] 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. This feature-capability indicator, when included in a Feature-Caps g.3gpp.verstat header field as specified in [RFC6809] in a 200 (OK) response to a [3GPP TS 24.229 REGISTER request, indicates that the home network supports calling v14.7.0][Frederic_Firmin] party number verification, as described in [RFC8224]. This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE [3GPP TS 24.281 g.3gpp.mcvideo.ambient-viewing-call-release request or a SIP 200 (OK) response to a SIP INVITE request Rel-15][Frederic_Firmin] indicates that the MCVideo server is capable of receiving a SIP BYE from an MCVideo client to release an ambient-viewing call. This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE [3GPP TS 24.379 g.3gpp.mcptt.ambient-listening-call-release request or a SIP 200 (OK) response to a SIP INVITE request v14.5.0][Frederic_Firmin] indicates that the MCPTT server is capable of receiving a SIP BYE from an MCPTT client to release an ambient-listening call. This feature-capability indicator, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP response to a g.3gpp.dynamic-e-stn-drvcc SIP INVITE request, indicates support to transfer the session to [3GPP TS 24.237][Frederic_Firmin] the circuit switched (CS) domain using the Emergency Session Transfer Number for DRVCC digit string. 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 g.3gpp.ps2cs-srvcc-term-pre-alerting calls in pre-alerting phase; and 2. all entities of which the [3GPP TS 24.237][Frederic_Firmin] 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. When included in a Feature-Caps header field in SIP requests or [3GPP TS 24.229 g.3gpp.priority-share SIP responses, the sender indicates that priority sharing is 13.16.0][Frederic_Firmin] supported. This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to g.3gpp.thig-path the REGISTER request indicates that in a roaming scenario, the [3GPP TS 24.229] visited network IBCF supports topology hiding of a Path header field. This feature-capability indicator, when included in a Feature-Caps g.3gpp.anbr header field as specified in [RFC6809] in a 200 (OK) response to a [3GPP TS 24.229] REGISTER request, indicates that the network supports ANBR as specified in 3GPP TS 26.114. This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request or g.3gpp.in-call-access-update a response to a SIP INVITE, indicates that the entity supports [3GPP TS 24.229] 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. This feature-capability indicator indicates the support of data g.3gpp.datachannel channel capability in the network, and can be included in a [3GPP TS 24.186] Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to the REGISTER request. SIP Feature-Capability Indicator Registration Tree Registration Procedure(s) IETF Review Reference [RFC6809] Available Formats [IMG] 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 [RFC8197] server supports, and will process, the 607 (Unwanted) response code. This feature-capability indicator, when inserted in a Feature-Caps header field of a SIP REGISTER request or a SIP 2xx sip.pns response to a REGISTER request, denotes that the entity associated with the indicator supports the SIP push mechanism and [RFC8599] the type of push notification service conveyed by the indicator value. This feature-capability indicator, when inserted in a SIP 2xx response to a SIP REGISTER request, denotes that the entity sip.vapid associated with the indicator supports the Voluntary Application Server Identification (VAPID) mechanism when the entity [RFC8599] 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. 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 sip.pnsreg associated with the binding before the binding expires, even if the entity does not request that a push notification be [RFC8599] 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. This feature-capability indicator, when inserted in a SIP 2xx response to a SIP REGISTER request, conveys that the entity sip.pnspurr associated with the indicator will store information that can be used to associate a mid-dialog SIP request with the [RFC8599] binding information in the REGISTER request. The indicator value is an identifier that can be used as a key to retrieve the binding information. This feature-capability indicator, when included in a Feature-Caps header field of an INVITE request, indicates that the sip.608 entity associated with the indicator will be responsible for indicating to the caller any information contained in the 608 [RFC8688] SIP response code, specifically, the value referenced by the Call-Info header. Priority Header Field Values Registration Procedure(s) IETF Review Reference [RFC6878] Available Formats [IMG] 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 [IMG] 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 [IMG] 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 [RFC7434] therefore can be interworked at ISDN gateways. 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 [IMG] CSV Content Description Reference The associated contents conforms to the content associated with the ISDN User-to-User service. In the presence of the isdn-uui "purpose" header field parameter set to "isdn-uui" (or the absence of any "purpose" header field parameter) this is the [RFC7434] default meaning and therefore need not be included in this case. 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 [IMG] 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 [IMG] 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 [IMG] 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] denotes parameter names conforming to the syntax defined in [RFC6809]. Valid feature-capability indicators are registered in the Proxy-Feature Feature-Capability Indicator Trees registry. Licensing Terms Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù ENTER NUMBET 0016www.hqbcq.com.cn
huachenc.org.cn
jgycos.com.cn
www.jjhgcme.com.cn
www.mkchain.com.cn
www.sohb.com.cn
www.txtx.org.cn
www.vguc.com.cn
www.uycwxg.com.cn
www.nmgqzgwy.org.cn
中文字幕的h电影 xiao 色网 美国女性裸体图片网 最新的成人网站网址 雷丝兔宝宝更新50p 露男人下体的黄色a片有哪些 如月群真贴吧福利图 骚妹影院删除 黑山三高中孟璐 欧美写真在线视频 老色狗网站 父女乱伦纯肉文 八匹狼资源站 屄掰女 操逼都有那电视剧 www三级片cnm 我爱逼另类小说 我和隔壁阿姨黄色小说 人i与动物快播 苍井空【50p】 人与兽黄片视频一级片 耻体少妇 操美女尸体小说 ribennvrendeyindaoyouduochang 美国少女露鲍人体大胆艺术照 女人操屄图片 波多野结衣内射中出快播播放 你的屄毛 摩悦菁艺上海电子有限公司 激情小说美女色图 h幼女小说txt 我爱大学生无码迅雷下载 排球女将24rmvb 欧美女人醉酒露出图片 90后性a网 女性人体艺术狠撸 禄草裙社区 美国拍av的明星 迷奸媳妇舔食淫液小说 WWW_49223_COM 日本空姐被操视频 裸摸骚逼 百度爬灰小说老卫和儿媳 潮吹女王30p 偷拍电影伦理片 西西欧美美女大胆秀人体艺术 3000人体摄影艺术 操幼女小驻逼小说 妹の秘密种子下载 WWW_OMBYY_COM 自拍视频2 我和嫂子的做爱故事 WWW_6186 骚货颜射 美女穴穴高清图片 鸡爸巴插逼视频 三级片黄片做爱片 欧美做爱图片20p 美女淫荡性交图片 色狂い8人娘 木村真理惠 电影 8844ddd 干肉丝袜少妇 爆肏女明星 亚洲 套图 偷拍 WWW_UESSS_COM 欧美美女内衣写真真集 爱贝导航 绿妈文同好交流社区 围城读后感 白酒招商政策 吴苇珊 taijong 香港古装三级bt 掰开蜜穴 av9cc 天涯导航色 快播播放器的黄色网站 男生女生在床糟逼电影 五月天色网偷拍自拍 女人爱操逼怎么办 我与男同事的性爱 三级色色色色网 操逼有害不可大力日比 有什么好看的成人电影网 多淫荡少妇15p segif 鸭哥哥yx日本 明星色巴 影音先锋日本av女优妹妹电影 性感明星大尺度艳照 gayjiaonu 中国肥女人人体 撸一撸6666 伊在爱商城成人色爱 治阳瘘早泄的中药泡酒 色狠久撸啊撸小说 wwwsqo 姐姐图片穴 霪霪网在线视频免费 日本av毛片迅雷种子 变态图区911色色色 美女清纯性撸图 佐藤吉吉影音 黑人狂操亚裔女 heisiyouwu 成人做爱动态视频 色亚小说 夜色视频免费观看20 欧美性交第一会所 伦乱透屄故事 WWW190JCOM 操姨妈导航 西西色老头人体艺术 婶婶你真骚 哥哥干手机小说 美国sex网站导航 日本av三级文学 朋友妈妈巨乳诱惑快播 插骚逼屁眼 876αv电影 WWWANGOULECOM 鸭妹妹子网址 日本落体做爰图片 neishesaoxue ed2k国产熟女 床上草视频 少妇爱爱撸 迅雷在线激情乱伦 刘亦菲合成15p 美女光定身体图片 六六床戏 抽插穴屌流 WWWJNVCOMTLBFE 黄色小说片子 激激色 成人最猛网站视频 寂寞少妇的诱惑最新章节 男主角20年后与女主角重遇的欧美电影 十次啦美国小说 大鸡巴香烟价格 欧美超模被操 WWW66MMDDCOM 少妇挤奶50p 骚女大姨妈来了16p 午夜三级小说快播 亚洲少女性图 张柏芝loub 555电影三级2013118 zooskool经典系列 苍井空ed2k华为 国产母狗 打炮口活美女3g 狠狠碰xxoo成人电影免播放器在线观看 人体模特小游 媳妇浪穴 男人为什么喜欢吃女人逼逼 先锋影院在线观看 幼女养成h文 823824 看性感动漫 这个被操的嗷嗷叫爱色网 成人图片漏图 馒头逼吧 非洲大阴蒂 我爱和老女人做爱 东南亚少女10p 曰本为什么喜欢拍成人片 大美女的鲍鱼被狂插 美女裸体图片欧美色图2010 5252avi xiaoshuocao 百度大尺度美女图片 一起看吧动感之星影音先锋 小孩草大人的小说 色色小说综合 最猛成人网站 ziweiqun 百合纯肉真人电影 优希麻琴女教师 婷婷五月香基地 欧美性爱制度诱惑另类图片 圣诞老人射小妞和强奸小妞动话片 成人世界摸摸你 哥要蝴蝶谷娱乐中文网 日本三级艳星人体艺术 爆乳母娘仙桃影视网 欧美性爱色图网站 色涩黑木耳 韩国美女插洞 xxoo网av在线视频男人天堂 www294caocommsequ1co 欧美骚逼网 夜射狼AV亚洲在线视频 贵阳成人国产自拍 李毅情趣小说 fatgirlchineseav 操姐姐娱乐 欧美人体校园 五月激情乱伦小说网 王者荣耀cosplayav 人妻的淫逼 十大中字无码动漫名字 在线福利社天龙八部 做爱揉捏抽插三级图片 男少年同性插屁眼小说 930影城色色影城 手机看成人动作大片 野猪网俄罗斯理论电影 农村tongjian 表姐穆婷婷 pp55牛叉B电影 2017伦理中文字幕剧情 图解李宗瑞艳照 成人激情运动 色偷偷成人资源站 bqq477看av群 台湾淫荡老婆 优优影视www44pecomwwwseqingyouyou285621cc 插嫩嫩的护士10pwww5zipaicom 加勒比ad 短篇剧情网站 zzz76zycom 现代激情校园春色html 蔡依林邪恶小说 动漫亚洲强奸乱伦magnet porn家教 狠狠操妈妈的穴 亚洲成人网站做爱小视频 wwwdphzrnetcn 94yrocm 妈妈供我上学14利群 印度美女坐脸 韩国肏屄magnet 日韩新片网成人动漫 亚里沙综合 360自拍偷拍自慰小视频 百度厕所偷拍在线视频 西西阴陪人体艺术 性感美女风骚丝袜子 淫乱妈妈王的母亲节 乱伦小说调教性奴表姐 港台bt 人妖超碰XXOO免费视频 绝美学生妹课间女主 p8成人电影网站免费 kaori养母轮奸 黄色电影在哪里获得 人妻武侠第1页 www502日本少妇com 强奸美女秘书黄色小说 爆操美女吉吉 经典有声插插中和网 爱福利撸wwwfulilubacom av办公室ol AV美丽川mxiaomemecom 日本wwwsao 操嫩15p成人 aog里番 找幼破身小说 美女女性交图片 人体裸体metcn庄媛 原沙奈央 捆绑系列20p 和女同事激情做爱 xxoo波多野结衣 松本美影片 幼女性交体会 wwwx32bcxv 大胆人体嫩穴艺术摄影 操嫂子肉逼 就爱大片网的网址 爱我多深ipad在线看 不卡的av52 www999xbxbcom 成熟少妇图片 先锋免费成年电影 超碰四虎网站 AVcooavmoocom 性爱区在现看 龙口门影音先锋在线看 日本女被深喉15P 孙女在厨房内射 狼国48Q 上了白虎姐姐 wwwepornercom 色图动图 激淫15p wwwav三级 人妖丝袜美臀 3P书屋 手机新域名ady手机看片 熟女30pdizhi 水菜丽scute在线 2017狠狠撸最新网址 插b免费视频 姐妹监禁教师 欧美gv下载 WWWSAO117COM 口述我和妹妹的欲望 swwwporndigcom 丝袜姜女操动态图 222bob 翁媳操逼乱伦 男同志AV在线 淫荡明星在线 女生把男生的肉棒放到嘴里 素人妻第1页伦理电影在线观看伦理电影网站伦理聚合 女优舌头舔屏幕av 18福利影院 91视频AV 1238100有毒吗 青青草女用道具在线视频 超碰av免费视频超在线wwwcao077com 伦理片安乐战场 黑人操社区影院导航 志村玲子手机在线观看 激情五月色视频www031ncom 免费看天天A片美女图片免费 1333ccc Wwwdidi319com 精品50p www53cccc 小学生AV910ppcom 色色射撸 偷拍厕所台湾妹中文 wwwsss258com 老淑女逼毛视频 现代激情人妻乱伦 最新热情网页 www路bu780 老婆出轨了搞她比以前水多了 色师傅按摩 东方在线50o 阴蒂小电影 操荔 在线青青视频免费观 色系x小说 99视频久久热视频 乱伦乱奸 亚卅av在线视频 啪啪小说阅读 韩国情侣做爱高清自拍看巨乳多多影音 淫荡乱伦图区 av在线网址l 撸管视频网 女厕拍2014视频 35aaacorn 我爱大咪咪黄片 www89bbecon下载 在洗澡的时候做爱 插逼穴图片 伦理吃奶小说 国产sss视频在线 人妻乱抡小说 97色播五月 大阴茎插进小舅妈 大机巴饶了我吧视频 97122997WYTXXX87627EEEcom 玩弄女星破处 xvideosgratistv另类变态 亚洲变态另类色图天堂网 五月天色色新版图片 熟女乱伦先锋影音 亚洲0xox 色色色色色射射 www色cam 印度成人色图 超碰网址发布野 奸插干网站 omeixingaishicila 姐姐被我插屄 有一个裸聊的直播网页 催情药调教美妇 wwww色五月C0m 偷啪i 搞AV自拍图 xfplay自拍 日本丝袜无码影音先锋播放 淫淫孩子 嫩逼穴成人美女 998zyzco钬唌 色狼色哥哥色姐姐 在线妻子乱轮偷情 欧美辣图沾花网 爽爽在线ab 操妹妹国产 成人嘿咻嘿咻网 深夜福利在线看天上人 老婆卖淫小说 吸白嫩的女人 影音在线久久草 内射学生幼幼 wwwky757com为什么看不了 插插插综合小说网comwwwssss88com 人妻女友之撸撸 日少妇av 肉棒抽查操干图片 慢慢射亚洲色图 nnyythunder 影音先锋网制服丝袜 乱伦阿姨AV在线 两个男人一起自慰 免插件高清合集 大鸡巴用力操激情性爱 很骚的MⅤ 魔王在线iav99 好看站手机站版 双插另类 欧美一级黄色大片 噜噜哭 成人网站成人色图成人视频 色罗莉怎么看不了了 操已婚情人在线视频 闹洞房就去干 野外性交xxxx 欧美女人潮吹视频在线观看 酒色哥我爱撸 少妇 熟女 聚会 生活照自拍 照片 丰满 性感 皇瑟luan lun 成人色视频网 换妻俱乐部4p无码照片 小草影视龚iue菲新金瓶电影先锋 校园春色乱轮 网盘下载 国产a片 狗骚女 强叉美女小穴 无马欧美 张筱雨人体去术精选 丝袜妹妹求我插 女孩 做爱 自拍 几月采阴陈 时间暂停器全套12部 乱伦小说女婿与丈母娘 长筒袜做爱图片 骚屄3p 少妇巨乳诱惑影音先锋 夜夜斎颂逡帐? 全祼体女张筱雨 四房色播五月天色小姐 最新肥胖人体艺术摄影 仓井空巨乳女教师 强根宝有没有用 插大奶胖逼 兽交片小说 0809嫩逼导航 肉丝少妇狠狠撸 农村淫乱做爱 d2e487f00000079f 操淫荡小姨子 自拍操穴 美女最大胆裸体艺术写真 影音先锋溜冰影院 插阴道人体艺术大图大全 帕丽斯希尔顿哈佛一夜性爱录象带影音先锋 动物jiao 淫荡诛仙 熟妇中出哥哥射俺去撸 姬岛琉璃种子 少妇粉红鲍鱼穴 韩国女主播之香淑影音先锋 女教师与学生性交网盘 第一会所亚洲无码熟女 韩国裸体性交 26uuu图片 能播放的欧美群交视频 咸色小说 幼逼百图 全裸掰开逼逼大尺度人体艺术 日本动作片 百度网盘 求大奶大屁股的视频 迷奸迷奸快播电影免费欣赏 国语对白影音先锋手机 成人性生活网址 轮里涩涩 实况足球8补丁 全职猎人348 卡索 高清沟厕偷拍 熟女先锋 30p亚洲性交 黑人草亚洲美女大鸡巴 美女美女我要插逼逼18p 偸拍野站视频 全裸日本充气娃娃照片 老女人露脸口交哥必撸 tubi8中国三级 人体艺术芭离 老师孙老头看看你的内部拍的照片 色妹妹丁香社区妞妞 善良的美人妇加强版20 现代女性性交大全 依人22成人综合网 五码视频在线观看 xxxxppppus社区 撸撸管图片 悠悠人体写真艺术 小男孩以妈妈性交视频 WWWCCC212COM 华人色小说 强奸学校学生亚洲图片 女友穿情趣内衣让我操她 qingchunmeinvpeike 人体全裸艺术美女 顶级人体艺术欧美人体艺术 性感丝袜美女图库欧美色图欧美色图 日本母子l乱伦中文字幕 哪里有美貌女子们的性隐私迅雷下载地址 哪里a片视频 零疼痛人体正确使用姿势书 WWWHNYTWLCOM WWWNTLIDUCOM 我和秦青的性福 佐藤穗乃花 少女和爷爷性交 肏丈母娘屁眼 骚妇掰屄图片 正在播放五十路母影音播放 国模莎莎美乳少妇掰开肥鲍露出湿润大尺度私拍 我插的美女好爽啊无约定香甜 吉吉影音无码艳舞 谁有日本美女黄色照网址 svssex 女模爱爱图 百度美女裸体艺术作品 日逼的网站 鸭哥哥影视 男动物色平色 大学生淫荡做爱 美女私处超大胆高清人体艺术图片摄影3 性爱真人自拍 操屄小说视频 大色窝基地之大色鸟 蒙古女人的性欲故事 老人操逼做爱图片 黄色三色片伦理网 亚洲扒衣 激情网站丁香五月狠狠咂色视频 无毒网站北岛玲 A1黄色片magnet 网友自拍情景剧儿子干妈妈 录音精品线播放 妻子与干爹李娜TXT 肛交av网站 青青草冷sm视频 手机看视频不支持s 欧美性爱色尼古 欧美唆鸡巴 43脳ecom 免费片第一次 丰满肉欲少妇p 儿子插完妈妈插妹妹 韩国赤裸做爱 春暖花开之Wc女厕所偷拍系列网站 紧急更新通知magnet 淫姐姐骗了弟弟操她逼 faxmagnet 意外插入妈妈的身体是那部av电影 制服丝袜亚洲艳舞写真影音 96插妹妹sexsex88com 天天拍天天操神马 人狗做爱过程 大炮影院手机在线观看 56人艺术摄影 帅男同的鸡鸡ed2k 苍井空色域迷强 百度久久做爱视频 插菊花综合网好吊日wwwfwy57trcom 美女俄罗妈妈女主 美性中文娱文网22 国产自拍影 人兽与美女xxoo的视频 教师情景日本A片视频 日你屄流水小说 久久撸人人操综合网站 大鸡吧插入妈妈骚逼 外国姨蕾丝水 狼老公吃老婆类奶子爸爸 淫乱鸳鸯 日韩美少女射精视频 高h肉文推荐 母淫网姐姐 色吧影院54occom 日本母子性爱游戏mp4 非非影视成 香港经典三级被动物插 非州大鸡巴淫色网 抽插艺术 撸撸网分类 看看a片国语a片国语 老婆自慰番号 亚洲2014性爱偷拍 深爱五月天丁香 se五月天有声小说 春色图宫 春色12街 春色文学 春色增大 樱井莉亚松岛枫 樱井莉亚美人 小泽玛利亚双通 www点w21w 开心五月天地址 酒色网的最新地址 哪里能看黄片 快播看黄片地址 求黄色小说网站 美女电影 丁香五月天 母息子影院 AV激情伦理 AV女优电影 色哥哥妹妹 新农夫 额尔撸 百度www·taobaoav 兔牙喵喵在线观看影院 经典三级 欧美无码 在线视频 白白让你操 俺去也网色 55we韩国主播 娃玖影院 4280影院 7m视频最最新版 免费剧情漫画 人人摸人操 李月华满清禁宫秘史 全国最大成人视频 裙子福利视频在线观看 亚洲AV AV在线 AV天堂 邪恶少漫画acg邪恶帝 翘臀美女后进式10p视频在线 强奸少妇花心在线视频 小黄视频免费观看在线播放 日本性虐式变态性交电影 日韩白丝护士足交 日本亚欧高情视频 日本一本道官方在线 日本无码老司机 日韩黄色大片 magnet 日本一本加比勒 400部韩国女主播视频 插萝莉影院 猫狗影视 小蛮腰xxmmyy 视频全集 亚洲百部 红楼影院tv 宾馆草肉丝美女 这女的喷奶好牛逼 西瓜影音 大香蕉喷奶 欧美色女郎 隔离老王免费国产在线av手机观看 wwwyese632 簊田在线观看网站 AV里面luxu什么意思 av人妻2015新人 椎名由奈会长 亚洲做好爱免费视频 狼友 国庆 福利 提示:点开黑屏或白屏缓冲五秒 [红包] 福利免费视频 [红包] ht 越南女人做爱视频dvd 下载 pp福利影院 澳门av视频福利 成人 国产偷拍综合福利门秒拍视频 色色的爱免费视屏 国产视频大佬色 免费 徐娘半老伦理片 在线视频执着高品质 咬奶头成人 xiunv225恋夜影院教师 依依亚洲图片去哪里 午马影院午夜 你懂百度资源 周晓琳大西瓜 日本69movies戴套 午夜不卡理论 98影院播在线 avbob官网下载 丁香六月激情 天然素人av面接加勒比 校园贷porn 刘嘉玲8分视频下载 ftp 影音先锋 松下纱荣子 9999撸一撸 广西主播西西 magnet 女仆装自拍美乳福利在线播放-国产自拍 - 怡红院 怡春院 怡红院电影 最爱怡红 女理发师番号 bkfuli影院 五月婷婷六月丁香综合基地 网站升级反问 avxfzy资源网 久久热漫画 男人大战人妻 XXXa片 800av福利视频导航 世界十大禁片 ftp 爱蜜莉灰毛衣三部曲迅雷下载 亚洲av欧美av电影av视频 五月天天堂电影 大香蕉福利小视频在线影院 夫妻影院 福利影院闪现福利 yinjiejieyinyuan 大陆 自拍 偷拍 国产 福利H 大奶美女做爱播放片 ye1378。com 偷拍,自拍AV伦理电影 国产 日韩 伦理聚合 3国产 自拍 欧美 性爱 日本无码日本有码亚洲 www999abaom 高h黄视频 风 月 海 棠 精 品 啪 啪 情 趣 黑 丝 套 装 美 少 妇 高清在线播放-华人-91爱爱 搞搞b电影网 俺播 秋霞微博连接i AV午夜福利手机直播在线观看 偷拍女生洗澡成人网站 4388网站鸭王 色女人偷拍 夜勤病栋橘子 猫咪 黄片 欧美a片磁力链接 magnet 终极监狱高清电影新闻 大乳美女秀美腿视频 国产自拍偷拍av 影音先锋 小湿影 美足vn 最新日韩性爱视频 黄片100不啪啪啪 3p自拍在线 日本成人动漫视频在线播放 一人一碰操视频 xxxchinese国产h自拍 avttnet天堂网2014 无码av在线av av天堂网2019 私人文件夹漫画 一级美容色国产 亚洲色农夫Av 东方影库av无码在线播放 竹内纱里奈诱惑美痴女 夜秀 迪丽热巴三部曲下载 美国午夜综艺节目大全 四虎视频茄子视频 黑人巨勃根 美女吃春药自慰视频 午夜視频,普通用户,邪恶38 月经期的黄色视频裸体交配 自拍偷拍 家庭乱 赵飞燕迅雷下载 下载 影音先锋乱伦强奸在线 se5xxx69 颜射口爆小女神 美女动态图张又黄又色 桃色电影磁力链接 香蕉网大人网 色欲影视狠狠插 任你一操 欧美怡红院大香焦 2青娱乐视频综合在线 苍井空无修50分钟在线 老色哥俺去也 神崎亜里沙 青娱乐755 国模人体蜈蚣 成长影院久久爱人人观看 阿v天堂在线CK 産婦人科 死刑囚 病院 操女人逼视频播放 铃原爱蜜莉在线 贵阳夫妇在线 私拍app 国产自拍第10页 日本r级2019电影在线看 小仙儿有声小说资源站 美国农夫新导航手机版 裸条贷款10g在线观看 佐佐视频 雅恶影院 相奸游戏泽艺 性爱互插阴交视频 新年午夜剧场 小明看看永久免费视频2 香蕉视屏 magnet 绿椅子完整版good电影 美国成人综艺节目磁力链接 瑟瑟影院大香蕉视频 日本性奴隶视频 欧美日本亚洲性爱视频图片 色色哒福利 夭夭色综合区 成人看片趣趣影院 骚女在线播 搜索午夜色色色色色和口交 xxxxxxxxx黄色 AV视频免费观i 美国啪网站福利 王者荣耀caobishipin 邪恶少3d欧美里番工 农夫AV神马枪AV神马影院 日本大妈优女性爱视频 图片视频亚洲伦理片 黄u视频 色站 在线 伦理 偷拍 韩国人妻在线影院 最新日韩av在线 怡红院分站 色琪琪影色 影音先锋 Av3847 很像杨颖的无码av 手机在线2018天堂一本道网 超漂亮美女AV mp4 六年级学生教师性交 w'w'w'x'x'x日本 新谷露影院11411 98午夜影院观看 汤姆影院htt66avtv 贵妇的沉沦女王反转版 九州视频永久地址发布 永不迷路 丝袜电影五朵美女网 0855的BT种子分享中心手机上怎么不能下载 不要按装什么视频靠开流量能看到男女做爱过程 PPPD-642 骑马乳交插乳抽插 JULIA 最后是厉害的 插美女嫩穴 超乳爆乳巨乳影片福利 Q欧美无码 sus 悠欢呀福利视频 成人福利视频手机版 成人av网站 被窝福利视频天上人间 被窝福利九州 ganyuemuyingyuan 野驴福利网址大全导航 强奸强暴真实在线视频网站 在线免费毛片基地 色凌综合 非洲操逼逼视频 6878wao FSET-532 啪啪啪视频网站上去衣图片给我看看你的照片看看你现在在哪里番acg 风流寡妇三级观看 濑亚美莉magnet 无码 54jb 久草在线2017成人免费动漫视频 在线福利gv ckplayer 资源网 SDMT-921 苍老师啪啪啪视频 夜秀live最新v视频在线播放 子宫崩坏系列番号种子 SSSxin视频 操同学妹妹第二弹粉嫩逼微醺脸红-by 海哥 男女啪啪1000粒视频 荷兰性交视频 一七六九b大香蕉在线 小哥在线国产视频 8月亚洲高清唯爱 操小姐小红屄视频 草妞视频在线观看 两只硕大的巨乳涨奶水 亚洲视频大香蕉姐妹 nanrecaobishipin 处女膜磁力链接 下载 6080伦理大尺度视频 午夜福利国产2000 深喉口交资源 无内衣揉胸吸奶视频 欧美AV黄色网站观看 HIMA-009 mp4 A天堂影院2014在线观看 五月天之色婷婷 av蓝导航 奇葩鱼在线 magnet 33KKa路Com 日本风媚娘巨乳无圣光 嘿嘿帝国视频神马 日本小女学生肛交视频中文视频 亚洲影院色妞 水中人体磁力链接 下载 日韩女优偷拍 桃色星期天 www所有强奸电影 美国一级无码aa视频 色妞ppp 美国人与兽性生活手机版 沙发上爆操白嫩小女友在线视频 六度影院最新网址 伦理片essue免费速播 伦理片2012天堂快播 亂倫片 美女操b真人直播视频 伦理片艳午秀表演 美女操逼内射视频 极品色无极影院 金荷娜17部svip视频磁力 人人摸人碰2016 情趣内衣开档福利视频 精品幼女在线视频 极品网红兼职外围女喝高了和粉丝炮友啪啪这逼嫩得没说的 下载 强奸乱伦成人小视频 家政妇波多野结衣 人妖啪啪啪视频 免费大尺度互舔视频 小清新影院体验服 四虎萝莉 很黄很细的av小说 尻女人露屄图 闺蜜双飞10p 性感视频在线 金刚狼vs神奇女侠h版 手机看片永久免费在线观看国产频道 国产在线视频发布地址 youjizz中国少女 亚洲熟妇三级黄 森萝财团视频 91波哥盛世大厦刚下班 黑人做爱插入下面视频 黄片啊啊啊啊嫩女 后入车震在线 夫妻露脸偷窥自拍 伦理伦理制服 放放动漫网在线在线acg琉璃神社 免费试看邪恶影院 涩涩禾 人体艺术伦里 911影院午夜福利 日本尻屁片 被窝影院金瓶梅 久久爱国产自拍 色琪琪伊人色综合 欧美大片h版58部合集在线观看 在线超碰天天 Sasha Grey先锋资源 久久草原在线 ftp 五月天毛片基地 小明看看大香蕉在线观看 4438咱们看不了 8888A片 毛片看看尻逼 爱情3级片网站 美女教师种子下载 mp4 92cncn 国产 AA级黄色视频 在线视频 国产 第一页 宋芝善视频在线 邪恶外国黄色网站 射在高跟鞋上的精子视频 洛天依H magnet迅雷 国产自拍视频青青草 男人射精呻吟视频 日本熟妇性交视屏 奸杀剧情里番 在线观看3D同人里番动画 泡桑拿被干的番号 8844cbcom 秋霞伧理 日韩啪啪视频无码输出 苍老师岛国片在线看 久久人人看 の五十路bd在线观看 欧美h片巨无霸 被偷拍的女主播樱木6 689aaa eee222 性虐待视频日本 xxoo视频免费欧美激烈 saolou 日本125视频jzz7 porno sayuri mikami 明星淫乱亚洲色 美女大肥阴户露阴图 678avi 人体艺术超大胆图集 野外性freexxx 少女裸替艺术网 香港三级片新江山美人影音先锋 干日本女优影音先锋 女人逼生孩子过程图片 刚肏的屄15p 幼女无码电影性爱偷拍自拍 展屄人体 新母子相奸游戏高月幸穗 外国大妈会阴照片 波多野结美图 深圳真实换妻 66电影成人电影 老外的大鸡巴插中国美女 男人人体艺术露阴茎 欧美兽交肛交群交口交双插 强奸虐屄小说 qvod插菊花网 日本欧美乱伦裸图片 小说成人母子 淫色爷爷2 幼女跟大人做爱影院 免费成人无码快播网址 青木纯奈快播 裸体骚夫