|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
ETSI TS 129 165 V17.6.0 (2023-09)
|
|
Title:
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI) (3GPP TS 29.165 version 17.06.0 Release 17)
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
It used as a reference for the Inter-IMS Network to Network Interface (NNI)
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
https://www.etsi.org/about/how-we-work/intellectual-property-rights-iprs
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of the referred ETSI document is "approved standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
ETSI TS 129.165 was published in 2018-01.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
[5] 3GPP TS 24.229: "INTERNET PROTOCOL (IP) MULTIMEDIA CALL CONTROL PROTOCOL BASED ON SESSION INITIATION PROTOCOL (SIP) AND SESSION DESCRIPTION PROTOCOL (SDP); STAGE 3".
[13] IETF RFC 3261: "SIP: SESSION INITIATION PROTOCOL".
[23] IETF RFC 3311: "THE SESSION INITIATION PROTOCOL (SIP) UPDATE METHOD".
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] 3GPP TR 21.905: "VOCABULARY FOR 3GPP SPECIFICATIONS"./
[2] IETF RFC 791: "INTERNET PROTOCOL"./
[3] 3GPP TS 23.002: "NETWORK ARCHITECTURE"./
[4] 3GPP TS 23.228: "IP MULTIMEDIA SUBSYSTEM (IMS); STAGE 2"./
[5] 3GPP TS 24.229: "INTERNET PROTOCOL (IP) MULTIMEDIA CALL CONTROL PROTOCOL BASED ON SESSION INITIATION PROTOCOL (SIP) AND SESSION DESCRIPTION PROTOCOL (SDP); STAGE 3"./
[6] 3GPP TR 24.930: "SIGNALLING FLOWS FOR THE SESSION SETUP IN THE IP MULTIMEDIA CORE NETWORK SUBSYSTEM (IMS) BASED ON SESSION INITIATION PROTOCOL (SIP) AND SESSION DESCRIPTION PROTOCOL (SDP); STAGE 3"./
[7] IETF RFC 2460: "INTERNET PROTOCOL, VERSION 6 (IPV6) SPECIFICATION"./
[8] 3GPP TS 29.162: "INTERWORKING BETWEEN THE IM CN SUBSYSTEM AND IP NETWORKS"./
[9] 3GPP TS 22.228: "SERVICE REQUIREMENTS FOR THE IP MULTIMEDIA CORE NETWORK SUBSYSTEM"./
[10] 3GPP TS 33.210: "3G SECURITY; NETWORK DOMAIN SECURITY (NDS); IP NETWORK LAYER SECURITY"./
[11] 3GPP TS 26.114: "IP MULTIMEDIA SUBSYSTEM (IMS); MULTIMEDIA TELEPHONY; MEDIA HANDLING AND INTERACTION"./
[12] ETSI TS 181 005 1.1.1: "TELECOMMUNICATIONS AND INTERNET CONVERGED SERVICES AND PROTOCOLS FOR ADVANCED NETWORKING (TISPAN); SERVICES AND CAPABILITIES REQUIREMENTS"./
[13] IETF RFC 3261: "SIP: SESSION INITIATION PROTOCOL"./
[14] IETF RFC 3966: "THE TEL URI FOR TELEPHONE NUMBERS"./
[15] IETF RFC 3860: "COMMON PROFILE FOR INSTANT MESSAGING (CPIM)"./
[16] IETF RFC 3859: "COMMON PROFILE FOR PRESENCE (CPP)"./
[17] IETF RFC 4975: "THE MESSAGE SESSION RELAY PROTOCOL (MSRP)"./
[18] IETF RFC 3262: "RELIABILITY OF PROVISIONAL RESPONSES IN SESSION INITIATION PROTOCOL (SIP)"./
[19] IETF RFC 3428: "SESSION INITIATION PROTOCOL (SIP) EXTENSION FOR INSTANT MESSAGING"./
[20] IETF RFC 3265: "SESSION INITIATION PROTOCOL (SIP) SPECIFIC EVENT NOTIFICATION"./
[21] IETF RFC 3903: "AN EVENT STATE PUBLICATION EXTENSION TO THE SESSION INITIATION PROTOCOL (SIP)"./
[22] IETF RFC 3515: "THE SESSION INITIATION PROTOCOL (SIP) REFER METHOD"./
[23] IETF RFC 3311: "THE SESSION INITIATION PROTOCOL (SIP) UPDATE METHOD"./
[24] IETF RFC 3455: "PRIVATE HEADER (P-HEADER) EXTENSIONS TO THE SESSION INITIATION PROTOCOL (SIP) FOR THE 3RD-GENERATION PARTNERSHIP PROJECT (3GPP)"./
[25] IETF RFC 4244: "AN EXTENSION TO THE SESSION INITIATION PROTOCOL (SIP) FOR REQUEST HISTORY INFORMATION"./
[26] IETF RFC 6050: "A SESSION INITIATION PROTOCOL (SIP) EXTENSION FOR THE IDENTIFICATION OF SERVICES"./
[27] IETF RFC 4168: "THE STREAM CONTROL TRANSMISSION PROTOCOL (SCTP) AS A TRANSPORT FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[28] VOID./
[29] 3GPP TS 32.260: "TELECOMMUNICATION MANAGEMENT; CHARGING MANAGEMENT; IP MULTIMEDIA SUBSYSTEM (IMS) CHARGING"./
[30] 3GPP TS 22.173: "IP MULTIMEDIA CORE NETWORK SUBSYSTEM (IMS); MULTIMEDIA TELEPHONY SERVICE AND SUPPLEMENTARY SERVICES; STAGE 1"./
[31] 3GPP TS 24.173: "IMS MULTIMEDIA TELEPHONY COMMUNICATION SERVICE AND SUPPLEMENTARY SERVICES; STAGE 3"./
[32] 3GPP TS 24.607: "ORIGINATING IDENTIFICATION PRESENTATION (OIP) AND ORIGINATING IDENTIFICATION RESTRICTION (OIR) USING IP MULTIMEDIA (IM); CORE NETWORK (CN) SUBSYSTEM"./
[33] 3GPP TS 24.616: "MALICIOUS COMMUNICATION IDENTIFICATION (MCID) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[34] IETF RFC 3323: "A PRIVACY MECHANISM FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[35] 3GPP TS 23.003: "NUMBERING, ADDRESSING AND IDENTIFICATION"./
[36] 3GPP TS 24.610: "COMMUNICATION HOLD (HOLD) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[37] 3GPP TS 24.615: "COMMUNICATION WAITING (CW) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[38] 3GPP TS 24.628: "COMMON BASIC COMMUNICATION PROCEDURES USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[39] IETF RFC 6086: "SESSION INITIATION PROTOCOL (SIP) INFO METHOD AND PACKAGE FRAMEWORK"./
[40] IETF RFC 3312: "INTEGRATION OF RESOURCE MANAGEMENT AND SESSION INITIATION PROTOCOL (SIP)"./
[41] IETF RFC 4032: "UPDATE TO THE SESSION INITIATION PROTOCOL (SIP) PRECONDITIONS FRAMEWORK"./
[42] IETF RFC 3313: "PRIVATE SESSION INITIATION PROTOCOL (SIP) EXTENSIONS FOR MEDIA AUTHORIZATION"./
[43] IETF RFC 3327: "SESSION INITIATION PROTOCOL EXTENSION HEADER FIELD FOR REGISTERING NON-ADJACENT CONTACTS"./
[44] IETF RFC 3325: "PRIVATE EXTENSIONS TO THE SESSION INITIATION PROTOCOL (SIP) FOR NETWORK ASSERTED IDENTITY WITHIN TRUSTED NETWORKS"./
[45] IETF RFC 3608: "SESSION INITIATION PROTOCOL (SIP) EXTENSION HEADER FIELD FOR SERVICE ROUTE DISCOVERY DURING REGISTRATION"./
[46] IETF RFC 3486: "COMPRESSING THE SESSION INITIATION PROTOCOL (SIP)"./
[47] IETF RFC 3329: "SECURITY MECHANISM AGREEMENT FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[48] IETF RFC 3326: "THE REASON HEADER FIELD FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[49] IETF RFC 6432: "CARRYING Q.850 CODES IN REASON HEADER FIELDS IN SIP (SESSION INITIATION PROTOCOL) RESPONSES"./
[50] IETF RFC 3581: "AN EXTENSION TO THE SESSION INITIATION PROTOCOL (SIP) FOR SYMMETRIC RESPONSE ROUTING"./
[51] IETF RFC 3841: "CALLER PREFERENCES FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[52] IETF RFC 4028: "SESSION TIMERS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[53] IETF RFC 3892: "THE SESSION INITIATION PROTOCOL (SIP) REFERRED-BY MECHANISM"./
[54] IETF RFC 3891: "THE SESSION INITITATION PROTOCOL (SIP) 'REPLACES' HEADER"./
[55] IETF RFC 3911: "THE SESSION INITITATION PROTOCOL (SIP) 'JOIN' HEADER"./
[56] IETF RFC 3840: "INDICATING USER AGENT CAPABILITIES IN THE SESSION INITIATION PROTOCOL (SIP)"./
[57] IETF RFC 5079: "REJECTING ANONYMOUS REQUESTS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[58] IETF RFC 4458: "SESSION INITIATION PROTOCOL (SIP) URIS FOR APPLICATIONS SUCH AS VOICEMAIL AND INTERACTIVE VOICE RESPONSE (IVR)"./
[59] IETF RFC 4320: "ACTIONS ADDRESSING IDENTIFIED ISSUES WITH THE SESSION INITIATION PROTOCOL'S (SIP) NON-INVITE TRANSACTION"./
[60] IETF RFC 4457: "THE SESSION INITIATION PROTOCOL (SIP) P-USER-DATABASE PRIVATE-HEADER (P-HEADER)"./
[61] IETF RFC 5031: "A UNIFORM RESOURCE NAME (URN) FOR SERVICES"./
[62] IETF RFC 5627: "OBTAINING AND USING GLOBALLY ROUTABLE USER AGENT (UA) URIS (GRUU) IN THE SESSION INITIATION PROTOCOL (SIP)"./
[63] VOID/
[64] IETF RFC 5002: "THE SESSION INITIATION PROTOCOL (SIP) P-PROFILE-KEY PRIVATE HEADER (P-HEADER)"./
[65] IETF RFC 5626: "MANAGING CLIENT-INITIATED CONNECTIONS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[66] IETF 5768: "INDICATING SUPPORT FOR INTERACTIVE CONNECTIVITY ESTABLISHMENT (ICE) IN THE SESSION INITIATION PROTOCOL (SIP)"./
[67] IETF RFC 5365: "MULTIPLE-RECIPIENT MESSAGE REQUESTS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[68] IETF RFC 6442: "LOCATION CONVEYANCE FOR THE SESSION INITIATION PROTOCOL"./
[69] IETF RFC 5368: "REFERRING TO MULTIPLE RESOURCES IN THE SESSION INITIATION PROTOCOL (SIP)"./
[70] IETF RFC 5366: "CONFERENCE ESTABLISHMENT USING REQUEST-CONTAINED LISTS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[71] IETF RFC 5367: "SUBSCRIPTIONS TO REQUEST-CONTAINED RESOURCE LISTS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[72] IETF RFC 4967: "DIAL STRING PARAMETER FOR THE SESSION INITIATION PROTOCOL UNIFORM RESOURCE IDENTIFIER"./
[73] IETF RFC 4964: "THE P-ANSWER-STATE HEADER EXTENSION TO THE SESSION INITIATION PROTOCOL FOR THE OPEN MOBILE ALLIANCE PUSH TO TALK OVER CELLULAR"./
[74] IETF RFC 5009: "PRIVATE HEADER (P-HEADER) EXTENSION TO THE SESSION INITIATION PROTOCOL (SIP) FOR AUTHORIZATION OF EARLY MEDIA"./
[75] IETF RFC 4694: "NUMBER PORTABILITY PARAMETERS FOR THE 'TEL' URI"./
[76] VOID/
[77] IETF RFC 4411: "EXTENDING THE SESSION INITIATION PROTOCOL (SIP) REASON HEADER FOR PREEMPTION EVENTS"./
[78] IETF RFC 4412: "COMMUNICATIONS RESOURCE PRIORITY FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[79] IETF RFC 5393: "ADDRESSING AN AMPLIFICATION VULNERABILITY IN SESSION INITIATION PROTOCOL (SIP) FORKING PROXIES"./
[80] IETF RFC 5049: "APPLYING SIGNALING COMPRESSION (SIGCOMP) TO THE SESSION INITIATION PROTOCOL (SIP)"./
[81] IETF RFC 5688: "A SESSION INITIATION PROTOCOL (SIP) MEDIA FEATURE TAG FOR MIME APPLICATION SUB-TYPES"./
[82] IETF RFC 5360: "A FRAMEWORK FOR CONSENT-BASED COMMUNICATIONS IN THE SESSION INITIATION PROTOCOL (SIP)"./
[83] DRAFT-IETF-CUSS-SIP-UUI-04 (OCTOBER 2011): "A MECHANISM FOR TRANSPORTING USER TO USER CALL CONTROL INFORMATION IN SIP"./
[83A] DRAFT-IETF-CUSS-SIP-UUI-ISDN-02 (FEBRUARY 2012): "INTERWORKING ISDN CALL CONTROL USER INFORMATION WITH SIP"./
[84] DRAFT-VANELBURG-DISPATCH-PRIVATE-NETWORK-IND-01 (JUNE 2010): "THE SESSION INITIATION PROTOCOL (SIP) P-PRIVATE-NETWORK-INDICATION PRIVATE-HEADER (P-HEADER)"./
[85] IETF RFC 5502: "THE SIP P-SERVED-USER PRIVATE-HEADER (P-HEADER) FOR THE 3GPP IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[86] VOID./
[87] DRAFT-DAWES-SIPPING-DEBUG-04 (FEBRUARY 2011): " SESSION INITIATION PROTOCOL (SIP) HEADER PARAMETER FOR DEBUGGING"./
[88] IETF RFC 6228: "RESPONSE CODE FOR INDICATION OF TERMINATED DIALOG"./
[89] IETF RFC 5621: "MESSAGE BODY HANDLING IN THE SESSION INITIATION PROTOCOL (SIP)"./
[90] IETF RFC 6223: "INDICATION OF SUPPORT FOR KEEP-ALIVE"./
[91] IETF RFC 5552: "SIP INTERFACE TO VOICEXML MEDIA SERVICES"./
[92] IETF RFC 3862: "COMMON PRESENCE AND INSTANT MESSAGING (CPIM): MESSAGE FORMAT"./
[93] IETF RFC 5438: "INSTANT MESSAGE DISPOSITION NOTIFICATION"./
[94] IETF RFC 5373: "REQUESTING ANSWERING MODES FOR THE SESSION INITIATION PROTOCOL (SIP)". /
[95] VOID/
[96] IETF RFC 3959: "THE EARLY SESSION DISPOSITION TYPE FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[97] VOID./
[98] 3GPP TS 24.183: "CUSTOMIZED RINGING SIGNAL (CRS) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[99] 3GPP TS 24.259: "PERSONAL NETWORK MANAGEMENT (PNM) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[100] 3GPP TS 24.238: "SESSION INITIATION PROTOCOL (SIP) BASED USER CONFIGURATION"./
[101] 3GPP TS 24.239: "FLEXIBLE ALERTING (FA) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[102] VOID./
[103] 3GPP TS 24.654: "CLOSED USER GROUP (CUG) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[104] VOID./
[105] 3GPP TS 24.605: "CONFERENCE (CONF) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[106] 3GPP TS 24.147: "CONFERENCING USING THE IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[107] VOID./
[108] VOID. /
[109] 3GPP TS 24.642: "COMPLETION OF COMMUNICATIONS TO BUSY SUBSCRIBER (CCBS) COMPLETION OF COMMUNICATIONS BY NO REPLY (CCNR) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[110] VOID./
[111] VOID./
[112] 3GPP TS 24.606: "MESSAGE WAITING INDICATION (MWI) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[113] 3GPP TS 24.608: "TERMINATING IDENTIFICATION PRESENTATION (TIP) AND TERMINATING IDENTIFICATION RESTRICTION (TIR) USING IP MULTIMEDIA (IM); CORE NETWORK (CN) SUBSYSTEM"./
[114] 3GPP TS 24.611: "COMMUNICATION BARRING (CB) USING IP MULTIMEDIA (IM); CORE NETWORK (CN) SUBSYSTEM"./
[115] VOID./
[116] 3GPP TS 24.629: "EXPLICIT COMMUNICATION TRANSFER (ECT) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[117] 3GPP TS 24.604: "COMMUNICATION DIVERSION (CDIV) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[118] VOID./
[119] VOID./
[120] 3GPP TS 23.292: "IP MULTIMEDIA SUBSYSTEM (IMS) CENTRALIZED SERVICES; STAGE 2"./
[121] 3GPP TS 24.292: "IP MULTIMEDIA CORE NETWORK SUBSYSTEM CENTRALIZED SERVICES (ICS); STAGE 3"./
[122] 3GPP TS 24.647: "ADVICE OF CHARGE (AOC) USING IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[123] VOID./
[124] DRAFT-KAPLAN- DISPATCH -SESSION-ID-00 (DECEMBER 2009): "A SESSION IDENTIFIER FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[125] IETF RFC 6026: "CORRECT TRANSACTION HANDLING FOR 2XX RESPONSES TO SESSION INITIATION PROTOCOL (SIP) INVITE REQUESTS"./
[126] IETF RFC 5658: "ADDRESSING RECORD-ROUTE ISSUES IN THE SESSION INITIATION PROTOCOL (SIP)"./
[127] IETF RFC 5954: "ESSENTIAL CORRECTION FOR IPV6 ABNF AND URI COMPARISON IN RFC3261"./
[128] VOID./
[129] 3GPP TS 24.182: "IP MULTIMEDIA SUBSYSTEM (IMS) CUSTOMIZED ALERTING TONES (CAT)"./
[130] 3GPP TS 29.292: "INTERWORKING BETWEEN THE IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM AND MSC SERVER FOR IMS CENTRALIZED SERVICES (ICS)"./
[131] 3GPP TS 24.237: "IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM; IP MULTIMEDIA SUBSYSTEM (IMS) SERVICE CONTINUITY"./
[132] 3GPP TS 24.141: "PRESENCE SERVICE USING THE IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[133] DRAFT-IETF-SIP-SESSION-POLICY-FRAMEWORK-10 (FEBRUARY 2011): "A FRAMEWORK FOR SESSION INITIATION PROTOCOL (SIP) SESSION POLICIES"./
[134] IETF RFC 5875: "AN EXTENSIBLE MARKUP LANGUAGE (XML) CONFIGURATION ACCESS PROTOCOL (XCAP) DIFF EVENT PACKAGE"./
[135] IETF RFC 4488: "SUPPRESSION OF SESSION INITIATION PROTOCOL (SIP) REFER METHOD IMPLICIT SUBSCRIPTION"./
[136] DRAFT-IETF-SALUD-ALERT-INFO-URNS-00(DECEMBER 2010): "ALERT-INFO URNS FOR FOR THE SESSION INITIATION PROTOCOL (SIP)"./
[137] DRAFT-DAWES-DISPATCH-MEDIASEC-PARAMETER-04 (AUGUST 2011): "CAPABILITY EXCHANGE FOR MEDIA PLANE SECURITY"./
[138] OMA-TS-PRESENCE_SIMPLE-V2_0-20101202 "PRESENCE SIMPLE SPECIFICATION"./
[139] 3GPP TS 24.247: "MESSAGING SERVICE USING THE IP MULTIMEDIA (IM) CORE NETWORK (CN) SUBSYSTEM"./
[140] IETF RFC 4538: "REQUEST AUTHORIZATION THROUGH DIALOG IDENTIFICATION IN THE SESSION INITIATION PROTOCOL (SIP)"./
[141] IETF RFC 5318: "THE SESSION INITIATION PROTOCOL (SIP) P-REFUSED-URI-LIST PRIVATE-HEADER (P-HEADER)"./
[142] OMA-TS-PRESENCE_SIMPLE-V1_1-20100225 "PRESENCE SIMPLE SPECIFICATION"./
[143] DRAFT-HOLMBERG-SIPCORE-PROXY-FEATURE-04 (DECEMBER 2011): "INDICATION OF FEATURES SUPPORTED BY PROXY"./
[144] IETF RFC 5839: "AN EXTENSION TO SESSION INITIATION PROTOCOL (SIP) EVENTS FOR CONDITIONAL EVENT NOTIFICATION"./
[145] VOID./
[146] IETF RFC 3264: "AN OFFER/ANSWER MODEL WITH THE SESSION DESCRIPTION PROTOCOL (SDP)"./
[147] IETF RFC 4566: "SDP: SESSION DESCRIPTION PROTOCOL"./
[148] 3GPP TS 29.079: "OPTIMAL MEDIA ROUTEING WITHIN THE IP MULTIMEDIA SUBSYSTEM; STAGE 3"./
[149] 3GPP TS 24.337: "IP MULTIMEDIA SUBSYSTEM (IMS) INTER-UE TRANSFER"./
[150] IETF RFC 3960: "EARLY MEDIA AND RINGING TONE GENERATION IN THE SESSION INITIATION PROTOCOL (SIP)"./
[151] IETF RFC 3550: "RTP: A TRANSPORT PROTOCOL FOR REAL-TIME APPLICATIONS"./
[152] IETF RFC 768: "USER DATAGRAM PROTOCOL"./
[153] IETF RFC 3551: "RTP PROFILE FOR AUDIO AND VIDEO CONFERENCES WITH MINIMAL CONTROL"./
[154] IETF RFC 3556: "SESSION DESCRIPTION PROTOCOL (SDP) BANDWIDTH MODIFIERS FOR RTP CONTROL PROTOCOL (RTCP) BANDWIDTH"./
[155] IETF RFC 4585: "EXTENDED RTP PROFILE FOR REAL-TIME TRANSPORT CONTROL PROTOCOL (RTCP)-BASED FEEDBACK (RTP/AVPF)"./
[156] IETF RFC 793: "TRANSMISSION CONTROL PROTOCOL"./
[157] IETF RFC 4733: "RTP PAYLOAD FOR DTMF DIGITS, TELEPHONY TONES, AND TELEPHONY SIGNALS"./
[158] IETF RFC 4916: "CONNECTED IDENTITY IN THE SESSION INITIATION PROTOCOL (SIP)"./
[159] 3GPP TS 23.237: "IP MULTIMEDIA SUBSYSTEM (IMS) SERVICE CONTINUITY "/
[160] IETF RFC 6140: "Registration for Multiple Phone Numbers in the Session Initiation Protocol/
(SIP)"./
[161] IETF RFC 6230: "Media Control Channel Framework"./
[162] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)"./
[163] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD)"./
[164] IETF RFC 6357: "Design Considerations for Session Initiation Protocol (SIP) Overload Control"./
[165] IETF RFC 7339: "Session Initiation Protocol (SIP) Overload Control"./
[166] IETF RFC 7415: "Session Initiation Protocol (SIP) Rate Control"./
[167] IETF RFC 7200: "A Session Initiation Protocol (SIP) Load-Control Event Package"./
[168] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem/
and Circuit Switched (CS) networks"./
[169] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"./
[170] IETF RFC 2387: "The MIME Multipart/Related Content-type"./
[171] IETF RFC 3420: "Internet Media Type message/sipfrag"./
[172] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the/
Session Initiation Protocol (SIP)"./
[173] IETF RFC 3858: "An Extensible Markup Language (XML) Based Format for Watcher/
Information". /
[174] IETF RFC 3863: "Presence Information Data Format (PIDF)"./
[175] IETF RFC 3994: "Indication of Message Composition for Instant Messaging"./
[176] IETF RFC 4661: "An Extensible Markup Language (XML) Based Format for Event Notification/
Filtering"./
[177] IETF RFC 4662: "A Session Initiation Protocol (SIP) Event Notification Extension for Resource/
Lists"./
[178] IETF RFC 4826: "Extensible Markup Language (XML) Formats for Representing Resource/
Lists"./
[179] IETF RFC 5262: "Presence Information Data Format (PIDF) Extension for Partial Presence"./
[180] IETF RFC 5874: "An Extensible Markup Language (XML) Document Format for Indicating a/
Change in XML Configuration Access Protocol (XCAP) Resources"./
[181] Void./
[182] OMA-SUP-XSD_prs_suppnotFilter-V1_0-20120710-A: "Presence - Event notification/
suppression filter"./
[183] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging/
architecture and principles"./
[184] IETF RFC 7090: "Public Safety Answering Point (PSAP) Callback"./
[185] IETF RFC 8055: "Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate/
Received Realm"./
[186] 3GPP TS 29.658: "SIP Transfer of IP Multimedia Service Tariff Information"./
[187] 3GPP TS 22.153: "Multimedia priority service"./
[188] IETF RFC 7549: "3GPP SIP URI Inter Operator Traffic Leg parameter"./
[189] 3GPP TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem/
(IMS); Stage 3"./
[190] IETF RFC 8841: "Session Description Protocol (SDP) Offer/Answer Procedures for Stream/
Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS)/
Transport"./
[191] 3GPP TS 24.315: "IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB)"./
[192] 3GPP TR 29.949: "Study on Technical aspects on Roaming End-to-end scenarios with VoLTE/
IMS and other networks"./
[193] IETF RFC 8119: "SIP "cause" URI Parameter for Service Number Translation"./
[194] IETF RFC 7647: "Clarifications for the Use of REFER with RFC6665"./
[195] IETF RFC 7614: "Explicit Subscriptions for the REFER Method"./
[196] IETF RFC 7621: "A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in/
the Session Initiation Protocol SIP Event Notification Framework"./
[197] IETF RFC 2646: "The Text/Plain Format Parameter"./
[198] IETF RFC 1866: "Hypertext Markup Language - 2.0"./
[199] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1"./
[200] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2"./
[201] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification"./
[202] 3GPP TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control Protocol specification"./
[203] IETF RFC 8498: "A P-Served-User Header Field Parameter for an Originating Call Diversion/
(CDIV) Session Case in the Session Initiation Protocol (SIP)"./
[204] IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State"./
[205] IETF RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various/
Settings in Support for the Push-to-Talk over Cellular (PoC) Service"./
[206] IETF RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)"./
[207] IETF RFC 8197: "A SIP Response Code for Unwanted Calls"./
[208] IETF RFC 6910: "Completion of Calls for the Session Initiation Protocol (SIP)"./
[209] 3GPP TS 22.280: "Mission Critical Services Common Requirements"./
[210] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification"./
[211] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification"./
[212] 3GPP TS 24.581: "Mission Critical Video (MCVideo) media plane control; Protocol/
specification"./
[213] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification"./
[214] IETF RFC 8606: "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header/
Field"./
[215] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions"./
[216] IETF RFC 8262: "Content-ID Header Field in the Session Initiation Protocol (SIP)"./
[217] 3GPP TS 24.196: "Technical Specification Group Core Network and Terminals; Enhanced Calling/
Name"./
[218] 3GPP TS 24.174: "Support of Multi-Device and Multi-Identity in IMS; Stage 3"./
[219] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model"./
[220] IETF RFC 9410: "Handling of Identity Header Errors for Secure Telephone Identity Revisited/
(STIR)". /
|
|
9.
|
Qualification of
ETSI:
|
|
|
ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
If the Study Group decides to make the reference to the ETSI TS 129.165, the reference should always be made by ETSI number
|
