ipfix-15----Page:6
1 2 3 4 5 6 7 8
|
Option Template Record used in multiple streams? Sending the (Options) Template Records on every single streams is NOT POSSIBLE No backwards compatibility with the current Collecting Process [IPFIX-PROTO]: "Template IDs are unique per SCTP association and per Observation Domain. If the Collecting Process receives a Template which has already been received but which has not previously been withdrawn (i.e. a Template Record from the same Exporter Observation Domain with the same Template ID received on the SCTP association), then the Collecting Process MUST shutdown the association". Ideas (but not full solution) to lower the probability: “The Template Withdrawal Message MUST be sent in the last used stream that carried the Template ID to be removed” Notion of reuse timer for template withdrawal "Redefinition of the Template ID is not encouraged. Instead, new Template ID SHOULD be used, until the exhaustion of the Template ID space.“ MUST? |