RFC 8195 on Use of BGP Large Communities

rfc-editor@rfc-editor.org Fri, 30 June 2017 22:53 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 0525C1314FF; Fri, 30 Jun 2017 15:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 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] 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 14HmdwJDAca9; Fri, 30 Jun 2017 15:53:19 -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 A3BD712EC61; Fri, 30 Jun 2017 15:52:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2F6FBB813F0; Fri, 30 Jun 2017 15:52:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8195 on Use of BGP Large Communities
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: <20170630225223.2F6FBB813F0@rfc-editor.org>
Date: Fri, 30 Jun 2017 15:52:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/V2b_Nam1sGMS6DkmyLfdb3pB61Y>
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: Fri, 30 Jun 2017 22:53:31 -0000

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

        
        RFC 8195

        Title:      Use of BGP Large Communities 
        Author:     J. Snijders, 
                    J. Heasley,
                    M. Schmidt
        Status:     Informational
        Stream:     IETF
        Date:       June 2017
        Mailbox:    job@ntt.net, 
                    heas@shrubbery.net, 
                    martijnschmidt@i3d.net
        Pages:      15
        Characters: 33281
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-large-communities-usage-07.txt

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

        DOI:        10.17487/RFC8195

This document presents examples and inspiration for operator
application of BGP Large Communities.  Based on operational
experience with BGP Communities, this document suggests logical
categories of BGP Large Communities and demonstrates an orderly
manner of organizing community values within them to achieve typical
goals in routing policy.  Any operator can consider using the
concepts presented as the basis for their own BGP Large Communities
repertoire.

This document is a product of the Global Routing Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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