RFC 8502: L2L3 VPN Multicast MIB
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes two MIB modules that will be used by other MIB modules for monitoring and/or configuring Layer 2 and Layer 3 Virtual Private Networks that support multicast.
Document record
- Document ID
- RFC8502
- Published
- December 2018
- Authors
- Z. Zhang; H. Tsunoda
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8503BGP/MPLS Layer 3 VPN Multicast Management Information BaseCurrent
December 2018
- RFC 8669Segment Routing Prefix Segment Identifier Extensions for BGPCurrent
December 2019
- RFC 8950Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next HopCurrent
November 2020
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 7630HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3Obsoleted
October 2015
- RFC 3805Printer MIB v2Current
June 2004
- RFC 3638Applicability Statement for Reclassification of RFC 1643 to Historic StatusCurrent
October 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?