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

Re: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t



On Sun, 5 Oct 2003, Juergen Schoenwaelder wrote:
> On Thu, Oct 02, 2003 at 09:03:50AM -0700, C. M. Heard wrote:
> > >[Juergen Schoenwaelder wrote:] 
> > > So perhaps the new TCs should in fact go into an update of RFC 2674
> > > rather than introducing a new module? This would at least side-step
> > > this interesting problem...
> > 
> > This approach would solve the "legal" problems but it does
> > have some significant drawbacks:
> > 
> > - It's necessary to re-spin RFC 2674.  Bert has suggested an
> > incremental update as one way to get around this.
> > 
> > - It causes any module that imports VlanID and kin to depend
> > normatively on the P-BRIDGE-MIB.  The upshot would be that absent a
> > variance of some kind, no module importing VlanID and kin could
> > advance on the standards track faster than P-BRIDGE-MIB.  That's not
> > desirable, because changes to things that are unrelated to  VlanID
> > and kin could hold back advancement.
> 
> So what is your suggestion how RFC 2674 should pick up the new
> TCs? Or is your suggestion to leave RFC 2674 alone?

I think it's probably best to leave RFC 2674 alone, unless we decide
to change the rules on standards-track advancement for MIB modules.

//cmh