Re: [IPFIX] [Idr] discussion about exporting BGP community information in IPFIX
PJ Aitken <[email protected]> Wed, 7 Jun 2017 10:53:20 +0100
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <be981ea3-cc15-09a8-e46a-1fa054059c52__42814.3820063726$1496829239$gmane$org@brocade.com> |
--===============4401285883175752201== Content-Type: multipart/alternative; boundary="------------15A4C26C3A4803534CADE22A" Content-Language: en-GB --------------15A4C26C3A4803534CADE22A Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit What IPFIX message splitting method would you propose? Bear in mind that it must be backwards-compatible with existing collectors which do not expect message splitting. Rather than splitting messages, it might be acceptable simply to send longer messages. I think this would require a new version of IPFIX (eg, version 11) with the following modifications: * 32-bit Length in the Message Header (cf. RFC 7011 / Figure F) * 32 bit Field Length in the Field Specifier Format (cf. RFC 7011 / Figure G) * 32 bit Length in the Set Header Format (cf. RFC 7011 / Figure I) P. On 07/06/17 10:02, li zhenqiang wrote: > about question 1， the message length. > A WG > draft,https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-extended-messages/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Didr-2Dbgp-2Dextended-2Dmessages_&d=DwMGaQ&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=plGpWzcW7ppWguHBC4w6PyEGZRLkmX7MJ1vUTVNOpZs&s=0pin7tGPbPq5n1iayUcdxrEXuvzvTPplWdQkXERikBo&e=>, > extends the maximum update message sizeof BGP beyond 4096 bytes to 65535 bytes. So, > one IPFIX message may not be sufficient to fit all the communities > related to a specific flow. BGP speakers > that support the extended message feature > SHOULD takecare to handle the IPFIX message properly, such as only convey as many communities as possible in theIPFIX message. The collector that > receives an IPFIX message with maximum length and BGP communities > contained in its data set SHOULD be aware of the BGP communities may be truncated due to limited messagespace. In this case, it is RECOMMENDED to configure export policy on the exporter to limit the BGP communitiesto be exported, to export only some specific communities, for example, or not to export some communities. > > To solve this problem completely, we should update > IPFIX Protocol Specification RFC7011 to supportmessage splitting. > > Your comments are appreciated. > > ------------------------------------------------------------------------ > [email protected] --------------15A4C26C3A4803534CADE22A Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> What IPFIX message splitting method would you propose? Bear in mind that it must be backwards-compatible with existing collectors which do not expect message splitting.<br> <br> Rather than splitting messages, it might be acceptable simply to send longer messages. I think this would require a new version of IPFIX (eg, version 11) with the following modifications:<br> <br> * 32-bit Length in the Message Header (cf. RFC 7011 / Figure F)<br> * 32 bit Field Length in the Field Specifier Format (cf. RFC 7011 / Figure G)<br> * 32 bit Length in the Set Header Format (cf. RFC 7011 / Figure I)<br> <br> P.<br> <br> <br> <div class="moz-cite-prefix">On 07/06/17 10:02, li zhenqiang wrote:<br> </div> <blockquote type="cite" cite="mid:HK2PR0601MB13614AD1610E2FA97C21A682FCC80@HK2PR0601MB1361.apcprd06.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <style>body { line-height: 1.5; }blockquote { margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em; }div.foxdiv20170607164906554296 { }body { font-size: 10.5pt; font-family: 微软雅黑; color: rgb(0, 0, 0); line-height: 1.5; }</style> <div><span></span>about question 1， the message length. </div> <div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"></span><span style="color: rgb(0, 0, 0); font-size: 10.5pt; line-height: 1.5; background-color: rgba(0, 0, 0, 0);">A WG draft,</span><span style="font-size: 10.5pt; line-height: 1.5; background-color: window;"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Didr-2Dbgp-2Dextended-2Dmessages_&d=DwMGaQ&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=plGpWzcW7ppWguHBC4w6PyEGZRLkmX7MJ1vUTVNOpZs&s=0pin7tGPbPq5n1iayUcdxrEXuvzvTPplWdQkXERikBo&e=" style="font-size: 10.5pt; line-height: 1.5; background-color: window;" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-extended-messages/</a>, <span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">extends the maximum update message size</span><span style="color: rgb(0, 0, 0); font-size: 10.5pt; line-height: 1.5; background-color: rgba(0, 0, 0, 0);"> </span><span style="color: rgb(0, 0, 0); font-size: 10.5pt; line-height: 1.5; background-color: rgba(0, 0, 0, 0);">of BGP beyond 4096 bytes to 65535 bytes.</span><span style="color: rgb(0, 0, 0); font-size: 10.5pt; line-height: 1.5; background-color: rgba(0, 0, 0, 0);"> So, one IPFIX message may not be sufficient to fit all the communities related to a specific flow. BGP speakers </span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">that support the extended message feature SHOULD take<span style="white-space: pre;"> </span></span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">care to handle the IPFIX message properly, such as only convey as many communities as possible in the<span style="white-space: pre;"> </span></span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">IPFIX message. The collector that receives an IPFIX message with maximum length and BGP communities </span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">contained in its data set SHOULD be aware of the BGP communities may be truncated due to limited message<span style="white-space: pre;"> </span></span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">space. In this case, it is RECOMMENDED to configure export policy on the exporter to limit the BGP communities<span style="white-space: pre;"> </span></span><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">to be exported, to export only some specific communities, for example, or not to export some communities.</span></div> <div><span style="background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;"><br> </span></div> <div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">To solve this problem completely, we should update IPFIX Protocol Specification RFC7011 to support<span style="white-space: pre;"> </span>message splitting.</span></div> <div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"><br> </span></div> <div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">Your comments are appreciated.</span></div> <div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"><br> </span></div> <hr style="width: 210px; height: 1px;" color="#b5c4df" size="1" align="left"> <div><span> <div style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"> <div><a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></div> <span></span></div> </span></div> </blockquote> </body> </html> --------------15A4C26C3A4803534CADE22A-- --===============4401285883175752201== 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 --===============4401285883175752201==--