[sidr] RFC 8206 on BGPsec Considerations for Autonomous System (AS) Migration

rfc-editor@rfc-editor.org Thu, 28 September 2017 04:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B631352C0; Wed, 27 Sep 2017 21:13:32 -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 E9f-ysl2gxrm; Wed, 27 Sep 2017 21:13:21 -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 64ABE1352B4; Wed, 27 Sep 2017 21:13:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D292EB81466; Wed, 27 Sep 2017 21:12:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20170928041249.D292EB81466@rfc-editor.org>
Date: Wed, 27 Sep 2017 21:12:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/fgdxlGVEV0jr5u6XhOxL9xuHWOM>
Subject: [sidr] RFC 8206 on BGPsec Considerations for Autonomous System (AS) Migration
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Thu, 28 Sep 2017 04:13:32 -0000

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

        
        RFC 8206

        Title:      BGPsec Considerations for 
                    Autonomous System (AS) Migration 
        Author:     W. George, 
                    S. Murphy
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2017
        Mailbox:    wesgeorge@puck.nether.net, 
                    sandy@tislabs.com
        Pages:      16
        Characters: 36491
        Updates:    RFC 8205

        I-D Tag:    draft-ietf-sidr-as-migration-06.txt

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

        DOI:        10.17487/RFC8206

This document discusses considerations and methods for supporting and
securing a common method for Autonomous System (AS) migration within
the BGPsec protocol.

This document is a product of the Secure Inter-Domain Routing 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