Benoît and Med, Thanks for this document, please find below some comments on the IPv6 sections (4.1 and 9.1), obviously wearing no hat. I like the idea of creating a registry mapping IPFIX IE bits to IPv6 extension headers, even if there won’t be any new IPv6 extension headers.
Another important issue is to export whether the full extension header chain has been parsed as some HW can only process so many headers or so many bytes. In this case, the bit mask is obviously incomplete. This could of course be another bit in the mask and could be specified in the companion I-D, draft-ietf-opsawg-ipfix-tcpo-v6eh. # Section 9.1 Should there be an entry to “no next header” value ? Should there be different bits for “destination options” as this one can happen *before* and *after* routing header ? Similar to FRA0 and FRA1 bits ? Please replace the “IPv6 options” column by “IP protocol number” or “IPv6 Next-Header Values” Use “IPv6 Hop-by-Hop Options” (plural) per RFC 8200 (even the IANA-EH registry is singular) The first “Note” already appears a couple of lines above ;-) Hope this helps -éric
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
