Re: [IPFIX] Promotion of Enterprise-Specific IEs to IANA IEs

On 25/09/2012 00:18, Paul Aitken wrote:
> Benoit,
>
>>>> Consider the mechanism versus the content: there are two mechanisms 
>>>> (option versus URI), while the underlying content is the same.
>> Not quite.
>> The "IE equivalence options template" is for the situation when one 
>> exporter upgraded his software, and is aware of one new IE mapping 
>> (due to the software upgrade).
>> This "IE equivalence options template" is basically telling: "mister 
>> collector, you were receiving enterprise-specific IE X from me, and 
>> now I'm sending you the IANA IE Y: the two are equivalent"
>>
>> The "IE equivalence options template"  has the context of the 
>> exporter only, while the URI solution contains a URI to a vendor 
>> maintained IANA like registry
>
> Unless the new code can determine exactly what the previous version 
> was, and knows exactly which IEs that version exported, it can't 
> export such a specific equivalence option.
Good! It was the next point I wanted to address....
>
> So the normal situation would be for the new code to export a table 
> with all the equivalences which it knows.
>
> Also from an implementation perspective, it's easier to build the 
> equivalence table into every new product and export the whole table, 
> rather than determine the correct subset for the old code versus 
> current code.
>
> A simply collector could simply merge all the equivalence options into 
> an equivalence superset in order to know all possible equivalences in 
> the network. ie there's no need to maintain device-specific equivalences.
Instead, just point the collector to the URI with all the information. 
That's way easier for everybody: the exporters and the collector.

Regards, Benoit (as a contributor)
>
> P.
>
>

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix