| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 19:02:27 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=pq5kogqr44g8n9t2un5ljf6a09; path=/
set-cookie: __cf_bm=8raEWfAQJR18abjzX9c6gW3Oid23pgWiJQbiIc_kLZc-1760122947-1.0.1.1-vrXjw3tW37FIiDeQXEhI8PwTRjtarOFIs833Ygww2xHCZ5S7DKXdT8oR8h_sR1TnwC3GdaNrUTlW.Ls46od6jnwvEJKi5KRWdvHAiI29Qa0; path=/; expires=Fri, 10-Oct-25 19:32:27 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98c85f3c4ae5f473-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 1 record.
Status: Held for Document Update (1)
RFC 7132, "Threat Model for BGP Path Security", February 2014
Source of RFC: sidr (rtg)
Errata ID: 4454
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: David Mandelberg
Date Reported: 2015-08-25
Held for Document Update by: Alvaro Retana
Date Held: 2016-02-16
Section 1 says:
PATHSEC is intended to address the concerns cited above, to provide significantly improved path security, which builds upon the route origination validation capability offered by use of the RPKI [RFC6810].
It should say:
PATHSEC is intended to address the concerns cited above, to provide significantly improved path security, which builds upon the route origination validation capability offered by use of the RPKI [RFC6811].
Notes:
I think this text should reference RFC6811 (origin validation), not RFC6810 (the rpki-rtr protocol).
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us