Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 29.941  Word version:  17.2.0

Top   Top   None   None   Next
0…   4…

 

0  Introductionp. 6

3GPP TR 29.835 studies Port Number Allocation Alternatives for New 3GPP Interfaces. This specification documents the outcome of the study by providing the guidelines for addressing the problem.

1  Scopep. 7

IETF has indicated to 3GPP that future IANA port number assignment requests for protocol only used inside 3GPP networks will be likely rejected except if there is a strong justification for it. The present document provides guidelines for resolving the problem with allocating port numbers for new 3GPP interfaces, as an alternative to IANA assigned port numbers.
Starting from 3GPP Rel-17, any 3GPP working group can rely on these guidelines when defining new interfaces, which require new default port number allocation.
Up

2  Referencesp. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TR 29.835: "Study on Port Number Allocation Alternatives for New 3GPP Interfaces".
[3]
RFC 793:  "Transmission Control Protocol".
[4]
RFC 1078:  "TCP Port Service Multiplexer (TCPMUX)"
[5]
RFC 2782:  "A DNS RR for specifying the location of services (DNS SRV)".
[6]
RFC 4960:  "Stream Control Transmission Protocol".
[7]
RFC 5226:  "Guidelines for Writing an IANA Considerations clause in RFCs".
[8]
RFC 6066:  "Transport Layer Security (TLS) Extensions: Extension Definitions".
[9]
RFC 6083:  "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)".
[10]
RFC 6335:  "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry".
[11]
RFC 6347:  "Datagram Transport Layer Security Version 1.2".
[12]
RFC 6762:  "Multicast DNS".
[13]
RFC 6763:  "DNS-Based Service Discovery".
[14]
RFC 7301:  "Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension".
[15]
RFC 7605:  "Recommendations on Using Assigned Transport Port Numbers".
[16]
RFC 7805:  "Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status".
[17]
RFC 8126:  "Guidelines for Writing an IANA Considerations Clause in RFCs".
[18]
RFC 8446:  "The Transport Layer Security (TLS) Protocol Version 1.3".
[19]
RFC 1035:  "Domain Names _ Implementation and specification".
[20]
TS 29.641: "3GPP registry for Service Names and Port Numbers".
Up

3  Definitions of terms, symbols and abbreviationsp. 8

3.1  Termsp. 8

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  Symbolsp. 8

For the purposes of the present document, the following symbols apply:

3.3  Abbreviationsp. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

Up   Top   ToC