RFC 8488 on RIPE NCC's Implementation of Resource Public Key Infrastructure (RPKI) Certificate Tree Validation
rfc-editor@rfc-editor.org Wed, 19 December 2018 05:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB573130F81; Tue, 18 Dec 2018 21:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 atuy6-bQZp5s; Tue, 18 Dec 2018 21:17:46 -0800 (PST)
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 68C841276D0; Tue, 18 Dec 2018 21:17:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A9C8CB80D59; Tue, 18 Dec 2018 21:17:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8488 on RIPE NCC's Implementation of Resource Public Key Infrastructure (RPKI) Certificate Tree Validation
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, sidrops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181219051718.A9C8CB80D59@rfc-editor.org>
Date: Tue, 18 Dec 2018 21:17:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Ucy6fzEtNhmyiC62usHpKgOIAdk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 05:17:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8488
Title: RIPE NCC's Implementation of Resource
Public Key Infrastructure (RPKI) Certificate Tree
Validation
Author: O. Muravskiy,
T. Bruijnzeels
Status: Informational
Stream: IETF
Date: December 2018
Mailbox: oleg@ripe.net,
tim@nlnetlabs.nl
Pages: 17
Characters: 35434
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sidrops-rpki-tree-validation-03.txt
URL: https://www.rfc-editor.org/info/rfc8488
DOI: 10.17487/RFC8488
This document describes an approach to validating the content of the
Resource Public Key Infrastructure (RPKI) certificate tree, as it is
implemented in the RIPE NCC RPKI Validator. This approach is
independent of a particular object retrieval mechanism, which allows
it to be used with repositories available over the rsync protocol,
the RPKI Repository Delta Protocol (RRDP), and repositories that use
a mix of both.
This document is a product of the SIDR Operations Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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