[Sidrops] RFC 8897 on Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties

rfc-editor@rfc-editor.org Fri, 04 September 2020 00:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 411173A005E; Thu, 3 Sep 2020 17:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3S9xUVvJR3YA; Thu, 3 Sep 2020 17:40:20 -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 DDCE53A11F2; Thu, 3 Sep 2020 17:39:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 481FEF40763; Thu, 3 Sep 2020 17:39:21 -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, sidrops@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200904003921.481FEF40763@rfc-editor.org>
Date: Thu, 3 Sep 2020 17:39:21 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/uO-R1qVe1fkD4sx6i7zi6Ji0XqA>
Subject: [Sidrops] =?utf-8?q?RFC_8897_on_Requirements_for_Resource_Public?= =?utf-8?q?_Key_Infrastructure_=28RPKI=29_Relying_Parties?=
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Sep 2020 00:40:21 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8897

        Title:      Requirements for Resource Public Key 
                    Infrastructure (RPKI) Relying Parties 
        Author:     D. Ma, 
                    S. Kent
        Status:     Informational
        Stream:     IETF
        Date:       September 2020
        Mailbox:    madi@zdns.cn, 
                    kent@alum.mit.edu
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidrops-rp-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8897

        DOI:        10.17487/RFC8897

This document provides a single reference point for requirements for
Relying Party (RP) software for use in the Resource Public Key
Infrastructure (RPKI). It cites requirements that appear in several
RPKI RFCs, making it easier for implementers to become aware of these
requirements. Over time, this RFC will be updated to reflect changes
to the requirements and guidance specified in the RFCs discussed
herein.

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