[IPFIX] basicList clarification

[Gerald Naveen A <[e-mail]>]

Hi all,

It is my understanding from the RFCs that basicList type is an encoding for
list of IPFIX Information Elements.

To create the template much more strongly typed, we have defined a custom
(enterprise) Information Element with a new ID (say X), which is defined as
a basicList of specific items (eg., InterfaceName).

My question to you all is: Is it mandatory that we have a separate
information element called InterfaceName (say ID Y) and define X as a
basicList of Y ? For our need, it is enough for us, that we define X as a
basicList of string (as X is already strongly defined). But string is a
type, not info element.

We would like to retain X (instead of defining a template directly with a
standard basicList). And we don't have any other need to define a new
Information Element Y.

I realize that the basicList encoding has a information-element ID of the
item in payload -- is this mandatory? Or for a strongly typed item X, we
could expect the IPFIX parser to be aware of contents (interface name) by
contract?

Pls let me know if my question is unclear.

Thanks in advance.
- Gerald Naveen