RE: MIB transition

["David B Harrington" <dbharrington@comcast.net>]

Hi Dan,

I haven't followed the ad or ah work, so you may be right - it may
require extensions or changes to the existing tables. 

If it requires extensions, they can be added under the 802 arc.

If the tables need to be changed, then the new columns can be defined
under the 802 arc, and new compliances can be written for
implementations that support ad and ah technologies. But I believe
many implementations will still function in non-provider environments,
so the existng MIB modules will likely remain viable for those who do
not implement ad and/or ah.

802.1h: "This project is intended to facilitate the scaling of
Provider Bridged P802.1ad networks using existing Bridged and Virtual
Bridged Local Area Network (VLAN) technologies." So apparently the
intention is not change the existing technology, but to supplement it.

David Harrington
dbharrington@comcast.net


> -----Original Message-----
> From: owner-mreview@ops.ietf.org 
> [mailto:owner-mreview@ops.ietf.org] On Behalf Of Romascanu, Dan
(Dan)
> Sent: Monday, October 10, 2005 1:23 PM
> To: dbharrington@comcast.net; MReview
> Subject: RE: MIB transition
> 
> Dave,
> 
> While agreeing with your analysis and with the 
> recommendations, I would
> like to point to one aspect that may be important in this
discussion.
> The IETF was very slow in following the pace of standards 
> development in
> the IEEE 802.1 Working Group so that from the perspective of the
IEEE
> the work that is just now being completed by the IETF 
> corresponds to the
> previous generation of bridge technology development.  
> 
> As you correctly point:
> 
> > In the Bridge WG, we didn't address all changes that have 
> > been incorporated into 802.1D-2004. Does anybody know of 
> > specific changes to 802.1D-2004 or the 802.1Q-REV or other 
> > 802.1 work that will REQUIRE a technical change to the 
> > existing IETF standards-track MIB modules?
> > 
> 
> The IEEE 802.1ad (Provider Bridges) and IEEE 802.1ah 
> (provider backbone)
> change the structure of the VLANs by allowing for an extended and
> hierarchical VLAN space to be defined. This will certainly 
> require some
> of the VLAN specific MIB tables to be extended or replaced. 
> 
> Regards,
> 
> Dan
> 
> 
>  
>  
> 
> > -----Original Message-----
> > From: owner-mreview@ops.ietf.org 
> > 
> 
>