RFC 8549 on Export of BGP Community Information in IP Flow Information Export (IPFIX)

rfc-editor@rfc-editor.org Wed, 03 April 2019 03:06 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 0F95212044F; Tue, 2 Apr 2019 20:06:50 -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 pXacmwLA8zax; Tue, 2 Apr 2019 20:06:46 -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 E161B1200A3; Tue, 2 Apr 2019 20:06:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A603B82421; Tue, 2 Apr 2019 20:06:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg1NDkgb24gRXhwb3J0IG9mIEJHUCBDb21tdW5pdHkgSW5mb3JtYXRpb24gaW4gSVAgRmxvdyBJbmZvcm1hdGlvbiBFeHBvcnQgKElQRklYKQ==?=
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, opsawg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190403030632.7A603B82421@rfc-editor.org>
Date: Tue, 2 Apr 2019 20:06:32 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/n5quFJ3nsgpgQfiy_EeMSUCoBw0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Apr 2019 03:06:50 -0000

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

        
        RFC 8549

        Title:      Export of BGP Community Information 
                    in IP Flow Information Export (IPFIX) 
        Author:     Z. Li, 
                    R. Gu,
                    J. Dong
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    li_zhenqiang@hotmail.com, 
                    gurong_cmcc@outlook.com, 
                    jie.dong@huawei.com
        Pages:      18
        Characters: 43692
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-ipfix-bgp-community-12.txt

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

        DOI:        10.17487/RFC8549

By introducing new Information Elements (IEs), this document extends
the existing BGP-related IEs to enable IP Flow Information Export
(IPFIX) to export BGP community information, including the BGP
Standard Communities defined in RFC 1997, BGP Extended Communities
defined in RFC 4360, and BGP Large Communities defined in RFC 8092.
According to the network operator's BGP community planning, network
traffic information can then be accumulated and analyzed at the BGP
community granularity, which represents the traffic of different
kinds of customers, services, or geographical regions.  Network
traffic information at the BGP community granularity is useful for
network traffic analysis and engineering.

This document is a product of the Operations and Management Area Working Group 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