RFC 8212 on Default External BGP (EBGP) Route Propagation Behavior without Policies

rfc-editor@rfc-editor.org Wed, 05 July 2017 22:52 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 E3878126B72; Wed, 5 Jul 2017 15:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 yAhFOFy-4DLa; Wed, 5 Jul 2017 15:52:36 -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 12A60127201; Wed, 5 Jul 2017 15:52:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9D7F3B818A8; Wed, 5 Jul 2017 15:51:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8212 on Default External BGP (EBGP) Route Propagation Behavior without Policies
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, grow@ietf.org
Message-Id: <20170705225158.9D7F3B818A8@rfc-editor.org>
Date: Wed, 05 Jul 2017 15:51:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/H_zswTNuJQeX8tKY5BO12gJUfAY>
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, 05 Jul 2017 22:52:38 -0000

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

        
        RFC 8212

        Title:      Default External BGP (EBGP) Route 
                    Propagation Behavior without Policies 
        Author:     J. Mauch, 
                    J. Snijders,
                    G. Hankins
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2017
        Mailbox:    jared@akamai.com, 
                    job@ntt.net, 
                    greg.hankins@nokia.com
        Pages:      7
        Characters: 12552
        Updates:    RFC 4271

        I-D Tag:    draft-ietf-grow-bgp-reject-08.txt

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

        DOI:        10.17487/RFC8212

This document updates RFC 4271 by defining the default behavior of a
BGP speaker when there is no Import or Export Policy associated with
an External BGP session.

This document is a product of the Global Routing Operations 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