[sidr] Last Call: <draft-ietf-sidr-bgpsec-ops-12.txt> (BGPsec Operational Considerations) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Wed, 07 December 2016 15:27 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: sidr@ietf.org
Delivered-To: sidr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D744129505; Wed, 7 Dec 2016 07:27:28 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <148112444860.13678.830966785604568036.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2016 07:27:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/NTfK74R-gGwA2XaF7VAzRhRkHqo>
Cc: Chris Morrow <morrowc@ops-netman.net>, sidr-chairs@ietf.org, draft-ietf-sidr-bgpsec-ops@ietf.org, sidr@ietf.org
Subject: [sidr] Last Call: <draft-ietf-sidr-bgpsec-ops-12.txt> (BGPsec Operational Considerations) to Best Current Practice
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2016 15:27:28 -0000

The IESG has received a request from the Secure Inter-Domain Routing WG
(sidr) to consider the following document:
- 'BGPsec Operational Considerations'
  <draft-ietf-sidr-bgpsec-ops-12.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-12-21. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Deployment of the BGPsec architecture and protocols has many
   operational considerations.  This document attempts to collect and
   present the most critical and universal.  It is expected to evolve as
   BGPsec is formalized and initially deployed.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-ops/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-ops/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6811: BGP Prefix Origin Validation (Proposed Standard - IETF stream)
    draft-ietf-sidr-bgpsec-protocol: BGPsec Protocol Specification (None - IETF stream)
    rfc6493: The Resource Public Key Infrastructure (RPKI) Ghostbusters Record (Proposed Standard - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.