[OPSAWG]Re: [Ie-doctors] Re: [IANA #1363823] Expert review for draft-ietf-opsawg-ipfix-tcpo-v6eh (ipfix)

Thanks Med. David, I'm happy and approve draft-ietf-opsawg-ipfix-tcpo-v6eh-15. P. On 23/05/24 06:30, mohamed.boucad...@orange.com wrote: Hi Paul, What prevails in that text is the wording in the guidance. Made the changes to avoid confusion: https://auth

[OPSAWG]Re: [Ie-doctors] Re: [IANA #1363823] Expert review for draft-ietf-opsawg-ipfix-tcpo-v6eh (ipfix)

Hi Paul, What prevails in that text is the wording in the guidance. Made the changes to avoid confusion: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-tcpo-v6eh-15 Thanks. Cheers, Med De : Aitken, Paul Envoyé : mercredi 22 mai 2024 22:25 À : BOUCADAIR Mohamed INNOV/NET ;

[OPSAWG]Re: [Ie-doctors] Re: [IANA #1363823] Expert review for draft-ietf-opsawg-ipfix-tcpo-v6eh (ipfix)

Med, 3.3. ipv6ExtensionHeadersFull Information Element The value of ipv6ExtensionHeadersFull IE is encoded in fewer octets per the guidelines in Section 6.2 of [RFC7011]. If the value "is" encoded in fewer octets, then the defined size is simply too large. For clarity I'd say "ma

[OPSAWG]Re: [Ie-doctors] Re: [IANA #1363823] Expert review for draft-ietf-opsawg-ipfix-tcpo-v6eh (ipfix)

Hi Paul, Thanks for double checking. I don’t think there is a conflict between 3.3/3.4-3.6 because these are covering distinct aspects of the information export. Fixed the nit. Cheers, Med De : Aitken, Paul Envoyé : lundi 13 mai 2024 22:13 À : BOUCADAIR Mohamed INNOV/NET ; drafts-expert-rev

[OPSAWG]Re: [Ie-doctors] Re: [IANA #1363823] Expert review for draft-ietf-opsawg-ipfix-tcpo-v6eh (ipfix)

Med, 3.3. Extension headers observed in a Flow with varying extension header chain MAY be aggregated in one single ipv6ExtensionHeadersFull Information Element or be exported in separate ipv6ExtensionHeadersFull IEs, one for each extension header chain. Seems to contradi