RE: Review of EFM-04 I-D

You are correct, the zero part of (0|64..1518) is a mistake. 

- Matt

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:[email protected]]
> Sent: Thursday, May 11, 2006 11:07 AM
> To: David T. Perkins; Wijnen, Bert (Bert)
> Cc: [email protected]; [email protected]; Matt Squire
> Subject: RE: [Hubmib] Review of EFM-04 I-D
> 
> For that one I agree with your comment Dave.
> 
> Bert
> 
> > -----Original Message-----
> > From: David T. Perkins [mailto:[email protected]]
> > Sent: Thursday, May 11, 2006 16:44
> > To: Wijnen, Bert (Bert)
> > Cc: [email protected]; [email protected];
[email protected]
> > Subject: RE: [Hubmib] Review of EFM-04 I-D
> >
> >
> > HI,
> >
> > oops. Cut and paste error on my part. Should be
> > dot3OamPeerMaxOamPduSize.
> >
> > Regards,
> > /david t. perkins
> >
> > On Thu, 11 May 2006, Wijnen, Bert (Bert) wrote:
> >
> > > W.r.t.
> > >
> > > >
> > > > 4) The syntax of object dot3OamMaxOamPduSize is specified
> > > >     as "SYNTAX (0..1518)", but the text says values
> > > >     1..63 are not allowed. So, why not
> > > >     "SYNTAX (0 | 64..1518)
> > > >
> > >
> > > Mmmm... which document are you looking at?
> > > The   that I have says (on page 15)
> > >       dot3OamMaxOamPduSize OBJECT-TYPE
> > >         SYNTAX      Unsigned32 (64..1518)
> > >         UNITS       "octets"
> > >         MAX-ACCESS  read-only
> > >         STATUS      current
> > >         DESCRIPTION
> > >           "The largest OAMPDU that the OAM entity supports.  OAM
> > >           entities exchange maximum OAMPDU sizes and
> > negotiate to use
> > >           the smaller of the two maximum OAMPDU sizes
> > between the peers.
> > >           This value is determined by the local implementation.
> > >           "
> > >         REFERENCE   "[802.3ah], 30.3.6.1.8"
> > >         ::= { dot3OamEntry 4 }
> > >
> > > So it does not have (0..1518) and the DESCRIPTION clause
> > also does not tell
> > > me what a value of zero would mean ??
> > > I tried to find it in the 802.3ah spec, but have not found it
(yet).
> > >
> > > Bert
> > >
> >