This page is being moved to a new, faster, and mobile-friendly application! Access the enhanced and centralized experience now on MyWorkspace.
ITU's 160 anniversary

Connecting the world and beyond

  •  

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.DMSA     
  ITU-T A.5 justification information for referenced document 3GPP TS 33.210 (2024-04) in draft Q.DMSA
1. Clear description of the referenced document:
Name: 3GPP TS 33.210 (2024-04)
Title: Network Domain Security (NDS); IP network layer security. (Release 18)
2. Status of approval:
Approved. Release 19 exists.
3. Justification for the specific reference:
It is used in Q.DMSA "Principles for detection and mitigation of signalling attacks in telecommunication networks" developed by ITU-T SG11.
4. Current information, if any, about IPR issues:
None.
5. Other useful information describing the "Quality" of the document:
3GPP TS 33.210 (Release 18) is published by 3GPP in 2024.
6. The degree of stability or maturity of the document:
3GPP TS 33.210 (Release 18) is published by 3GPP in 2024.
7. Relationship with other existing or emerging documents:
3GPP TS 33.210 (Release 18) is published by 3GPP in 2024.
8. Any explicit references within that referenced document should also be listed:
[1] Void./
[2] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services/
and System Aspects; Vocabulary for 3GPP Specifications"./
[3] 3GPP TS 23.002: "3rd Generation Partnership Project; Technical Specification Group Services/
and Systems Aspects; Network architecture"./
[4] Void./
[5] Void./
[6] 3GPP TS 29.060: "3rd Generation Partnership Project; Technical Specification Group Core/
Network; General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn/
and Gp Interface"./
[7] Void./
[8] Void./
[9] Void./
[10] 3GPP TS 33.203: "3rd Generation Partnership Project; Technical Specification Group Services/
and System Aspects; Access security for IP-based services"./
[11] -[25] Void./
[26] RFC-3554: "On the Use of Stream Control Transmission Protocol (SCTP) with IPsec"./
[27] Void./
[28] 3GPP TS 25.412: "3rd Generation Partnership Project; Technical Specification Group Radio/
Access Network; UTRAN Iu interface signalling transport"./
[29] Void./
[30] 3GPP TS 33.310: "3rd Generation Partnership Project; Technical Specification Group Services/
and System Aspects; 3G Security; Network domain security; Authentication Framework"./
[31] RFC-4303: "IP Encapsulating Security Payload (ESP)"/
[32] Void. /
[33] Void/
[34] Void./
[35] RFC-4301: "Security Architecture for the Internet Protocol"./
[36] Void./
[37] Void./
[38] 3GPP TS 25.422: "3rd Generation Partnership Project; Technical Specification Group Radio/
Access Network; UTRAN Iur interface signalling transport"./
[39] 3GPP TS 25.467: "3rd Generation Partnership Project; Technical Specification Group Radio/
Access Network; UTRAN architecture for 3G Home Node B (HNB); Stage 2"./
[40] 3GPP TS 25.468: "3rd Generation Partnership Project; Technical Specification Group Radio/
Access Network; UTRAN Iuh Interface RANAP User Adaption (RUA) signalling"./
[41] 3GPP TS 25.471: "3rd Generation Partnership Project; Technical Specification Group Radio/
Access Network; UTRAN Iurh Interface RNSAP User Adaption (RNA) signalling"./
[42] RFC-6311: "Protocol Support for High Availability of IKEv2/IPsec"./
[43] RFC-7296: "Internet Key Exchange Protocol Version 2 (IKEv2)"./
[44] IANA: "Internet Key Exchange Version 2 (IKEv2) Parameters"./
[45] Void./
[46] IETF RFC 7515: "JSON Web Signature (JWS)"./
[47] IETF RFC 7516: "JSON Web Encryption (JWE)"./
[48] IETF RFC 7518: "JSON Web Algorithms (JWA)"./
[49] IETF RFC 6347: "Datagram Transport Layer Security Version 1.2"./
[50] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2"./
[51] IETF RFC 8442: "ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for TLS 1.2 and/
DTLS 1.2”./
[52] Void/
[53] IETF RFC 2817: "Upgrading to TLS Within HTTP/1.1"./
[54] IETF RFC 5288: "AES Galois Counter Mode (GCM) Cipher Suites for TLS"./
[55] IETF RFC 5289: "TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter/
Mode (GCM)"./
[56] Void./
[57] IETF RFC 6066: "Transport Layer Security (TLS) Extensions: Extension Definitions"./
[58] Void./
[59] IETF RFC 5077: "Transport Layer Security (TLS) Session Resumption without Server-Side/
State"./
[60] IETF RFC 5746: "Transport Layer Security (TLS) Renegotiation Indication Extension"./
[61] IETF RFC 7627: "Transport Layer Security (TLS) Session Hash and Extended Master Secret/
Extension"./
[62] IETF RFC 7919: "Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport/
Layer Security (TLS)". /
[63] Void/
[64] IETF RFC 5489: "ECDHE_PSK Cipher Suites for Transport Layer Security (TLS)"./
[65] IETF RFC 5487: "Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois/
Counter Mode"./
[66] IETF RFC 8446: “The Transport Layer Security (TLS) Protocol Version 1.3"./
[67] Void/
[68] Void./
[69] IETF RFC 4086: "Randomness Recommendations for Security"./
[70] IETF RFC 8221: "Cryptographic Algorithm Implementation Requirements and Usage Guidance/
for Encapsulating Security Payload (ESP) and Authentication Header (AH)"./
[71] IETF RFC 8422: "Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security/
(TLS) "./
[72] IETF RFC 8937: " Randomness Improvements for Security Protocols"./
[73] IETF RFC-8247: "Algorithm Implementation Requirements and Usage Guidance for the Internet/
Key Exchange Protocol Version 2 (IKEv2)"./
[74] RFC 9110: "HTTP Semantics".
9. Qualification of 3GPP:
3GPP is qualified under Recommendation ITU-T A.5 since 09/2020, applying ITU-T A.5 §7.3. Reference: SG15-R24 (2020-09)
10. Other (for any supplementary information):
None
Note: This form is based on Recommendation ITU-T A.5