Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 29.835
Word version: 17.1.0
0…
4…
4
Requirements
5
Key Issues
6
Solutions
7
Comparison, Evaluations and Conclusions
A
IANA port allocation policy
B
Port number use
C
IANA procedures for Service Name and Port Number registry management
D
How future port number allocations from IETF/IANA could be addressed
$
Change history
4
Requirements
p. 10
4.1
General
p. 10
4.2
Requirement #1: At least either the port number or the Payload Protocol Identifier value shall be standardized for new SCTP interfaces
p. 11
4.2.1
Problem Statement
p. 11
4.2.2
Requirement
p. 11
4.3
Requirement #2: Criteria for selecting preferred solutions
p. 11
5
Key Issues
p. 12
5.1
General
p. 12
5.2
Key Issue #1: Roaming/inter-domain scenario
p. 12
5.2.1
Description of the use case
p. 12
5.2.2
Key issue definition
p. 12
5.3
Key Issue #2: Intra-domain scenario
p. 13
5.3.1
Description of the use case
p. 13
5.3.2
Key issue definition
p. 13
6
Solutions
p. 13
6.1
General
p. 13
6.2
Solution#1: 3GPP allocating port numbers
p. 14
6.2.1
General
p. 14
6.2.2
Detailed description
p. 14
6.2.2.1
General
p. 14
6.2.2.2
Summary of the solution
p. 15
6.2.3
Impacts
p. 15
6.2.4
Pros and cons
p. 15
6.3
Solution#2: Allocating port numbers via OAM
p. 16
6.3.1
General
p. 16
6.3.2
Detailed description
p. 16
6.3.3
Impacts
p. 16
6.3.4
Pros and cons
p. 16
6.4
Solution#3: DNS-SD based solution
p. 17
6.4.1
General
p. 17
6.4.2
Detailed description
p. 17
6.4.3
Impacts
p. 18
6.4.4
Pros and cons
p. 18
6.5
Solution#4: Service discovery using DNS SRV records
p. 18
6.5.1
General
p. 18
6.5.2
Detailed description
p. 19
6.5.3
Impacts
p. 19
6.5.4
Pros and cons
p. 19
6.6
Solution#5: Use of multicast address on local link
p. 20
6.6.1
General
p. 20
6.6.2
Detailed description
p. 20
6.6.3
Impacts
p. 20
6.6.4
Pros and cons
p. 20
6.7
Solution#6: Direct unicast DNS queries to the target node
p. 21
6.7.1
General
p. 21
6.7.2
Detailed description
p. 21
6.7.3
Impacts
p. 22
6.7.4
Pros and cons
p. 22
6.8
Solution#7: SCTP Multiplexer (Port)
p. 22
6.8.1
General
p. 22
6.8.2
Detailed description
p. 24
6.8.3
Impacts
p. 25
6.8.4
Pros and cons
p. 25
6.9
Solution#8: SCTP Multiplexer Application
p. 25
6.9.1
General
p. 25
6.9.2
Detailed description
p. 26
6.9.3
Impacts
p. 27
6.9.4
Pros and cons
p. 27
6.10
Solution#9: TCP Port Service Multiplexer (TCPMUX)
p. 27
6.10.1
General
p. 27
6.10.2
Detailed description
p. 27
6.10.3
Impacts
p. 28
6.10.4
Pros and cons
p. 28
6.11
Solution#10: Standardized and common port for all new SCTP based interfaces with a standardized Payload Protocol Identifier for each interface
p. 28
6.11.1
General
p. 28
6.11.2
Detailed description
p. 29
6.11.3
Impacts
p. 29
6.11.4
Pros and cons
p. 29
6.12
Solution#11: Form a work group to look at port number requirements from 3GPP and work towards relaxing the IETF port allocation policies
p. 30
6.12.1
General
p. 30
6.12.2
Detailed description
p. 30
6.12.3
Impacts
p. 31
6.12.4
Pros and Cons
p. 31
6.13
Solution#12: Port Registration and Retrieval via NRF
p. 32
6.13.1
General
p. 32
6.13.2
Detailed description
p. 32
6.13.3
Impacts
p. 32
6.13.4
Pros and cons
p. 32
6.14
Solution#13: Port information retrieval directly from an NF
p. 32
6.14.1
General
p. 32
6.14.2
Detailed description
p. 33
6.14.3
Impacts
p. 33
6.14.4
Pros and cons
p. 33
6.15
Solution#14: application-layer protocol negotiation over (D)TLS
p. 33
6.15.1
General
p. 33
6.15.2
Detailed description
p. 34
6.15.3
Impacts
p. 34
6.15.4
Pros and cons
p. 35
6.16
Solution#15: Multiplexing based on Service Name Indication
p. 35
6.16.1
General
p. 35
6.16.2
Detailed description
p. 35
6.16.3
Impacts
p. 36
6.16.4
Pros and cons
p. 36
7
Comparison, Evaluations and Conclusions
p. 36
7.1
General
p. 36
7.2
Evaluation of Solutions for Key Issue #1 (inter-PLMN or inter-domain) and Conclusions
p. 37
7.2.1
Evaluation
p. 37
7.2.2
Conclusions for Key Issue #1 solutions (inter-domain)
p. 37
7.3
Evaluation of Solutions for Key Issue #2 (Intra-PLMN or Intra-domain) and Conclusions
p. 37
7.3.1
Evaluation
p. 37
7.3.1.1
Solutions Overview
p. 37
7.3.1.2
Evaluation of 3GPP standardizing port from dynamic range (Solution#1)
p. 40
7.3.1.3
Evaluation of OAM based solution (Solution#2)
p. 40
7.3.1.4
Evaluation of DNS based solutions (solutions #3, #4, #5, #6)
p. 40
7.3.1.5
Evaluation of Multiplexer based solutions (solutions #7, #8 and #9)
p. 41
7.3.1.6
Evaluation of solution with Standardized PPID without multiplexer (solution#10)
p. 41
7.3.1.7
Evaluation of solution to form work group (Solution#11)
p. 42
7.3.1.8
HTTP(s) web server query for port discovery (solutions #12 and #13)
p. 42
7.3.2
Conclusions for Key Issue #2 solutions (intra-domain)
p. 42
7.4
Conclusion summary
p. 43
A
IANA port allocation policy
p. 47
B
Port number use
p. 48
B.1
General
p. 48
B.2
Port number ranges
p. 48
B.3
Service identified by port number not assigned by IANA
p. 49
C
IANA procedures for Service Name and Port Number registry management
p. 50
C.1
General principles
p. 50
C.2
Assignment Procedure
p. 50
C.3
IANA Policies for Port Number assignment
p. 51
C.4
Recommendations to designers of application and service protocols
p. 51
C.5
3GPP port assignment applications since 2009
p. 53
D
How future port number allocations from IETF/IANA could be addressed
p. 55
D.1
General
p. 55
D.2
Key provisions for the draft RFC
p. 55
D.2.1
Introduction
p. 55
D.2.2
Background
p. 55
D.2.3
Objectives
p. 56
D.2.4
Clarifying BCP 165 guidelines
p. 56
$
Change history
p. 57