Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)

[[e-mail]]

Hi all,

This version addresses all the comments raised in my previous review of the document. I have only very few comments:


  *   Section “5.9.  srhActiveSegmentIPv6Type”: please add the pointer to the IANA registry under “Additional Information”.
  *   Section 6.3:
     *   Is there any SPRING document that explains the motivation for having more than one SRH?
     *   Please reword these two sentences:

   OLD:

   [RFC8200] describes the support of multiple extension headers in one

   IPv6 packet.  Allowing the use of multiple SRH per SRv6 packet.


     *   I’m afraid the SHOULD normative language for the ordering is not required as it is redundant (?) with this part from RFC7011:

   If an Information Element is required more than once in a Template,
   the different occurrences of this Information Element SHOULD follow
   the logical order of their treatments by the Metering Process.


     *   What is an “active SRH”?

I support advancing this spec assuming these comments are addressed. Thanks.

Cheers,
Med

De : OPSAWG <[e-mail]> De la part de Joe Clarke (jclarke)
Envoyé : mercredi 30 novembre 2022 14:54
À : [e-mail]
Objet : [OPSAWG] 🔔 WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)

Hello, WG.  As discussed at IETF 115, we want to conduct a WG LC for draft-ietf-opsawg-ipfix-srv6-srh.  The authors believe this work is stable and moreover used the 115 hackathon to develop a interoperable implementations (linked in Data Tracker) .  Additionally, IANA has already weighed in on this work and agree with the considerations approach.

Therefore, we are calling for a two week LC.  We will conclude on December 14.

https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/

Please review the current -04 draft, post your comments and/or your thoughts on the current text.

Thanks.

Joe

_________________________________________________________________________________________________________________________

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.