[Bridge-mib] I-D ACTION:draft-ietf-bridge-ext-v2-01.txt

Internet-Drafts@ietf.org Tue, 24 September 2002 11:56 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23688 for <bridge-archive@odin.ietf.org>; Tue, 24 Sep 2002 07:56:07 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8OBvT526859 for bridge-archive@odin.ietf.org; Tue, 24 Sep 2002 07:57:29 -0400
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OBvEv26849; Tue, 24 Sep 2002 07:57:14 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OBslv26753 for <bridge-mib@optimus.ietf.org>; Tue, 24 Sep 2002 07:54:47 -0400
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23187; Tue, 24 Sep 2002 07:52:54 -0400 (EDT)
Message-Id: <200209241152.HAA23187@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: bridge-mib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 24 Sep 2002 07:52:54 -0400
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-ext-v2-01.txt
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>

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  
	Author(s)	: V. Ngai, E. Bell et al.
	Filename	: draft-ietf-bridge-ext-v2-01.txt
	Pages		: 88
	Date		: 2002-9-23
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 new
capabilities of MAC bridges defined by the IEEE 802.1D-1998 MAC
Bridges and the IEEE 802.1Q-1998 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.
The other MIB module defines objects for managing VLANs, as specified
in IEEE 802.1Q-1998, P802.1u and P802.1v.
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 also includes several
MIB modules in a manner that is compliant to the SMIv2 [V2SMI].
This memo supplements RFC 1493 [BRIDGEMIB] and (to a lesser extent)

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-01.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-bridge-ext-v2-01.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