RFC 7902: Registry and Extensions for P-Multicast Service Interface Tunnel Attribute Flags
In plain English — editorial summary, not part of the RFC
The BGP-based control procedures for Multicast Virtual Private Networks (MVPNs) make use of a BGP attribute known as the "P-Multicast Service Interface (PMSI) Tunnel" attribute. The attribute contains a one-octet "Flags" field. The purpose of this document is to establish an IANA registry for the assignment of the bits in this field. Since the "Flags" field contains only eight bits, this document also defines a new BGP Extended Community, "Additional PMSI Tunnel Attribute Flags", that can be used to carry additional flags for the "P-Multicast Service Interface (PMSI) Tunnel" attribute. This document updates RFC 6514.
Document record
- Document ID
- RFC7902
- Published
- June 2016
- Authors
- E. Rosen; T. Morin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 6514
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7900Extranet Multicast in BGP/IP MPLS VPNsUpdated
June 2016
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7898Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE)Current
June 2016
- RFC 7897Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7896Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7909Securing Routing Policy Specification Language (RPSL) Objects with Resource Public Key Infrastructure (RPKI) SignaturesCurrent
June 2016
- RFC 7893Pseudowire Congestion ConsiderationsCurrent
June 2016
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
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?