[Bridge-mib] I-D ACTION:draft-ietf-bridge-rstpmib-04.txt

Internet-Drafts@ietf.org Thu, 25 March 2004 20:38 UTC

Received: from optimus.ietf.org (optimus.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19435 for <bridge-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:38:31 -0500 (EST)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6bc3-0005Uc-JY for bridge-archive@odin.ietf.org; Thu, 25 Mar 2004 15:38:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PKc3OB021088 for bridge-archive@odin.ietf.org; Thu, 25 Mar 2004 15:38:03 -0500
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6bc1-0005T6-1E; Thu, 25 Mar 2004 15:38:01 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6bbD-0005Gl-8j for bridge-mib@optimus.ietf.org; Thu, 25 Mar 2004 15:37:11 -0500
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19183; Thu, 25 Mar 2004 15:37:08 -0500 (EST)
Message-Id: <200403252037.PAA19183@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: Thu, 25 Mar 2004 15:37:08 -0500
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-rstpmib-04.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 Rapid Spanning Tree Protocol
	Author(s)	: E. Bell, V. Ngai
	Filename	: draft-ietf-bridge-rstpmib-04.txt
	Pages		: 18
	Date		: 2004-3-25
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 a MIB module for managing the Rapid
Spanning Tree capability defined by the IEEE P802.1t [802.1t] and
P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging
between Local Area Network (LAN) segments.
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 a MIB
module in a manner that is compliant to SMIv2 [RFC2578].

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-rstpmib-04.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-rstpmib-04.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