[IPFIX] IE-doctors: transitioning IEs

Paul Aitken <[email protected]>
Newsgroups gmane.ietf.ipfix
Message-ID <[email protected]>
Brian,

In my IE-doctors reviews, I expressed some reservation about recording 
Enterprise-Specific information in IANA's IPFIX registry as specified in 
this text:

     In order to support transition from experimental registration to IANA
     registration, the IANA registry provides an optional "enterprise-
     specific IE reference" column for each Information Element.  In cases
     of promoted enterprise-specific Information Elements, this column in
     the registry SHOULD contain the private enterprise and Information
     Element numbers of the enterprise-specific version of the Information
     Element.


I've had a similar, but automated, idea in the back of my mind to for 
some years: an upgraded device could export a table mapping oldIE to 
newIE, where either of these IEs can be IANA standard or Enterprise 
Specific.

The table would be interpreted as "(if) I used to export oldIE, now I 
export newIE", so the Collecting Process can readily re-map exported 
data over the Exporting Process software change boundary. If the 
Collecting Process never received any oldIE elements, it can disregard 
the information.

With the IE doctors / IANA registry idea, the information has to be in 
the registry and the Collecting Process has to have read the new 
registry. So both the Exporting Process and Collecting Process must be 
updated.

With my idea, only the Exporting Process is updated, and it informs the 
Collecting Process.

I drafted a -00 on this last year which requires a little more work, so 
I've not published it yet.

Of course the two mechanisms are complementary rather than mutually 
exclusive. It's a question of which issues we're trying to solve.

P.



_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.