On Wed, Oct 22, 2003 at 12:30:41AM -0700, Terry Lambert wrote: > Peter Jeremy wrote: > > >As with the Linux driver, communication happens at the ethernet link > > >layer, using protocol number 0x0666 (entertaining choice). > > > > If Linux is using 0x0666, we should probably pick a different number > > since we're not wire compatible. Though coming up with a common > > protocol would be even better. > > 0x666 hex is 1638 decimal, and it's taken: > > cnip 1638/tcp CableNet Info Protocol > cnip 1638/udp CableNet Info Protocol That would be relevant if this protocol used TCP or UDP. My understanding is that it doesn't, in which case those port assignments are quite irrelevant. Looking at the protocol types listed in /usr/include/net/ethernet.h seems more relevant, unless I have misunderstood something. > > Basically, this is just an experimental protocol that's being played > with here, and if it ever becomes real, then it will need an IANA > protocol number assignment before it's widely deployed. Are you sure that IANA would be the right organisation, since AIUI this isn't a protocol running on top of IP ? > > -- Terry -- <Insert your favourite quote here.> Erik Trulsson ertr1013_at_student.uu.seReceived on Wed Oct 22 2003 - 01:14:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:26 UTC