RFC 7166: Supporting Authentication Trailer for OSPFv3
In plain English — editorial summary, not part of the RFC
Currently, OSPF for IPv6 (OSPFv3) uses IPsec as the only mechanism for authenticating protocol packets. This behavior is different from authentication mechanisms present in other routing protocols (OSPFv2, Intermediate System to Intermediate System (IS-IS), RIP, and Routing Information Protocol Next Generation (RIPng)). In some environments, it has been found that IPsec is difficult to configure and maintain and thus cannot be used. This document defines an alternative mechanism to authenticate OSPFv3 protocol packets so that OSPFv3 does not depend only upon IPsec for authentication. The OSPFv3 Authentication Trailer was originally defined in RFC 6506. This document obsoletes RFC 6506 by providing a revised definition, including clarifications and refinements of the procedures.
Document record
- Document ID
- RFC7166
- Published
- March 2014
- Authors
- M. Bhatia; V. Manral; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
- Obsoletes:
- RFC 6506
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7167A Framework for Point-to-Multipoint MPLS in Transport NetworksCurrent
April 2014
- RFC 7172Transparent Interconnection of Lots of Links (TRILL): Fine-Grained LabelingCurrent
May 2014
- RFC 7173Transparent Interconnection of Lots of Links (TRILL) Transport Using PseudowiresCurrent
May 2014
- RFC 7174Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
May 2014
- RFC 7175Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) SupportUpdated
May 2014
- RFC 7176Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISCurrent
May 2014
- RFC 7177Transparent Interconnection of Lots of Links (TRILL): AdjacencyUpdated
May 2014
- RFC 7178Transparent Interconnection of Lots of Links (TRILL): RBridge Channel SupportUpdated
May 2014
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?