[Bridge-mib] FW: RFC 4318 on Definitions of Managed Objects for Bridges with R apid Spanning Tree Protocol

Congrats, thanks to the WG and special thanks to the editors.

Bert

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org]On Behalf Of
rfc-editor@rfc-editor.org
Sent: Friday, December 23, 2005 22:39
To: ietf-announce@ietf.org
Cc: bridge-mib@ietf.org; rfc-editor@rfc-editor.org
Subject: RFC 4318 on Definitions of Managed Objects for Bridges with
Rapid Spanning Tree Protocol

A new Request for Comments is now available in online RFC libraries.

        RFC 4318

        Title:      Definitions of Managed Objects for Bridges
                    with Rapid Spanning Tree Protocol
        Author(s):  D. Levi, D. Harrington
        Status:     Standards Track
        Date:       December 2005
        Mailbox:    dlevi@nortel.com, ietfdbh@comcast.net
        Pages:      14
        Characters: 28124
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-bridge-rstpmib-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4318.txt

This memo defines an SMIv2 MIB module for managing the Rapid Spanning
Tree capability defined by the IEEE P802.1t and P802.1w amendments to
IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
segments.  The objects in this MIB are defined to apply both to
transparent bridging and to bridges connected by subnetworks other
than LAN segments.

This document is a product of the Bridge MIB Working Group of the
IETF. 

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib