Re: I-D ACTION:draft-ietf-bridge-8021x-03.txt

"C. M. Heard" <[email protected]> Thu, 20 Nov 2003 18:26:45 -0800 (PST)
Newsgroups gmane.ietf.bridge
Message-ID <[email protected]>
On Thu, 20 Nov 2003, Randy Presuhn wrote:
> > From: "C. M. Heard" <[email protected]>
> > To: <[email protected]>
> > Sent: Thursday, November 20, 2003 7:32 AM
> > Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt
> ...
> > 6.) In Section 7:  add RFC 1213 as a normative reference.  That is
> > needed because of its mention in Section 3.5.
> ...
> 
> It would be better to replace it with a reference to RFC 3418.

I don't object, but I would like to point out that it's not as
simple as just changing the reference.  Section 3.5 be would also
need to be modified along the following lines:

OLD:
   It is assumed that a system implementing this MIB will also implement
   (at least) the system group defined in MIB-II defined in IETF RFC
   1213 and the interfaces group defined in IETF RFC 2863.
NEW:
   It is assumed that a system implementing this MIB will also implement
   (at least) the system group defined in MIB-II defined in IETF RFC
   3418 and the interfaces group defined in IETF RFC 2863.

Since RFC 3418 (actually RFC 1907) expanded the system group by
adding sysORLastChange, sysORID, sysORUpTime, and sysORDescr to the
RFC 1213 objects sysDescr, sysObjectID, sysUpTime, sysContact,
sysName, sysLocation, and sysServices, this would not be a purely
editorial change and therefore should be vetted by the IEEE.

Mike