Re: [bmwg] draft-vfv-bmwg-srv6-bench-meth

[Giuseppe Fioccola <[e-mail]>]

Hi Bruno,
Thanks a lot for the suggestions.
We plan to address your comments in the next version.
Please find my further replies inline tagged as [GF].

Regards,

Giuseppe

-----Original Message-----
From: [e-mail] <[e-mail]> 
Sent: Tuesday, February 14, 2023 11:32 AM
To: [e-mail]; Giuseppe Fioccola <[e-mail]>
Cc: [e-mail]
Subject: draft-vfv-bmwg-srv6-bench-meth

Hi Authors,

Thanks for the draft, this is an interesting draft.

I may have some suggestions for you and I would be interested in discussing those.

1)	SRH SID numbers
Just like the MTU section (§3.3) lists multiple recommended MTU, I think that it would be interesting for the document to specify multiple SRH SID numbers to test as this typically also has an impact on the forwarding performance. I would suggest the following value:
- 1 SID
- 5 SIDs
- 10 SIDs
- DUT maximal

[GF]: Fully agree to specify multiple SRH SID list numbers and we can start from the values you proposed.

2)	Throughput tests on nodes
- §5.1.1 (source node) definitely +1. I think that you should specify the SRv6 behavior to use (either H.Encaps or H.Encaps.Red up to you) as this may impact the performance.
- §5.1.2 (Endpoint) +1. I think that it would be more accurate to specify the SRv6 behavior (typically End) and specify the SL (SL max in order to text the first segment which is the one harder to read)
- §new one: I think that it would be useful to add a test with SRv6 decapsulation (e.g. End USD) as this is both a typical use case and a typical hardware limitation.

[GF]: Yes, we will include the SRv6 behavior for the tests of the source and endpoint nodes. It is also relevant to specify the SL pointer for the endpoint nodes. In addition, will also add a new test for the SRv6 decapsulation.

Nits:
:s/[I-D.ietf-spring-segment-routing-policy]/[RFC9256]
:s/ISIS/IS-IS

[GF]: We will fix it

Thanks,
Best regards,
--Bruno

_________________________________________________________________________________________________________________________

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.