RFC Errata
RFC 6313, "Export of Structured Data in IP Flow Information Export (IPFIX)", July 2011
Source of RFC: ipfix (ops)
Errata ID: 2925
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Paul Aitken
Date Reported: 2011-08-08
Held for Document Update by: ron bonica
Section Appendix A says:
<enumeration value="basicList"> <annotation> <documentation> Represents a list of zero or more instances of any Information Element, primarily used for single-valued data types. Examples include a list of port numbers, a list of interface indexes, and a list of AS in a BGP AS-PATH. </documentation> </annotation> </enumeration> ... <enumeration value="subTemplateList"> <annotation> <documentation> Represents a list of zero or more instances of a structured data type, where the data type of each list element is the same and corresponds with a single Template Record. Examples include a structured data type composed of multiple pairs of ("MPLS label stack entry position", "MPLS label stack value"), a structured data type composed of performance metrics, and a structured data type composed of multiple pairs of IP address. </documentation> </annotation> </enumeration> ... <enumeration value="subTemplateMultiList"> <annotation> <documentation> Represents a list of zero or more instances of structured data types, where the data type of each list element can be different and corresponds with different Template definitions. An example is a structured data type composed of multiple access-list entries, where entries can be composed of different criteria types. </documentation> </annotation> </enumeration>
It should say:
<enumeration value="basicList"> <annotation> <documentation>The type "basicList" represents a list of zero or more instances of any Information Element, primarily used for single-valued data types. Examples include a list of port numbers, a list of interface indexes, and a list of AS in a BGP AS-PATH. </documentation> </annotation> </enumeration> ... <enumeration value="subTemplateList"> <annotation> <documentation>The type "subTemplateList" represents a list of zero or more instances of a structured data type, where the data type of each list element is the same and corresponds with a single Template Record. Examples include a structured data type composed of multiple pairs of ("MPLS label stack entry position", "MPLS label stack value"), a structured data type composed of performance metrics, and a structured data type composed of multiple pairs of IP address. </documentation> </annotation> </enumeration> ... <enumeration value="subTemplateMultiList"> <annotation> <documentation>The type "subTemplateMultiList" represents a list of zero or more instances of structured data types, where the data type of each list element can be different and corresponds with different Template definitions. An example is a structured data type composed of multiple access-list entries, where entries can be composed of different criteria types. </documentation> </annotation> </enumeration>
Notes:
Addition of 'The type "basicList"', 'The type "subTemplateList"' and 'The type "subTemplateMultiList"', for consistency with the existing descriptions which all begin 'The type xxx ...'.
Note that this refers to text on page 63, for modifications to the IPFIX schema. The schema has been updated with the corrected text above.