Dear Paul, Thanks a lot. I addressed both in -13 along with other IESG feedback.
There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-srv6-srh-13 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-srv6-srh-13 Best wishes Thomas From: Aitken, Paul <pait...@ciena.com> Sent: Tuesday, May 23, 2023 4:02 PM To: Graf Thomas, INI-NET-VNC-HCS <thomas.g...@swisscom.com> Cc: benoit.cla...@huawei.com; pierre.franc...@insa-lyon.fr; mohamed.boucad...@orange.com; opsawg@ietf.org Subject: Re: [**EXTERNAL**] RE: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt 3: "This section specifies the new IPv6 SRH IPFIX IEs." -> "... the new IPFIX IPv6 SRH IEs". 5.1: "Table 1 lists the new SRH IEs:" -> "... the new IPv6 SRH IEs" (because that's the title under the table). 5.2: Remove "(Section 5.2)". P. On 23/05/2023 14:35, thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com> wrote: Dear Paul and Med, Makes completely sense. I had the same thoughts. Thanks a lot. I submitted -12. Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-srv6-srh Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-srv6-srh-12 Best wishes Thomas From: Aitken, Paul <pait...@ciena.com><mailto:pait...@ciena.com> Sent: Tuesday, May 23, 2023 10:36 AM To: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>; Graf Thomas, INI-NET-VNC-HCS <thomas.g...@swisscom.com><mailto:thomas.g...@swisscom.com>; opsawg@ietf.org<mailto:opsawg@ietf.org> Cc: benoit.cla...@huawei.com<mailto:benoit.cla...@huawei.com>; pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> Subject: Re: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt In that case, I would update the names of sections 3 and 5.1 so that 5.1 and 5.2 are consistent, eg: 5.1. New IPFIX IPv6 SRH Information Elements 5.2. New IPFIX IPv6 SRH Segment Type Subregistry Moreover, please use consistent terminology around the words "IPFIX", "IPv6", and "SRH" / "SRv6". Although "IPFIX IPv6 SRH" is the most used, I also see these uses: 3. New SRH IPFIX Information Elements This section specifies the new SRv6 IPFIX IEs. Table 1: New SRv6 IEs in the "IPFIX Information Elements" Registry Thanks, P. On 23/05/2023 07:26, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: Hi Thomas, all, Thanks for implementing the changes. Looks good to me except one point: 5.1 as about new IEs. I think you should make this change: OLD: 5.1.10. New IPFIX IPv6 SRH Segment Type Subregistry NEW: 5.2. New IPFIX IPv6 SRH Segment Type Subregistry Cheers, Med De : thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com> <thomas.g...@swisscom.com><mailto:thomas.g...@swisscom.com> Envoyé : mardi 23 mai 2023 07:19 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com><mailto:mohamed.boucad...@orange.com>; pait...@ciena.com<mailto:pait...@ciena.com>; opsawg@ietf.org<mailto:opsawg@ietf.org> Cc : benoit.cla...@huawei.com<mailto:benoit.cla...@huawei.com>; pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> Objet : RE: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt Dear Paul and Med, Excellent. Thanks a lot for your suggestions. I merged them into the -11 version. There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-srv6-srh-11 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-srv6-srh-11 Best wishes Thomas From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Sent: Monday, May 22, 2023 2:50 PM To: Aitken, Paul <pait...@ciena.com<mailto:pait...@ciena.com>>; Graf Thomas, INI-NET-VNC-HCS <thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com>>; opsawg@ietf.org<mailto:opsawg@ietf.org> Cc: benoit.cla...@huawei.com<mailto:benoit.cla...@huawei.com>; pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> Subject: RE: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt Re-, The designed experts for this sub-registry should be familiar with SRH. I think your concern can be fixed by making this change: OLD: The guidelines that are being followed by the designated experts for .. NEW: The designed experts for this registry should be familiar with SRH. The guidelines that are being followed by the designated experts for .. The AD (Rob) will take that into account when selecting the DEs for this sub-registry. The good news is that the authors of draft-ietf-opsawg-ipfix-srv6-srh said that they volunteer to be DE for this registry. Cheers, Med De : Aitken, Paul <pait...@ciena.com<mailto:pait...@ciena.com>> Envoyé : lundi 22 mai 2023 13:10 À : Graf Thomas, INI-NET-VNC-HCS <thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com>>; BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>>; opsawg@ietf.org<mailto:opsawg@ietf.org> Cc : benoit.cla...@huawei.com<mailto:benoit.cla...@huawei.com>; pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> Objet : Re: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt 1) Yes, 5.1.9.1. could be renumbered to 5.2. But also modify the name to "New IPFIX IPv6 SRH Segment Type Subregistry", similar to the name of section 5.1. "New SRH Information Elements". Also watch for confusion between section 3's title and section 5.1: 3. New SRv6 IPFIX Information Elements 5.1. New SRH Information Elements 2) I specifically asked for the Expert Reviewers to be named, for two reasons: 1. Each registry lists the "Registration Procedure(s)" (Expert Review) and the corresponding "Expert(s)" (IE Doctors) - so it's necessary to provide both pieces of information. 2. Without specifying "SRH Experts", it might incorrectly be assumed that "IE Doctors" will be the expert reviewers. P. On 22/05/2023 09:38, thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com> wrote: Dear Med, Thanks a lot. Regarding your feedback on expert review, for me valid and ok but I am waiting on Paul's feedback if that make sense to him as well. Regarding, IPFIX IPv6 SRH Segment Type Subregistry. I believe the section is related to the srhIPv6ActiveSegmentType section. Therefore in the all the previous revisions of the document it was listed that way. For me to list it either under 5.1.9.1 or 5.2 works. Since it is the IANA section, lets get the opinion from Paul as well. I will adjust then accordingly. Best wishes Thomas -----Original Message----- From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> <mohamed.boucad...@orange.com><mailto:mohamed.boucad...@orange.com> Sent: Monday, May 22, 2023 8:50 AM To: opsawg@ietf.org<mailto:opsawg@ietf.org>; Graf Thomas, INI-NET-VNC-HCS <thomas.g...@swisscom.com><mailto:thomas.g...@swisscom.com> Cc: Aitken, Paul <pait...@ciena.com><mailto:pait...@ciena.com> Subject: RE: I-D Action: draft-ietf-opsawg-ipfix-srv6-srh-10.txt Hi Thomas, I think there was a bug in -10: s/5.1.9.1. IPFIX IPv6 SRH Segment Type Subregistry/5.2 IPFIX IPv6 SRH Segment Type Subregistry Also, for this text: The allocation policy of this new subregistry is Expert Review (Section 4.5 of [RFC8126]) by SRH Experts. I don't think we need to have ".. by SRH Experts" mentioned here given that the assigned DEs for this subregistry are IMO required to be familiar with SRH. If you think this is obvious and has to be recorded in the draft, I suggest the following: (1) OLD The allocation policy of this new subregistry is Expert Review (Section 4.5 of [RFC8126]) by SRH Experts. NEW: The allocation policy of this new subregistry is Expert Review (Section 4.5 of [RFC8126]). (2) OLD: The guidelines that are being followed by the designated experts for ... NEW: The designed experts for this registry should be familiar with SRH. The guidelines that are being followed by the designated experts for .. Thanks. Cheers, Med _________________________________________________________________________________________________________________________ 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.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
