Hi Éric,

Updated the name in my local copy.

I'm not sure to get your question. Can you please clarify? Thanks.

Cheers,
Med

De : Eric Vyncke (evyncke) <evyn...@cisco.com>
Envoyé : mercredi 11 octobre 2023 18:06
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; opsawg@ietf.org
Objet : Re: Length of EHs RE: About draft-boucadair-opsawg-ipfix-tcpo-v6eh

Hello Med

Indeed, I was not clear enough, what matters it the length of the extension 
headers chain not individual headers length.

Suggestion to s/ipv6ExtensionHeadersAggrLength/ipv6ExtensionHeadersChainLength/ 
to make it clear.

Now, what is the source of the IE ? The OS with a static value ?

From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> 
<mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>>
Date: Monday, 9 October 2023 at 16:39
To: Eric Vyncke (evyncke) <evyn...@cisco.com<mailto:evyn...@cisco.com>>, 
opsawg@ietf.org<mailto:opsawg@ietf.org> 
<opsawg@ietf.org<mailto:opsawg@ietf.org>>
Subject: Length of EHs RE: About draft-boucadair-opsawg-ipfix-tcpo-v6eh
Hi Éric, all,

> - what would also be SUPER interesting / useful is the length of those
> Ext Headers and their order...

The order part of the comment was already addressed.

For the length, I think that the aggregate length would be more useful to 
explain packet drops, use of slow paths, etc.

Please see a proposed PR to cover this issue at: 
https://github.com/boucadair/ipfix-tcpoptions-and-v6eh/pull/8/files.

Comments are more than welcome.

Cheers,
Med

> -----Message d'origine-----
> De : OPSAWG <opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org>> De la 
> part de Eric Vyncke
> (evyncke)
> Envoyé : samedi 27 mai 2023 18:17
> À : opsawg@ietf.org<mailto:opsawg@ietf.org>
> Objet : [OPSAWG] About draft-boucadair-opsawg-ipfix-tcpo-v6eh
>
> Benoît, Med,
>
> I just found draft-boucadair-opsawg-ipfix-tcpo-v6eh and the idea
> behind this I-D seems very attractive to me. Do you intend to request
> adoption ?
>
> BTW, if you do not mind some comments:
> - why not covering also IPv4 options ? Or split this I-D in two parts
> ?
> - how would an 'old' implementation (post a potential future
> publication of this I-D) differentiate between "unknown ext header"
> (this set is normally closed but who knows) and "unknown L4 header"
> and "unknow IP protocol" ?
> - ipv6ExtensionHeadersFull is redundant (always annoying) with
> ipv6ExtensionHeaderCount
> - what would also be SUPER interesting / useful is the length of those
> Ext Headers and their order...
>
> I look forward to reading (or even working with you) more on this I-D
>
> Regards
>
> -éric
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww<https://www/>.
> ietf.org%2Fmailman%2Flistinfo%2Fopsawg&data=05%7C01%7Cmohamed.boucadai
> r%40orange.com%7C602e6339fda948514e4308db5ecdd890%7C90c7a20af34b40bfbc
> 48b9253b6f5d20%7C0%7C0%7C638208010436919708%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300
> 0%7C%7C%7C&sdata=nIqtkrl%2FS5M5Oh2yUy4X8ITGHI8E4eTjDnmRqIio%2BhI%3D&re
> served=0
____________________________________________________________________________________________________________
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.
____________________________________________________________________________________________________________
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
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to