![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi, two clarifications: On 2009-10-29, at 8:42, Dan Wing wrote:
The IANA section in TURN [1] does not request a port assignment for TURN. However, due to existing IANA procedures, IANA is assigning port numbers forTURN.
IANA won't be allocating new port numbers for TURN, the service names for TURN will be aliases for the ports already allocated for STUN (as correctly shown below).
When [2] is adopted, the IANA procedures will be changed so that a portnumber registration is not required; however, [2] is not yet adopted.
It's adopted (in TSVWG), you mean "approved by the IESG" (which it isn't yet.)
Lars
This email is to confirm there is no objection in BEHAVE for the followingIANA action to the IANA port registry [3]: OLD:stun 3478/tcp Session Traversal Utilities for NAT (STUN) port stun 3478/udp Session Traversal Utilities for NAT (STUN) port# [RFC5389] ... stuns 5349/tcp STUN over TLS stuns 5349/udp Reserved for a future enhancement of STUN # [RFC5389] NEW:stun 3478/tcp Session Traversal Utilities for NAT (STUN) port stun 3478/udp Session Traversal Utilities for NAT (STUN) port# [RFC5389] turn 3478/tcp TURN over TCP turn 3478/udp TURN over UDP # [RFC-ietf-behave-turn-16.txt] ... stuns 5349/tcp STUN over TLS stuns 5349/udp Reserved for a future enhancement of STUN # [RFC5389] turns 5349/tcp TURN over TLS turns 5349/udp Reserved for a future enhancement of TURNIf you have an objection, please send email to behave-chairs at tools.ietf.org .Thanks. [1] http://tools.ietf.org/html/draft-ietf-behave-turn-16#section-18 [2] http://tools.ietf.org/html/draft-ietf-tsvwg-iana-ports-03 [3] http://www.iana.org/assignments/port-numbers _______________________________________________ Behave mailing list Behave at ietf.org https://www.ietf.org/mailman/listinfo/behave
Attachment:
smime.p7s
Description: S/MIME cryptographic signature