Hi Randy, Thanks. Will add this flavor explanation in the new version.
Best Regards, Zhenqiang Li ________________________________ [email protected] From: Randy Bush<mailto:[email protected]> Date: 2018-03-02 06:21 To: li zhenqiang<mailto:[email protected]> CC: Joel Halpern Direct<mailto:[email protected]>; Dongjie (Jimmy)<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; opsawg<mailto:[email protected]> Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-ipfix-bgp-community-04 > 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
_______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
