FW: RFC 4363 on Definitions of Managed Objects for B ridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensi ons

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C626D3.CF5BD5D8
Content-Type: text/plain

Congrats to the WG and specifically to the authors/editors/reviewers.

Bert

-----Original Message-----
From: [email protected] [mailto:[email protected]]On
Behalf Of [email protected]
Sent: Tuesday, January 31, 2006 16:57
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]
Subject: [Bridge-mib] RFC 4363 on Definitions of Managed Objects for
Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN
Extensions


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




        
        RFC 4363

        Title:      Definitions of Managed Objects for 
                    Bridges with Traffic Classes Multicast Filtering 
                    and Virtual LAN Extensions 
        Author:     D. Levi,  D. Harrington
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    [email protected], 
                    [email protected]
        Pages:      99
        Characters: 188981
        Obsoletes:  RFC2674
        See-Also:   

        I-D Tag:    draft-ietf-bridge-ext-v2-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4363.txt

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 4188 and obsoletes RFC 2674.  [STANDARDS TRACK]

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\\01) 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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...



------_=_NextPart_000_01C626D3.CF5BD5D8
Content-Type: text/plain;
	name="ATT122549.ATT"
Content-Disposition: attachment;
	filename="ATT122549.ATT"


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




        
        RFC 4363

        Title:      Definitions of Managed Objects for 
                    Bridges with Traffic Classes Multicast Filtering 
                    and Virtual LAN Extensions 
        Author:     D. Levi,  D. Harrington
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    [email protected], 
                    [email protected]
        Pages:      99
        Characters: 188981
        Obsoletes:  RFC2674
        See-Also:   

        I-D Tag:    draft-ietf-bridge-ext-v2-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4363.txt

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 4188 and obsoletes RFC 2674.  [STANDARDS TRACK]

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\\01) 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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...


------_=_NextPart_000_01C626D3.CF5BD5D8
Content-Type: text/plain;
	name="ATT122550.txt"
Content-Disposition: attachment;
	filename="ATT122550.txt"

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

------_=_NextPart_000_01C626D3.CF5BD5D8
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_01C626D3.CF5BD5D8--