[IPFIX] basicList clarification

--===============0980959870494551969==
Content-Type: multipart/alternative; boundary=089e013cba48bd1a040526af3e7f

--089e013cba48bd1a040526af3e7f
Content-Type: text/plain; charset=UTF-8

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

--089e013cba48bd1a040526af3e7f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div>Hi all,<br><br></div>It is m=
y understanding from the RFCs that basicList type is an encoding for list o=
f IPFIX Information Elements.<br><br></div>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 (e=
g., InterfaceName).<br><br></div>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, tha=
t we define X as a basicList of string (as X is already strongly defined). =
But string is a type, not info element.<br><br></div>We would like to retai=
n X (instead of defining a template directly with a standard basicList). An=
d we don&#39;t have any other need to define a new Information Element Y.<b=
r><br>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) b=
y contract? <br><br></div><div>Pls let me know if my question is unclear.<b=
r></div><div><br></div>Thanks in advance.<br></div>- Gerald Naveen<br></div=
>

--089e013cba48bd1a040526af3e7f--


--===============0980959870494551969==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0980959870494551969==--