Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions
RFC 4363, “Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions”, is a Proposed Standard document published in January 2006 by D. Levi, D. Harrington. It obsoletes RFC 2674. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4363 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4362 RObust Header Compression : A Link-Layer Assisted Profile for IP/UDP/RTP
- RFC 4364 BGP/MPLS IP Virtual Private Networks
- RFC 4361 Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four
- RFC 4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks
- RFC 4360 BGP Extended Communities Attribute
- RFC 4366 Transport Layer Security Extensions
- RFC 4359 The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload and Authentication Header
- RFC 4367 What's in a Name: False Assumptions about DNS Names