RE: I-D ACTION:draft-ietf-bridge-ext-v2-05.txt

I agree with David, that the changes reflect the WG consensus.=20

Dan


> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of David B Harrington
> Sent: Friday, July 01, 2005 11:11 PM
> To: 'Bridge-Mib (E-mail)'
> Subject: FW: [Bridge-mib] I-D ACTION:draft-ietf-bridge-ext-v2-05.txt=20
>=20
> Hi,
>=20
> This a new revision that addresses most of the issues raised=20
> by the Area Director during his review of the document.
>=20
> There are some changes to the Syntax and Descriptions within=20
> the MIB modules, and to the compliance statements. I believe=20
> all the changes are consistent with WG consensus.=20
>=20
> Please review this document to ensure that changes do not=20
> substantially change the semantics of the design.
>=20
> Thanks,
> David Harrington
> [email protected]
> co-chair, IETF Bridge WG
>=20
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of=20
> > [email protected]
> > Sent: Friday, July 01, 2005 3:50 PM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-ext-v2-05.txt
> >=20
> > A New Internet-Draft is available from the on-line Internet-Drafts=20
> > directories.
> > This draft is a work item of the Bridge MIB Working Group of the
> IETF.
> >=20
> > 	Title		: Definitions of Managed Objects for Bridges
> >                           with Traffic Classes, Multicast Filtering=20
> > and
> >                           Virtual LAN Extensions
> > 	Author(s)	: V. Ngai, E. Bell
> > 	Filename	: draft-ietf-bridge-ext-v2-05.txt
> > 	Pages		: 102
> > 	Date		: 2005-7-1
> > =09
> > This memo defines a portion of the Management Information Base (MIB)
> >    for use with network management protocols in TCP/IP based=20
> > internets.
> >    In particular, it defines two MIB modules for managing the
> >    capabilities of MAC bridges defined by the IEEE
> > 802.1D-1998 (TM) MAC
> >    Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN)
> standards
> >    for bridging between Local Area Network (LAN) segments.  One MIB
> >    module defines objects for managing the 'Traffic Classes' and
> >    'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and
> >    P802.1t-2001 (TM).  The other MIB module defines objects for=20
> > managing
> >    VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM) and P802.1v
> >    (TM).
> >=20
> >    Provisions are made for support of transparent bridging. =20
> > Provisions
> >    are also made so that these objects apply to bridges connected by
> >    subnetworks other than LAN segments.
> >=20
> >    This memo supplements RFC 1493bis, and obsoletes RFC 2674.
> >    (NOTE for RFC Ed.: all instances of 'RFC 1493bis' will need to be
> >    updated to reflect the new RFC number for draft-ietf-bridge-
> >    bridgemib-smiv2-10.txt)
> >=20
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-bridge-ext-v2-05.txt
> >=20
> > To remove yourself from the I-D Announcement list, send a message to
>=20
> > [email protected] with the word unsubscribe in=20
> the body of=20
> > the message.
> > You can also visit
> > https://www1.ietf.org/mailman/listinfo/I-D-announce
> > to change your subscription settings.
> >=20
> >=20
> > Internet-Drafts are also available by anonymous FTP. Login with the=20
> > username "anonymous" and a password of your e-mail address. After=20
> > logging in, type "cd internet-drafts" and then
> > 	"get draft-ietf-bridge-ext-v2-05.txt".
> >=20
> > A list of Internet-Drafts directories can be found in=20
> > http://www.ietf.org/shadow.html or=20
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.
> >=20
> > Send a message to:
> > 	[email protected].
> > In the body type:
> > 	"FILE /internet-drafts/draft-ietf-bridge-ext-v2-05.txt".
> > =09
> > NOTE:	The mail server at ietf.org can return the document in
> > 	MIME-encoded form by using the "mpack" utility.  To use this
> > 	feature, insert the command "ENCODING mime" before the "FILE"
> > 	command.  To decode the response(s), you will need "munpack"
> or
> > 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> > 	exhibit different behavior, especially when dealing with
> > 	"multipart" MIME messages (i.e. documents which have been
> split
> > 	up into multiple messages), so check your local documentation
> on
> > 	how to manipulate these messages.
> > 	=09
> > 	=09
> > Below is the data which will enable a MIME compliant mail reader=20
> > implementation to automatically retrieve the ASCII version of the=20
> > Internet-Draft.
> >=20
>=20