RFC 7211: Operations Model for Router Keying
In plain English — editorial summary, not part of the RFC
The IETF is engaged in an effort to analyze the security of routing protocol authentication according to design guidelines discussed in RFC 6518, "Keying and Authentication for Routing Protocols (KARP) Design Guidelines". Developing an operational and management model for routing protocol security that works with all the routing protocols will be critical to the deployability of these efforts. This document gives recommendations to operators and implementors regarding management and operation of router authentication. These recommendations will also assist protocol designers in understanding management issues they will face.
Document record
- Document ID
- RFC7211
- Published
- June 2014
- Authors
- S. Hartman; D. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7210Database of Long-Lived Symmetric Cryptographic KeysCurrent
April 2014
- RFC 7212MPLS Generic Associated Channel (G-ACh) Advertisement ProtocolCurrent
June 2014
- RFC 7213MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet AddressingCurrent
June 2014
- RFC 7209Requirements for Ethernet VPN (EVPN)Current
May 2014
- RFC 7214Moving Generic Associated Channel (G-ACh) IANA Registries to a New RegistryCurrent
May 2014
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
- RFC 7196Making Route Flap Damping UsableCurrent
May 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
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?