Ethereal-dev: Re: [ethereal-dev] Adding new protocols

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: David Frascone <dave@xxxxxxxxxxxx>
Date: Sun, 30 Jul 2000 06:45:13 -0500
On Sun, Jul 30, 2000 at 12:12:23AM -0700, Guy Harris wrote:
> On Fri, Jul 21, 2000 at 06:43:36AM -0500, David Frascone wrote:
> > Wow!  You read the draft!  Well then, on that particular draft, you probably
> > noticed that diameter does not run over UDP anymore *grin*.
> 
> So does RADIUS run over SCTP?  Or is the RADIUS Packet Compatibility
> Code there only for historical reasons?

Historical reasons.  Diameter originally ran on UDP (and there are plenty of
implementations out there that still do) and TCP.  The AAA Wg (and the IESG) did
not like mulitple protocols.  So, it was reduced to UDP.  Then the IESG wanted
Diameter to be run over SCTP, instead of using it's own reliable transport
protocol over UDP.  

The reason I included a TCP dissector is that most people will be converting
over to TCP as an interim to SCTP.  (Since most SCTP implementations are going
to try to minic the TCP calls (socket, bind, connect, etc))

> 
> > Right now, I needed the sniffer for the UDP version.  Soon, I'll need to 
> > dissect TCP and then SCTP packets.
> 
> Presumably there will be an SCTP dissector that plugs into IP the way
> the TCP and UDP dissectors plug in, and that have a port table similar
> to TCP's and UDP's port tables, for the benefit of other protocols
> running atop SCTP.

There will.  I talked to (e-mailed) the author of the SCTP dissector, and he'll
have it sub-dissectorable soon.