Protocol Action: 'BGPsec Operational Considerations' to Best Current Practice (draft-ietf-sidr-bgpsec-ops-16.txt)

The IESG <> Mon, 09 January 2017 16:13 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id CB2C3129541; Mon, 9 Jan 2017 08:13:02 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'BGPsec Operational Considerations' to Best Current Practice (draft-ietf-sidr-bgpsec-ops-16.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 09 Jan 2017 08:13:02 -0800
Archived-At: <>
Cc:, Chris Morrow <>,, The IESG <>,,
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Jan 2017 16:13:03 -0000

The IESG has approved the following document:
- 'BGPsec Operational Considerations'
  (draft-ietf-sidr-bgpsec-ops-16.txt) as Best Current Practice

This document is the product of the Secure Inter-Domain Routing Working

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah

A URL of this Internet Draft is:

Technical Summary

   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.

Working Group Summary

   This draft went thorugh several revisions, with good discussion from 
   stake-holders in the communities affected.

Document Quality

   The document describes what the WG believes is the best way
   to implement/deploy BGPsec.  As it describes, it is expected to
   evolve as more experience is gained.


   Shepherd: Chris Morrow (
   AD: Alvaro Retana (

RFC Editor Note

This document should be published alongside draft-ietf-sidr-bgpsec-protocol and draft-ietf-sidr-as-migration so that they have consecutive RFC numbers in the following order: