Yes I agree that EtherNet/IP isn't a very good name if you're not familiar with industrial ethernet. If it make sence I think that the name shall be chaged to CIP, as you state.
In fact this was the name we first used, we made the name change since the name CIP also applyes to DeviceNet and ControlNet. EtherNet/IP uses some parts that isn't included in the CIP common specification, therefore we decided to call the dissector EtherNet/IP instaed of CIP.
If you think that we should call the dissector CIP instead to avoid confusion, I'm happy with that.
-----Ursprungligt meddelande-----
Från: Guy Harris [mailto:gharris@xxxxxxxxx]
Skickat: fr 2003-06-06 21:45
Till: Joakim Wiberg
Kopia: ethereal-dev@xxxxxxxxxxxx
Ämne: Re: [Ethereal-dev] Dissector for EtherNet/IP
On Fri, Jun 06, 2003 at 05:16:40PM -0500, Joakim Wiberg wrote:
> Attached is a dissector for EtherNet/IP, along with a capture file with some
> EtherNet/IP traffic.
Unfortunately, "EtherNet/IP" can be a confusing name if you're
unfamiliar with that particular family of industrial networking
protocols - my first thought when I saw your message was "but we already
*have* dissectors for Ethernet and IP, and the IP dissector registers
itself so that it's called for IP-over-Ethernet packets, so we already
support Ethernet/IP".
Would it be better to call it a dissector for the Common Industrial
Protocol, or would that be confusing to the industrial network users
who'd use Ethereal to dissect those protocols?