RFC 6395: An Interface Identifier (ID) Hello Option for PIM
In plain English — editorial summary, not part of the RFC
This document defines a new PIM Hello option to advertise an Interface Identifier that can be used by PIM protocols to uniquely identify an interface of a neighboring router. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6395
- Published
- October 2011
- Authors
- S. Gulrajani; S. Venaas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6391Flow-Aware Transport of Pseudowires over an MPLS Packet Switched NetworkUpdated
November 2011
- RFC 6389MPLS Upstream Label Assignment for LDPCurrent
November 2011
- RFC 6388Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched PathsUpdated
November 2011
- RFC 6387GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)Current
September 2011
- RFC 6378MPLS Transport Profile (MPLS-TP) Linear ProtectionUpdated
October 2011
- RFC 6375A Packet Loss and Delay Measurement Profile for MPLS-Based Transport NetworksCurrent
September 2011
- RFC 6374Packet Loss and Delay Measurement for MPLS NetworksUpdated
September 2011
- RFC 6373MPLS Transport Profile (MPLS-TP) Control Plane FrameworkCurrent
September 2011
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?