[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: BER encoding of Unsigned32 and BITS

To: khchan@NortelNetworks.com
Subject: Re: BER encoding of Unsigned32 and BITS
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Tue, 9 Sep 2003 09:01:28 +0200
Cc: khchan@NortelNetworks.com, chum@noos.fr, rap@ops.ietf.org, khchan@NortelNetworks.com
In-reply-to: <5.2.0.9.0.20030908145246.0352c3e0@zbl6c002.corpeast.baynetworks.com> (message from Kwok Ho Chan on Mon, 08 Sep 2003 15:00:50 -0400)
References: < <5.2.0.9.0.20030905112405.028009f0@zbl6c002.corpeast.baynetworks.com> <E19uqMn-000DxX-T0@psg.com> <E19uqMn-000DxX-T0@psg.com> <5.2.0.9.0.20030905112405.028009f0@zbl6c002.corpeast.baynetworks.com> <5.2.0.9.0.20030908145246.0352c3e0@zbl6c002.corpeast.baynetworks.com>

>>>>> Kwok Ho Chan writes:

Kwok> The intent for the SPPI is to reuse as much of SMIv2 as
Kwok> possible.  I believe BITS is a construct created in SMIv2 (I
Kwok> think in the modified version).  And it is described in RFC 2578
Kwok> (SMIv2) section 7.1.4 on page 22.

Kwok,

we are discussing the _encoding_ of BITS and not the BITS construct
per se. As I wrote before, the _encoding_ of BITS when using SNMP is
defined in RFC 3417 section 8 and is not really defined for COPS-PR as
far as I can tell.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

References:
- Re: BER encoding of Unsigned32 and BITS
  - From: Kwok Ho Chan <khchan@NortelNetworks.com>
- BER encoding of Unsigned32 and BITS
  - From: "chum chum"<chum@noos.fr>
- Re: BER encoding of Unsigned32 and BITS
  - From: Kwok Ho Chan <khchan@NortelNetworks.com>

Prev by Date: Re: BER encoding of Unsigned32 and BITS
Next by Date: RSVP (or other recent reservation protocol) implementation
Previous by thread: Re: BER encoding of Unsigned32 and BITS
Next by thread: Re: BER encoding of Unsigned32 and BITS
Index(es):
- Date
- Thread