Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 29.835  Word version:  17.1.0

Top   Top   Up   Prev   None
0…   4…

 

4  Requirementsp. 10

5  Key Issuesp. 12

6  Solutionsp. 13

6.1  Generalp. 13

6.2  Solution#1: 3GPP allocating port numbersp. 14

6.3  Solution#2: Allocating port numbers via OAMp. 16

6.4  Solution#3: DNS-SD based solutionp. 17

6.5  Solution#4: Service discovery using DNS SRV recordsp. 18

6.6  Solution#5: Use of multicast address on local linkp. 20

6.7  Solution#6: Direct unicast DNS queries to the target nodep. 21

6.8  Solution#7: SCTP Multiplexer (Port)p. 22

6.9  Solution#8: SCTP Multiplexer Applicationp. 25

6.10  Solution#9: TCP Port Service Multiplexer (TCPMUX)p. 27

6.11  Solution#10: Standardized and common port for all new SCTP based interfaces with a standardized Payload Protocol Identifier for each interfacep. 28

6.12  Solution#11: Form a work group to look at port number requirements from 3GPP and work towards relaxing the IETF port allocation policiesp. 30

6.13  Solution#12: Port Registration and Retrieval via NRFp. 32

6.14  Solution#13: Port information retrieval directly from an NFp. 32

6.15  Solution#14: application-layer protocol negotiation over (D)TLSp. 33

6.16  Solution#15: Multiplexing based on Service Name Indicationp. 35

7  Comparison, Evaluations and Conclusionsp. 36

A  IANA port allocation policyp. 47

B  Port number usep. 48

C  IANA procedures for Service Name and Port Number registry managementp. 50

D  How future port number allocations from IETF/IANA could be addressedp. 55

$  Change historyp. 57


Up   Top