Ethereal-dev: Re: [Ethereal-dev] COPS dissector update

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

From: Heikki Vatiainen <hessu@xxxxxxxxx>
Date: Tue, 17 Oct 2000 00:08:35 +0300
Ashok Narayanan <ashokn@xxxxxxxxx> wrote:

> How do you handle the client-specific objects? For COPS/RSVP do you
> pass the client-specific objects (which are RSVP messages) tothe RSVP dissector?

The cops dissector does not handle client-specific objects yet. The
dissector currently only knows about RFC 2748, and does not pass
the contents of ClientSI object or any other objects that have been
flagged as "client-type specific" to other dissectors.

We have a COPS-PR implementation as a part of something that a good
willed person could call the beginnings of a bandwidth broker, so I
will probably add a dissector for QoS clients if I manage to get
the appropriate PIBs [1] to work with the SNMP decoder. However, if
someone else has planned this, please go ahead :-)

I just took a look at the COPS-RSVP RFC and adding support for it
looks quite straight forward to do. The problem is that it is not
possible for us to test the dissector, so I think I will not mess 
with it.

BTW, I found CISCO-QOS-PIB-MIB.my from Cisco. Is there any public
documentation about the COPS-PR-like protocol that e.g. Catalyst
6500 series use?

[1] Policy (Provisioning ?) Information Base, looks just like a MIB.

Heikki
-- 
Heikki Vatiainen                  * hessu@xxxxxxxxx
Tampere University of Technology  * Tampere, Finland