[Sidrops] RFC 9255 on The 'I' in RPKI Does Not Stand for Identity

rfc-editor@rfc-editor.org Thu, 09 June 2022 04:54 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 0C391C14F612; Wed, 8 Jun 2022 21:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kuw0rlbRNwlo; Wed, 8 Jun 2022 21:54:51 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52EB9C159827; Wed, 8 Jun 2022 21:54:50 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7BF84CF503; Wed, 8 Jun 2022 21:54:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, auth48archive@rfc-editor.org
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: <20220609045450.7BF84CF503@rfcpa.amsl.com>
Date: Wed, 08 Jun 2022 21:54:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/DtF0ejVjXaZOYZflFD2I79vuXfI>
Subject: [Sidrops] RFC 9255 on The 'I' in RPKI Does Not Stand for Identity
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 09 Jun 2022 04:54:55 -0000

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

        
        RFC 9255

        Title:      The 'I' in RPKI Does Not Stand for Identity 
        Author:     R. Bush,
                    R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2022
        Mailbox:    randy@psg.com,
                    housley@vigilsec.com
        Pages:      7
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidrops-rpki-has-no-identity-07.txt

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

        DOI:        10.17487/RFC9255

There is a false notion that Internet Number Resources (INRs) in the
RPKI can be associated with the real-world identity of the 'holder'
of an INR.  This document specifies that RPKI does not associate to
the INR holder.

This document is a product of the SIDR Operations 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