RFC 7909: Securing Routing Policy Specification Language (RPSL) Objects with Resource Public Key Infrastructure (RPKI) Signatures
In plain English — editorial summary, not part of the RFC
This document describes a method that allows parties to electronically sign Routing Policy Specification Language objects and validate such electronic signatures. This allows relying parties to detect accidental or malicious modifications of such objects. It also allows parties who run Internet Routing Registries or similar databases, but do not yet have authentication (based on Routing Policy System Security) of the maintainers of certain objects, to verify that the additions or modifications of such database objects are done by the legitimate holder(s) of the Internet resources mentioned in those objects. This document updates RFCs 2622 and 4012 to add the signature attribute to supported RPSL objects.
Document record
- Document ID
- RFC7909
- Published
- June 2016
- Authors
- R. Kisteleki; B. Haberman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 7902Registry and Extensions for P-Multicast Service Interface Tunnel Attribute FlagsCurrent
June 2016
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- 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 7920Problem Statement for the Interface to the Routing SystemCurrent
June 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?