[sidr] RFC 8211 on Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)
rfc-editor@rfc-editor.org Thu, 28 September 2017 04:15 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 AE6B61352BD; Wed, 27 Sep 2017 21:15:27 -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 XoyL_ERHQqoa; Wed, 27 Sep 2017 21:15:19 -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 CDB2A1352B4; Wed, 27 Sep 2017 21:14:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 58F26B814DD; Wed, 27 Sep 2017 21:14:06 -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: <20170928041406.58F26B814DD@rfc-editor.org>
Date: Wed, 27 Sep 2017 21:14:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/UpGG7Vr4zIafKAByLGtfaSgiwDE>
Subject: [sidr] RFC 8211 on Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)
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:15:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8211
Title: Adverse Actions by a Certification
Authority (CA) or Repository Manager in
the Resource Public Key Infrastructure (RPKI)
Author: S. Kent,
D. Ma
Status: Informational
Stream: IETF
Date: September 2017
Mailbox: kent@alum.mit.edu,
madi@zdns.cn
Pages: 26
Characters: 64041
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sidr-adverse-actions-04.txt
URL: https://www.rfc-editor.org/info/rfc8211
DOI: 10.17487/RFC8211
This document analyzes actions by or against a Certification
Authority (CA) or an independent repository manager in the RPKI that
can adversely affect the Internet Number Resources (INRs) associated
with that CA or its subordinate CAs. The analysis is done from the
perspective of an affected INR holder. The analysis is based on
examination of the data items in the RPKI repository, as controlled
by a CA (or an independent repository manager) and fetched by Relying
Parties (RPs). The analysis does not purport to be comprehensive; it
does represent an orderly way to analyze a number of ways that errors
by or attacks against a CA or repository manager can affect the RPKI
and routing decisions based on RPKI data.
This document is a product of the Secure Inter-Domain Routing 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