RFC 6506: Supporting Authentication Trailer for OSPFv3
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7166.
Current version: 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 only depend upon IPsec for authentication. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6506
- Published
- February 2012
- Authors
- M. Bhatia; V. Manral; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
- Obsoleted by:
- RFC 7166
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6907Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying PartiesCurrent
March 2013
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 5796Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local MessagesCurrent
March 2010
- RFC 9582A Profile for Route Origin Authorizations (ROAs)Current
May 2024
- RFC 9829Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number ExtensionsCurrent
July 2025
- RFC 9981Resource Public Key Infrastructure (RPKI) Manifest Number HandlingCurrent
May 2026
- RFC 6510Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes ObjectsCurrent
February 2012
- RFC 6511Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched PathsCurrent
February 2012
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?