[rfc-dist] RFC 8642 on Policy Behavior for Well-Known BGP Communities

rfc-editor@rfc-editor.org Thu, 08 August 2019 04:50 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34CEA120111 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 7 Aug 2019 21:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 3DOGsDRQyJEr for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 7 Aug 2019 21:50:37 -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 81E201200A4 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 7 Aug 2019 21:50:35 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5D309B800B8; Wed, 7 Aug 2019 21:50:09 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 73148B800B4; Wed, 7 Aug 2019 21:50:08 -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
Message-Id: <20190808045008.73148B800B4@rfc-editor.org>
Date: Wed, 7 Aug 2019 21:50:08 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8642_on_Policy_Behavior_for_Well-Known_?= =?utf-8?q?BGP_Communities?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, grow@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8642

        Title:      Policy Behavior for Well-Known BGP 
                    Communities 
        Author:     J. Borkenhagen, 
                    R. Bush,
                    R. Bonica, 
                    S. Bayraktar
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2019
        Mailbox:    jayb@att.com, 
                    randy@psg.com, 
                    rbonica@juniper.net,  
                    serpil@cisco.com
        Pages:      7
        Characters: 13429
        Updates:    RFC 1997

        I-D Tag:    draft-ietf-grow-wkc-behavior-08.txt

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

        DOI:        10.17487/RFC8642

Well-known BGP communities are manipulated differently across various
current implementations, resulting in difficulties for operators.
Network operators should deploy consistent community handling across
their networks while taking the inconsistent behaviors from the
various BGP implementations into consideration.  This document
recommends specific actions to limit future inconsistency: namely,
BGP implementors must not create further inconsistencies from this
point forward.  These behavioral changes, though subtle, actually
update RFC 1997.

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org