[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<mailto: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://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-tcpo-v6eh-15 [author-tools.ietf.org]<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-tcpo-v6eh-15__;!!OSsGDw!PqITvCWRU417BIOdV2vWvNScbHxKA-x1FpAP4Csq6nD-XAE2MtaoT2dJ4VLKvYTXkqMO9M1Di0uQpdnnTOWIKaAs$> Thanks. Cheers, Med De : Aitken, Paul <mailto:pait...@ciena.com> Envoyé : mercredi 22 mai 2024 22:25 À : BOUCADAIR Mohamed INNOV/NET <mailto:mohamed.boucad...@orange.com>; drafts-expert-review-comm...@iana.org<mailto:drafts-expert-review-comm...@iana.org> Cc : ie-doct...@ietf.org<mailto:ie-doct...@ietf.org>; opsawg <mailto:opsawg@ietf.org> Objet : 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 "may be encoded", even "MAY be", indicating that it's permissible to do so. Same issue at 4.1: The value of tcpOptionsFull IE is encoded in fewer octets per the guidelines in Section 6.2 of [RFC7011]. P. Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
[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 ; drafts-expert-review-comm...@iana.org Cc : ie-doct...@ietf.org; opsawg Objet : 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 "may be encoded", even "MAY be", indicating that it's permissible to do so. Same issue at 4.1: The value of tcpOptionsFull IE is encoded in fewer octets per the guidelines in Section 6.2 of [RFC7011]. P. Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
[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 "may be encoded", even "MAY be", indicating that it's permissible to do so. Same issue at 4.1: The value of tcpOptionsFull IE is encoded in fewer octets per the guidelines in Section 6.2 of [RFC7011]. P. ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
[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-review-comm...@iana.org Cc : ie-doct...@ietf.org; opsawg Objet : 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 contradict these paragraphs: 3.4. Each header chain in Flow with varying extension header chain MUST be exported in a separate IE. 3.6 Each header chain length of a Flow with varying extension header chain MUST be exported in a separate ipv6ExtensionHeadersChainLength IE. 6.1. remove ",and" : Figure 2 provides another example of reported values in an ipv6ExtensionHeadersFull IE for an IPv6 Flow in which the Destination Options (0), IPv6 Hop-by-Hop Options (1), and Routing (5), and headers are observed. P. Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
[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 contradict these paragraphs: 3.4. Each header chain in Flow with varying extension header chain MUST be exported in a separate IE. 3.6 Each header chain length of a Flow with varying extension header chain MUST be exported in a separate ipv6ExtensionHeadersChainLength IE. 6.1. remove ",and" : Figure 2 provides another example of reported values in an ipv6ExtensionHeadersFull IE for an IPv6 Flow in which the Destination Options (0), IPv6 Hop-by-Hop Options (1), and Routing (5), and headers are observed. P. ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
