RE: Evaluation: draft-ietf-atommib-opticalmib - Definitions of Ma naged Objects for the Optical Interface Type to Proposed Standard

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

The list of objects in a SEQUENCE construct just show that
those objects are the "columns" of which a "row" is constructed.
The details about each object then follow below that in the
form of OBJECT-TYPE definitions and that is where the object
details are specified, including a UNITs clause if appropriate.

Hope that explains and if so, pls remove your DISCUSS.

Thanks,
Bert 

> -----Original Message-----
> From: Steven M. Bellovin [mailto:smb@research.att.com]
> Sent: dinsdag 1 april 2003 2:30
> To: Wijnen, Bert (Bert)
> Cc: IESG Secretary; Internet Engineering Steering Group
> Subject: Re: Evaluation: draft-ietf-atommib-opticalmib - 
> Definitions of
> Ma naged Objects for the Optical Interface Type to Proposed Standard 
> 
> 
> In message 
> <7D5D48D2CAA3D84C813F5B154F43B15501483742@nl0006exch001u.nl.lucent.c
> om>, "Wijnen, Bert (Bert)" writes:
> >Steve, can you be specific, I see things like:
> >
> >optIfOTSnSinkIntervalLastInputPower OBJECT-TYPE
> >  SYNTAX  Integer32
> >  UNITS  "0.1 dbm"
> >
> >So which ones did you see without a UNITs clause?
> >
> 
> Maybe I'm misunderstanding something (quite likely with 
> something like 
> this).
> 
> OptIfOTSnSinkCurrentEntry ::=
>   SEQUENCE { 
>     optIfOTSnSinkCurrentSuspectedFlag             TruthValue,
>     optIfOTSnSinkCurrentInputPower                Integer32,
>     optIfOTSnSinkCurrentLowInputPower             Integer32,
>     optIfOTSnSinkCurrentHighInputPower            Integer32,
>     optIfOTSnSinkCurrentLowerInputPowerThreshold  Integer32,
>     optIfOTSnSinkCurrentUpperInputPowerThreshold  Integer32,
>     optIfOTSnSinkCurrentOutputPower               Integer32,
>     optIfOTSnSinkCurrentLowOutputPower            Integer32,
>     optIfOTSnSinkCurrentHighOutputPower           Integer32,
>     optIfOTSnSinkCurrentLowerOutputPowerThreshold Integer32,
>     optIfOTSnSinkCurrentUpperOutputPowerThreshold Integer32
>     }
> 
> Or is the forward pointer sufficient?  (If so, I (of course) withdraw 
> my comment.)
> 
> 		--Steve Bellovin, http://www.research.att.com/~smb (me)
> 		http://www.wilyhacker.com (2nd edition of 
> "Firewalls" book)
> 
> 
> 		--Steve Bellovin, http://www.research.att.com/~smb (me)
> 		http://www.wilyhacker.com (2nd edition of 
> "Firewalls" book)
> 
>