[sidr] RFC 8210 on The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
rfc-editor@rfc-editor.org Thu, 28 September 2017 04:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3221352D0; Wed, 27 Sep 2017 21:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0IilRdgzlsX; Wed, 27 Sep 2017 21:14:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878C81352AC; Wed, 27 Sep 2017 21:14:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0F13BB814D0; Wed, 27 Sep 2017 21:13:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidr@ietf.org
Message-Id: <20170928041353.0F13BB814D0@rfc-editor.org>
Date: Wed, 27 Sep 2017 21:13:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/txaf3MiwPL1ots7H7sh2MyTpvR4>
Subject: [sidr] RFC 8210 on The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 04:14:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8210
Title: The Resource Public Key Infrastructure
(RPKI) to Router Protocol, Version 1
Author: R. Bush,
R. Austein
Status: Standards Track
Stream: IETF
Date: September 2017
Mailbox: randy@psg.com,
sra@hactrn.net
Pages: 35
Characters: 78467
Updates: RFC 6810
I-D Tag: draft-ietf-sidr-rpki-rtr-rfc6810-bis-09.txt
URL: https://www.rfc-editor.org/info/rfc8210
DOI: 10.17487/RFC8210
In order to verifiably validate the origin Autonomous Systems and
Autonomous System Paths of BGP announcements, routers need a simple
but reliable mechanism to receive Resource Public Key Infrastructure
(RFC 6480) prefix origin data and router keys from a trusted cache.
This document describes a protocol to deliver them.
This document describes version 1 of the RPKI-Router protocol. RFC
6810 describes version 0. This document updates RFC 6810.
This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC