Re: [Gen-art] [OPSAWG] Genart early review of draft-ietf-opsawg-ipfix-bgp-community-04

Randy Bush <randy@psg.com> Thu, 01 March 2018 22:21 UTC

Return-Path: <randy@psg.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C56C124BE8; Thu, 1 Mar 2018 14:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CAnikupnPNEe; Thu, 1 Mar 2018 14:21:15 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 092571200C1; Thu, 1 Mar 2018 14:21:15 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1erWZY-0000NM-4F; Thu, 01 Mar 2018 22:21:08 +0000
Date: Fri, 02 Mar 2018 07:21:06 +0900
Message-ID: <m24llz30a5.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: li zhenqiang <li_zhenqiang@hotmail.com>
Cc: Joel Halpern Direct <jmh.direct@joelhalpern.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-opsawg-ipfix-bgp-community.all@ietf.org" <draft-ietf-opsawg-ipfix-bgp-community.all@ietf.org>, opsawg <opsawg@ietf.org>
In-Reply-To: <HKNPR0601MB17946383EC5074A29F98CFACFCC60@HKNPR0601MB1794.apcprd06.prod.outlook.com>
References: <151819723555.1208.12835539554987861622@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/FKN3XLkr1koZvyXmPwafYORIaWo>
Subject: Re: [Gen-art] [OPSAWG] Genart early review of draft-ietf-opsawg-ipfix-bgp-community-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 22:21:16 -0000

> Let me try to explain it clearly in simple words again. BGP community
> attributes, such as standard community, extended community, large
> community, have already been defined by IDR working group. Operaters
> use those already defined BGP communities in their field networks with
> their own plans to represent the groups of customers, peers,
> geographical and topological regions. For example, using standard
> community XXX to represent fixed line customers, YYY for WLAN
> customers, and ZZZ for mobile customers, using community AAA for state
> L, BBB for state M, CCC for state N. Now we want to know the traffic
> generated by the WLAN customer in state N. So we need the community
> information related to the traffic flow exported by IPFIX. If IPFIX
> can export BGP community information using the IEs introduced in my
> doc, the IPFIX collector, without running BGP protocol, can easily
> figure up the traffic in BGP community granularity, i.e. the traffic
> from different customers, from different states, from different
> customers in different states, and so on.

to help readers, perhaps this flavor explanation belongs in the
introduction, or a rationale section?

randy