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]
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
