BCP 211, RFC 8207 on BGPsec Operational Considerations
rfc-editor@rfc-editor.org Thu, 28 September 2017 04:13 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 9A6871344E2; Wed, 27 Sep 2017 21:13:58 -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 5s0dKZZubB9F; Wed, 27 Sep 2017 21:13: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 BD7511352C5; Wed, 27 Sep 2017 21:13:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4F1C1B814A3; Wed, 27 Sep 2017 21:13:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 211, RFC 8207 on BGPsec Operational Considerations
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: <20170928041309.4F1C1B814A3@rfc-editor.org>
Date: Wed, 27 Sep 2017 21:13:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GyLUOnbJQB2MChiYXSptWeAClAQ>
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: Thu, 28 Sep 2017 04:13:58 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 211
RFC 8207
Title: BGPsec Operational Considerations
Author: R. Bush
Status: Best Current Practice
Stream: IETF
Date: September 2017
Mailbox: randy@psg.com
Pages: 10
Characters: 21086
See Also: BCP 211
I-D Tag: draft-ietf-sidr-bgpsec-ops-16.txt
URL: https://www.rfc-editor.org/info/rfc8207
DOI: 10.17487/RFC8207
Deployment of the BGPsec architecture and protocols has many
operational considerations. This document attempts to collect and
present the most critical and universal. Operational practices are
expected to evolve as BGPsec is formalized and initially deployed.
This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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