Re: [IPFIX] IE-doctors: transitioning IEs
Paul Aitken <[email protected]>
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
Benoit, > I'm wondering if this equivalent Options Template is not an overkill. > > Let me explain: > _All _the exporters should export this IE equivalent Options Template > to help the collector deduce the mapping between old/new IEs If the exporter begins to use different IEs, yes. > If one of the exporters doesn't export the equivalent Options > Template, the collector should anyway maintain its own mapping. > Mapping that could be find in IANA. This requires the collector to be able to query IANA - which isn't always possible. Or the collector manufacturer queries IANA and issues an updated collector (ie, new software version). The proposed idea requires no enterprise-specific information to be recorded in IANA - because it simply does not belong there! And it provides a mechanism where collectors are immediately aware of the equivalence of old and new IEs without requiring any software update. > Isn't it a good practice anyway that the collectors should insert the > latest IANA info on regular basis? Perhaps. However, we know that some customers can test equipment in their labs for months or years before putting new versions into production. It's unlikely that they'd allow their collector to query IANA since this opens a potential attack vector if someone can inject incorrect information via the IANA registry lookup (eg, by DNS spoofing). > So which problem does this equivalent Options Template really solve? When an exporter begins to use a new IE (eg, IANA versus enterprise-specific), it enables a collector to process data received before the change with data received after the change without any software update being required. P. _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix