RFC 8608 on BGPsec Algorithms, Key Formats, and Signature Formats

rfc-editor@rfc-editor.org Wed, 19 June 2019 16:50 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 7AD2C120316; Wed, 19 Jun 2019 09:50:59 -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 NUSogyHt9lDg; Wed, 19 Jun 2019 09:50:57 -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 F0F311202E4; Wed, 19 Jun 2019 09:50:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B68FAB81286; Wed, 19 Jun 2019 09:50:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2MDggb24gQkdQc2VjIEFsZ29yaXRobXMsIEtleSBGb3JtYXRzLCBhbmQgU2lnbmF0dXJlIEZvcm1hdHM=?=
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: <20190619165034.B68FAB81286@rfc-editor.org>
Date: Wed, 19 Jun 2019 09:50:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ZJYBZWOksTwbtNYASUpG3x_QSoA>
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 Jun 2019 16:51:04 -0000

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

        
        RFC 8608

        Title:      BGPsec Algorithms, Key Formats, and 
                    Signature Formats 
        Author:     S. Turner, O. Borchert
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2019
        Mailbox:    sean@sn3rd.com, 
                    oliver.borchert@nist.gov
        Pages:      21
        Characters: 43153
        Obsoletes:  RFC 8208
        Updates:    RFC 7935

        I-D Tag:    draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-05.txt

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

        DOI:        10.17487/RFC8608

This document specifies the algorithms, algorithm parameters,
asymmetric key formats, asymmetric key sizes, and signature formats
used in BGPsec (Border Gateway Protocol Security).  This document
updates RFC 7935 ("The Profile for Algorithms and Key Sizes for Use                           
in the Resource Public Key Infrastructure") and obsoletes RFC 8208
("BGPsec Algorithms, Key Formats, and Signature Formats") by adding
Documentation and Experimentation Algorithm IDs, correcting the range
of unassigned algorithms IDs to fill the complete range, and
restructuring the document for better reading.

This document also includes example BGPsec UPDATE messages as well as
the private keys used to generate the messages and the certificates
necessary to validate those signatures.

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