RFC 8181 on A Publication Protocol for the Resource Public Key Infrastructure (RPKI)

rfc-editor@rfc-editor.org Wed, 26 July 2017 21:30 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 822991317C1; Wed, 26 Jul 2017 14:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 ePwohz9wsOuM; Wed, 26 Jul 2017 14:30:26 -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 E3064131471; Wed, 26 Jul 2017 14:30:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9628DB81913; Wed, 26 Jul 2017 14:30:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8181 on A Publication Protocol for the Resource Public Key Infrastructure (RPKI)
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: <20170726213016.9628DB81913@rfc-editor.org>
Date: Wed, 26 Jul 2017 14:30:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/TLoddIrtT2gQwaI7krxuX2qV7-k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Jul 2017 21:30:28 -0000

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

        
        RFC 8181

        Title:      A Publication Protocol for the 
                    Resource Public Key Infrastructure (RPKI) 
        Author:     S. Weiler,
                    A. Sonalker,
                    R. Austein
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2017
        Mailbox:    weiler@csail.mit.edu, 
                    anuja@steer-tech.com, 
                    sra@hactrn.net
        Pages:      21
        Characters: 38546
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-publication-12.txt

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

        DOI:        10.17487/RFC8181

This document defines a protocol for publishing Resource Public Key
Infrastructure (RPKI) objects.  Even though the RPKI will have many
participants issuing certificates and creating other objects, it is
operationally useful to consolidate the publication of those objects.
Even in cases where a certificate issuer runs its own publication
repository, it can be useful to run the certificate engine itself on
a different machine from the publication repository.  This document
defines a protocol which addresses these needs.

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