RFC 8374 on BGPsec Design Choices and Summary of Supporting Discussions
rfc-editor@rfc-editor.org Wed, 25 April 2018 23:00 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 4EDB212EB52 for <ietf-announce@ietfa.amsl.com>; Wed, 25 Apr 2018 16:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 3FTjOKY4d36D for <ietf-announce@ietfa.amsl.com>; Wed, 25 Apr 2018 16:00:09 -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 B125412E8D2 for <ietf-announce@ietf.org>; Wed, 25 Apr 2018 15:59:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 318A1B810AF; Wed, 25 Apr 2018 15:59:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8374 on BGPsec Design Choices and Summary of Supporting Discussions
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180425225938.318A1B810AF@rfc-editor.org>
Date: Wed, 25 Apr 2018 15:59:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1yOUF4mgGmkM39LGhwH_Lx7iBSA>
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, 25 Apr 2018 23:00:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8374
Title: BGPsec Design Choices and Summary
of Supporting Discussions
Author: K. Sriram, Ed.
Status: Informational
Stream: Independent
Date: April 2018
Mailbox: ksriram@nist.gov
Pages: 50
Characters: 115388
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-sriram-bgpsec-design-choices-16.txt
URL: https://www.rfc-editor.org/info/rfc8374
DOI: 10.17487/RFC8374
This document captures the design rationale of the initial draft
version of what became RFC 8205 (the BGPsec protocol specification).
The designers needed to balance many competing factors, and this
document lists the decisions that were made in favor of or against
each design choice. This document also presents brief summaries of
the arguments that aided the decision process. Where appropriate,
this document also provides brief notes on design decisions that
changed as the specification was reviewed and updated by the IETF
SIDR Working Group and that resulted in RFC 8205. These notes
highlight the differences and provide pointers to details and
rationale regarding those design changes.
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