Hi Zahed, 

Good question/catch. 

Fixed. Please see 
https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/ipfix-tcpoptions-and-v6eh/draft-ietf-opsawg-ipfix-tcpo-v6eh.txt&url_2=https://boucadair.github.io/ipfix-tcpoptions-and-v6eh/Zahed-catch/draft-ietf-opsawg-ipfix-tcpo-v6eh.txt

Thanks. 

Cheers,
Med

> -----Message d'origine-----
> De : Zaheduzzaman Sarker via Datatracker <nore...@ietf.org>
> Envoyé : jeudi 11 juillet 2024 11:06
> À : The IESG <i...@ietf.org>
> Cc : draft-ietf-opsawg-ipfix-tcpo-v...@ietf.org; opsawg-
> cha...@ietf.org; opsawg@ietf.org; thomas.g...@swisscom.com;
> thomas.g...@swisscom.com
> Objet : Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-
> ipfix-tcpo-v6eh-17: (with COMMENT)
> 
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-opsawg-ipfix-tcpo-v6eh-17: No Objection
> 
> When responding, please keep the subject line intact and reply to
> all email addresses included in the To and CC lines. (Feel free
> to cut this introductory paragraph, however.)
> 
> 
> -----------------------------------------------------------------
> COMMENT:
> -----------------------------------------------------------------
> 
> Thanks for working on this specification. Thanks to Wesley Eddy
> for his TSVART
> review. I think this specification is OK to publish from
> tranpsport protocol
> perspective.
> 
> However, this specification deprecates tcpOptions IE without
> updating (or
> obsolating) RFC 5102, so I am unsure about the operational issues
> and usage of
> the new IEs when we have tcpOption IE. Hence supporting Paul's
> discuss.
> 
> One question -
> 
> - Section 4.1: it says
>      "This approach allows an observer to export any observed TCP
> option even
>      if it does support that option and without requiring
> updating a mapping
>      table"
> 
>   Do you mean "even if it does *not* support that option"?
> 

____________________________________________________________________________________________________________
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

Reply via email to