[hpsdr] The UDP ports in the new Ethernet protocol violate the ethos of the Internet.

[George Byrkit]

Dear Matthew,
Thanks for your observations.  The truth is that these UDP ports (or some of them) were
also used in the previous Ethernet implementation.

Now, 'Internet' isn't of much use, because most ISPs do not route UDP packets, it would
seem.   Thus, all of this is confined to being used inside your own subnet.  That might
make internet standards somewhat less relevant.

However, a conflict with other 'well-known' UDP ports should be avoided, to better ensure
operation of the software and hardware.

George Byrkit, K9TRV

-----Original Message-----
From: Hpsdr [mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of Matthew J Wolf
Sent: Thursday, January 14, 2016 11:15 AM
To: hpsdr at lists.openhpsdr.org
Subject: [hpsdr] The UDP ports in the new Ethernet protocol violate the ethos of the
Internet.

***** High Performance Software Defined Radio Discussion List *****


The UDP ports in the new Ethernet protocol violates the ethos of the 
Internet.

The UDP service ports I see in version 2.3 of Ethernet Protocol document 
are 1024 to 1114. These UDP ports are part of "Users Ports" port number 
range. The User Ports range of port are Registered (assigned)  Ports, 
sec 6 RFC 6335.

Most of the port numbers from 1024 to 1114 are all ready assigned to 
other protocols.

It is bad form to reuse all ready assigned ports with a different 
protocol.

There is range of ports that have been set aside for local and dynamic 
use. Local being network traffic that will not be sent over the 
Internet. The port range is the "Dynamic Ports", sec 6 RFC 6335.


First bullet point from section 8.1.2 of RFC 6335:

       "Ports in the Dynamic Ports range (49152-65535) have been
       specifically set aside for local and dynamic use and cannot be
       assigned through IANA.  Application software may simply use any
       dynamic port that is available on the local host, without any sort
       of assignment.  On the other hand, application software MUST NOT
       assume that a specific port number in the Dynamic Ports range will
       always be available for communication at all times, and a port
       number in that range hence MUST NOT be used as a service
       identifier."

I think the Ethernet protocol should use ports from the Dynamic Ports 
range. Why not start at port 55555.

Another possibility is that we get one assigned port. Use the assigned 
port for discovery and initial configuration. Then as part of the 
initial configuration switch to using ports from the Dynamic Ports range.

I think it would be difficult getting more than one port number 
assigned.  The assignment process is outlined in RFC 6335.


There is the issue that the port numbers in the Dynamic Ports range will 
use more bits in the datagrams.

The whole point of the Internet standards is to allow interoperability 
on the Internet. Will the contents of the Ethernet protocol every make 
it on to the Internet?


A link to a HTML version of RFC 6335,  http://tools.ietf.org/html/rfc6335

A link to HTML list of the assigned port numbers, 
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xht
ml


-Matthew Wolf, N4MTT






_______________________________________________
HPSDR Discussion List
To post msg: hpsdr at openhpsdr.org
Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
HPSDR web page: http://openhpsdr.org
Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/


 1452789932.0