[IPFIX] discussion about exporting BGP community information in IPFIX
li zhenqiang <[email protected]> Mon, 22 May 2017 06:49:51 +0000
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80__44792.3911423006$1495435811$gmane$org@HK2PR0601MB1361.apcprd06.prod.outlook.com> |
--===============7374838655162972367== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80HK2PR0601MB1361_" --_000_HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80HK2PR0601MB1361_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello experts from OPSAWG, IDR and IPFIX, This mail is to follow up the discussion in the mail lists and face to face= meetings. Since traffic aggregation in BGP community granularity is useful for severa= l applications such as backbone network traffic engineering, https://datatr= acker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/ introduces new in= formation elements(IEs) in IPFIX to export the BGP community information of= a specific traffic flow. At present, this draft only defines the IEs for s= tandard community specified in RFC1997. To solve the following two signific= ant questions raised in the previous meetings and mails, I solicit more com= ments and solution alternatives. Question 1: Does one IPFIX message have enough space to fit all the commun= ities related to a specific flow? BGP community, including standard, extended, large and community container,= is a path attribute of BGP distributed in an update message. Since the ma= ximum length of one BGP message is 4096 bytes as per RFC4271 and 64K bytes= for one IPFIX message as per RFC7011, the answer for this question SHOULD = be yes. Howerer, some experts say the specification for BGP message lenth i= n RFC4271 is out of date. Its length is not limited to 4096 bytes. But I d= o not know the new specification. Solution alternatives for this question a= re also welcomed. Question 2: Do we need to cover other kinds of BGP communities, such as ext= ended, large and community container? Based on previous discussion, large community defined in RFC8092 will be co= vered in the next version, since it has the same application purpose as sta= ndard community. Till now, we do not reach consensus about extended communi= ty defined in RFC4360 and community container defined in https://datatracke= r.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/. We usually do not use = the statistical information based on extended community or community contai= ner to do traffic engineering tasks. If you think it is useful to export th= ese two kinds of BGP community informaiton in IPFIX, please show your opini= ons and application use cases. Thank you all very much and best regards, ________________________________ [email protected] --_000_HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80HK2PR0601MB1361_ Content-Type: text/html; charset="us-ascii" Content-ID: <[email protected]> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <style>body { line-height: 1.5; }body { font-size: 10.5pt; font-family: ???= ?; color: rgb(0, 0, 0); line-height: 1.5; }</style> </head> <body> <div><span></span>Hello experts from OPSAWG, IDR and IPFIX,</div> <div><br> </div> <div>This mail is to follow up the discussion in the mail lists and face to= face meetings.</div> <div><br> </div> <div><span style=3D"color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0)= ;">Since traffic aggregation in BGP community = ;granularity is useful for several applications&nb= sp;such as backbone network traffic engineering,&n= bsp;</span><span style=3D"font-size: 10.5pt; line-height: 1.5; background-c= olor: window;"></span><a href=3D"https://datatracker.ietf.org/doc/draft-iet= f-opsawg-ipfix-bgp-community/" style=3D"font-size: 10.5pt; line-height: 1.5= ; background-color: window;">https://datatracker.ietf.org/doc/draft-ietf-op= sawg-ipfix-bgp-community/</a><span style=3D"font-size: 10.5pt; line-height:= 1.5; background-color: window;"> </span><span style=3D"background-col= or: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">introduces = ;new information elements(IEs) in IPFIX to export the&= nbsp;BGP community information of a specific = traffic flow. At present, this draft only defines the IEs for standard= community specified in RFC1997. To solve the following two significant que= stions raised in the previous meetings and mails, I solicit more comments and solution alternatives.</sp= an></div> <div><br> </div> <div>Question 1: <span style=3D"background-color: rgba(0, 0, 0, 0); fo= nt-size: 10.5pt; line-height: 1.5;">Does one IPFIX message&n= bsp; have enough space to fit all the&nb= sp;communities related to a specific flow? </= span></div> <div><span style=3D"color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0)= ;">BGP community, including standard, extended, la= rge and community container, is a path = attribute of BGP distributed in an update&nbs= p;message. Since the maximum length of one BGP message is 40= 96 bytes as per RFC4271 and 64K bytes for= one IPFIX message as per RFC7011, the answer= for this question SHOULD be yes. Howerer, some experts say the specificati= on for BGP message lenth </span><span style=3D"font-size: 10.5pt; line= -height: 1.5; background-color: window;">in RFC4271</span><span style=3D"font-size: 10.5pt; line-height: 1.5; backgrou= nd-color: window;"> </span><span style=3D"background-color: rgba(0, 0,= 0, 0); font-size: 10.5pt; line-height: 1.5;"> is out of date. Its len= gth is not limited to 4096 bytes. But I do not know the new specification. Solution alternatives for this question are al= so welcomed.</span></div> <div><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; = line-height: 1.5;"><br> </span></div> <div><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; = line-height: 1.5;">Question 2: </span><span style=3D"background-color:= rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">Do we ne= ed to cover other kinds of BGP communiti= es, such as </span><span style=3D"font-size: 10.5pt; line-height: 1.5;= background-color: window;">extended, large and community container</span><span style=3D"background-color: rgba(0, 0, 0, 0); font-si= ze: 10.5pt; line-height: 1.5;">?</span></div> <div><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; = line-height: 1.5;">Based on previous discussion, large community defined in= RFC8092 will be covered in the next version, since it has the same applica= tion purpose as standard community. Till now, we do not reach consensus about extended community defined in RF= C4360 and community container defined in </span><span style=3D"backgro= und-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;"></span><= a href=3D"https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communit= ies/" style=3D"font-size: 10.5pt; line-height: 1.5; background-color: windo= w;">https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/</= a>. We usually do not use the statistical information based on extended commun= ity or community container to do traffic engineering tasks. If you think it= is useful to export these two kinds of BGP community informaiton in IPFIX,= please show your opinions and application use cases. </div> <div><br> </div> <div>Thank you all very much and best regards,</div> <div><br> </div> <span style=3D"color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"></= span> <hr style=3D"width: 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" align= =3D"left"> <div><span> <div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"> <div>[email protected]</div> </div> </span></div> </body> </html> --_000_HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80HK2PR0601MB1361_-- --===============7374838655162972367== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix --===============7374838655162972367==--