I have no objection to changing the range for the UDP port in the TWAMP yang model. I guess we need concensus from the other authors, and I believe Kostas or Mahesh would need to update the document.
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Sent: Monday, August 19, 2019 11:13 AM
To: Civil, Ruth <gcivil@ciena.com>
Cc: Henrik Nydell <hnydell@accedian.com>om>; Greg Mirsky <gregimirsky@gmail.com>om>; rrahman@cisco.com; Shahram Davari <shahram.davari@broadcom.com>om>; draft-ietf-ippm-stamp@ietf.org; IPPM Chairs <ippm-chairs@ietf.org>rg>; Mirja Kuehlewind <ietf@kuehlewind.net>et>; IETF IPPM WG <ippm@ietf.org>rg>; draft-ietf-ippm-twamp-yang@ietf.org
Subject: Re: [**EXTERNAL**] Re: [ippm] AD review of draft-ietf-ippm-stamp
Hi Ruth,
Thanks for forwarding the email discussion.
There are several drafts [draft-ietf-ippm-stamp-07] [draft-ietf-tram-turnbis-29] those allow User port as well as dynamic port ranges as defined in [RFC6335]. System ports are not allowed.
o the System Ports, also known as the Well Known Ports, from 0-1023
(assigned by IANA)
o the User Ports, also known as the Registered Ports, from 1024-
49151 (assigned by IANA)
o the Dynamic Ports, also known as the Private or Ephemeral Ports,
from 49152-65535 (never assigned)
TWAMP Yang model [draft-ietf-ippm-twamp-yang-13] can also support the range to allow user ports. An example caveat is specified in [draft-ietf-tram-turnbis-29] as "unless the TURN server application knows, through some means not
specified here, that other applications running on the same host as the TURN server application will not be impacted by allocating ports outside this range. "
Thanks,
Rakesh
On Thu, Aug 15, 2019 at 12:54 PM Civil, Ruth <gcivil@ciena.com<mailto:gcivil@ciena.com>> wrote:
We did have a long discussion about allowing UDP ports outside of the dynamic range in the TWAMP Yang model (see the attached outlook thread).
I'm not sure of the repercussions of allowing TWAMP test traffic with UDP port numbers that are assigned to other protocols.
For example, if we started sending TWAMP test packets with a destination UDP port of 123 (NTP) to an IP address on a remote device. How would an NTP application running on that device know that these are not NTP packets - and therefore that it should not intercept them and attempt to process them as such?
Cheers,
Ruth
-----Original Message-----
From: Rakesh Gandhi <rgandhi.ietf@gmail.com<mailto:rgandhi.ietf@gmail.com>>
Sent: Wednesday, August 07, 2019 8:56 AM
To: Henrik Nydell <hnydell@accedian.com<mailto:hnydell@accedian.com>>
Cc: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>; rrahman@cisco.com<mailto:rrahman@cisco.com>; Shahram Davari <shahram.davari@broadcom.com<mailto:shahram.davari@broadcom.com>>; draft-ietf-ippm-stamp@ietf.org<mailto:draft-ietf-ippm-stamp@ietf.org>; IPPM Chairs <ippm-chairs@ietf.org<mailto:ippm-chairs@ietf.org>>; Mirja Kuehlewind <ietf@kuehlewind.net<mailto:ietf@kuehlewind.net>>; IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>; draft-ietf-ippm-twamp-yang@ietf.org<mailto:draft-ietf-ippm-twamp-yang@ietf.org>
Subject: [**EXTERNAL**] Re: [ippm] AD review of draft-ietf-ippm-stamp
Thanks Henrik.
Adding the authors of the TWAMP Yang model to see if they have any thoughts on the UDP port range. It is still not an RFC, so may be this comment can be addressed if needed.
Thanks,
Rakesh
On Wed, Aug 7, 2019 at 4:30 AM Henrik Nydell <hnydell@accedian.com<mailto:hnydell@accedian.com>> wrote:
> The range probably comes from the IANA definition of the ephemeral
> ports
> (49152 to 65535) although these are defined for short-lived TCP and
> not explicitly for UDP. Why this made it into the yang model for
> TWAMP-test (which is UDP) I dont know, probably someone mixed it up
> with TCP and it passed the reviewers without much thought.
>
> Most, if not all, implementations of TWAMP I have seen does not impose
> limitations on the source UDP ports for the TWAMP-test packets when
> configuring via CLI. For example neither Accedian, Exfo, Viavi,
> Juniper, Nokia, Huawei impose any limitation like that when
> configuring via CLI or GUI.
>
> With a yang model based configuration the user will of course be
> limited if they use the yang model that only defines the ephemeral range as valid