[Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-05.txt

Internet-Drafts@ietf.org Mon, 28 July 2003 15:07 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04626 for <bridge-archive@odin.ietf.org>; Mon, 28 Jul 2003 11:07:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9a9-0000kJ-IG for bridge-archive@odin.ietf.org; Mon, 28 Jul 2003 11:06:37 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SF6bTr002865 for bridge-archive@odin.ietf.org; Mon, 28 Jul 2003 11:06:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9ZZ-0000iE-9d; Mon, 28 Jul 2003 11:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9Yv-0000hd-24 for bridge-mib@optimus.ietf.org; Mon, 28 Jul 2003 11:05:21 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04185; Mon, 28 Jul 2003 11:05:15 -0400 (EDT)
Message-Id: <200307281505.LAA04185@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: Mon, 28 Jul 2003 11:05:15 -0400
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-05.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
	Author(s)	: K. Norseth, E. Bell
	Filename	: draft-ietf-bridge-bridgemib-smiv2-05.txt
	Pages		: 38
	Date		: 2003-7-28
	
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 objects for managing MAC bridges based on
the IEEE 802.1D-1998 standard 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.
The MIB presented in this memo is a direct translation of the BRIDGE
MIB defined in [RFC1493], to the SMIv2 syntax required for current
IETF MIB standards.  This memo obsoletes RFC 1493.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-05.txt

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-bridgemib-smiv2-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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-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.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-05.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-05.txt>