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

This is a multi-part message in MIME format.

------=_NextPart_000_0482_01C57E57.77AD0750
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,

This a new revision that addresses most of the issues raised by the
Area Director during his review of the document.

There are some changes to the Syntax and Descriptions within the MIB
modules, and to the compliance statements. I believe all the changes
are consistent with WG consensus. 

Please review this document to ensure that changes do not
substantially change the semantics of the design.

Thanks,
David Harrington
[email protected]
co-chair, IETF Bridge WG

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> [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 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Bridge MIB Working Group of the
IETF.
> 
> 	Title		: Definitions of Managed Objects for Bridges
>                           with Traffic Classes, Multicast 
> Filtering and
>                           Virtual LAN Extensions
> 	Author(s)	: V. Ngai, E. Bell
> 	Filename	: draft-ietf-bridge-ext-v2-05.txt
> 	Pages		: 102
> 	Date		: 2005-7-1
> 	
> This memo defines a portion of the Management Information Base (MIB)
>    for use with network management protocols in TCP/IP based 
> 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 managing
>    VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM) and P802.1v
>    (TM).
> 
>    Provisions are made for support of transparent bridging.  
> Provisions
>    are also made so that these objects apply to bridges connected by
>    subnetworks other than LAN segments.
> 
>    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)
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-bridge-ext-v2-05.txt
> 
> To remove yourself from the I-D Announcement list, send a message to

> [email protected] with the word unsubscribe in 
> the body of the message.  
> You can also visit 
> https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login 
> with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-bridge-ext-v2-05.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	[email protected].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-bridge-ext-v2-05.txt".
> 	
> 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 
> 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.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 

------=_NextPart_000_0482_01C57E57.77AD0750
Content-Type: Message/External-body;
	name="ATT01122.dat"
Content-Disposition: attachment;
	filename="ATT01122.dat"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID: <[email protected]>

ENCODING mime
FILE /internet-drafts/draft-ietf-bridge-ext-v2-05.txt

------=_NextPart_000_0482_01C57E57.77AD0750
Content-Type: Message/External-body;
	name="draft-ietf-bridge-ext-v2-05.txt"
Content-Disposition: attachment;
	filename="draft-ietf-bridge-ext-v2-05.txt"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID: <[email protected]>


------=_NextPart_000_0482_01C57E57.77AD0750
Content-Type: text/plain;
	name="ATT01125.txt"
Content-Disposition: attachment;
	filename="ATT01125.txt"
Content-Transfer-Encoding: 7bit

_______________________________________________
Bridge-mib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/bridge-mib

------=_NextPart_000_0482_01C57E57.77AD0750
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bridge-mib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/bridge-mib

------=_NextPart_000_0482_01C57E57.77AD0750--