Paul, Fine for me. I did not realize that the specification for ipPayloadPacketSection changed since -03. Regards, Gerhard Paul Aitken wrote: > Gerhard, > >> I think Paul's concerns are important. >> >> Example: >> The standard IP header is 20 bytes long, but may be longer with options. >> You use a template with ipHeaderPacketSection and length 40 and want to >> export an IP packet that has a standard header only. There is payload >> which is indicated by the total length in the IP header. >> If the monitor now "blanks" the IP payload, your collector does not know >> if the payload originally was blank or not. The capability to decode the >> IP header information does not help. > > Blanking the payload is not allowed. See my reply to Thomas. > > Instead, the application would have been configured to only export > header information (no payload info), so it would have to create a new > template either with the necessary fixed length, or with a variable length. > > >> As a third solution, variable length IEs could be used (see >> draft-ietf-ipfix-protocol). > > This is allowed by solution (2). > -- Dipl.-Ing. Gerhard Münz Computer Networks and Internet Wilhelm Schickard Institute for Computer Science University of Tuebingen Auf der Morgenstelle 10C 9P16, D-72076 Tuebingen, Germany Phone: +49 7071 29-70534 / Fax: +49 7071 29-5220 EMail: muenz@informatik.uni-tuebingen.de WWW: http://net.informatik.uni-tuebingen.de/~muenz
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature