Re: RFC 8487 port assignment

Dear Hooman,

Sorry for late response.

I checked IANA assignments.
Port 33435 is assigned for Mtrace v2 (UDP) and "reserved" for TCP traceroute.
Port 33434 is assigned for TCP and UDP traceroute.
I don't know why 33435 is separately "reserved", but since 33434 is officially assigned for traceroute (for both TCP and UDP), why 33435 is needed for unicast traceroute, and why linux uses it?
Moreover, although "TCP" port 33435 is "reserved", "UDP" port 33435 is only assigned for Mtrace v2.
There isn't any contradiction for the 33435 port assignment, IMO.

Regards,

Hitoshi


> On Feb 9, 2019, at 6:00, Bidgoli, Hooman (Nokia - CA/Ottawa) <[email protected]> wrote:
> 
> Resending, including the entire WG to consider below questions…
>  
> Regards
>  
> Hooman
>  
> From: Bidgoli, Hooman (Nokia - CA/Ottawa) 
> Sent: Friday, February 1, 2019 4:42 PM
> To: [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: RFC 8487 port assignment 
>  
> Dear all
>  
> IANA has assigned port 33435 for RFC 8487 mtracev2 this port also coincides with Linux unicast traceroute. Actually if you look at this UDP port in IANA you will see it for both unix trace route and mtracev2.
>  
> Would this cause some issues from implementation point of view? Do we need to reconsider the port to be outside of Linux traceroute port range?
> 
> Regards
>  
> Hooman
>  
>  
> _______________________________________________
> MBONED mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mboned

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned