Hi Tianran, Thanks a lot for the review and comments.
Regarding your question why it is a standards and not a informational document.
We consulted with the IPFIX IE doctors and went for a standards document
because we create a new IPFIX registry: "IPFIX IPv6 SRH Flags" subregistry. We
will follow the recommendations from the WG chair, IPFIX IE doctors, and AD.
As per your suggestion we found two cases were it should be "MUST" instead of
"must" and will address it in the next draft version and do a normative
reference to RFC 2119.
Before: This doesn't impose any data flow manipulation on the exporter,
facilitating the immediate export. However, the data collection must be able to
decode the IPv6 addresses according the SR specifications. Compared to the
srhSegmentIPv6BasicList, the srhSegmentIPv6ListSection flow records length is
slightly reduced.
New: This doesn't impose any data flow manipulation on the exporter,
facilitating the immediate export. However, the data collection MUST be able to
decode the IPv6 addresses according the SR specifications. Compared to the
srhSegmentIPv6BasicList, the srhSegmentIPv6ListSection flow records length is
slightly reduced.
Before: The Length must be calculated to include the optional Type Length Value
objects.
New: The Length MUST be calculated to include the optional Type Length Value
objects.
Best wishes
Thomas
-----Original Message-----
From: Tianran Zhou <zhoutian...@huawei.com>
Sent: Monday, July 25, 2022 5:16 AM
To: Benoit Claise <benoit.claise=40huawei....@dmarc.ietf.org>; Graf Thomas,
INI-NET-TCZ-ZH1 <thomas.g...@swisscom.com>; spr...@ietf.org; opsawg@ietf.org
Cc: pierre.franc...@insa-lyon.fr
Subject: RE: [spring] FW: New Version Notification for
draft-tgraf-opsawg-ipfix-srv6-srh-04.txt
Hi Benoit,
Thanks for bringing this up.
I have been monitoring the discussions on this draft in SPRING and OPSAWG.
As I suggested, please copy your discussions to OPSAWG also, so that we know
the progress.
Basically, this draft is simple and straight forward. It's quite similar to
rfc9160 also produced by OPSAWG.
Here are some of my comments:
1. I see the use case section is still rather simple. I am not sure if you have
plan to expand. IMO, more details on how to use the proposed IEs is very useful
and builds an important part of this document.
2. We can discuss the "Intended status" of this draft, as a similar document
rfc9160 is informational. I searched the shepherd review of rfc9160, and there
is the following record:
The intended status is justified given that the document includes
informative use cases to illustrate the use of the new types
and it does not include any normative statements. Moreover, the
registration policy for the target IANA registry (MPLS label types)
is "Expert Review".
So, if it's the same situation here?
3. I see many lowercase "must" appears in the draft. Please check if some of
them should be "MUST".
Cheers,
Tianran
-----Original Message-----
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Benoit Claise
Sent: Tuesday, July 19, 2022 2:42 PM
To: thomas.g...@swisscom.com; spr...@ietf.org
Cc: pierre.franc...@insa-lyon.fr
Subject: Re: [spring] FW: New Version Notification for
draft-tgraf-opsawg-ipfix-srv6-srh-04.txt
Dear all,
Note that the authors will request WG adoption in the OPSAWG next week.
So feel free to join that meeting and/or post your comments via email.
Regards, Benoit
On 6/29/2022 6:53 AM, thomas.g...@swisscom.com wrote:
> Dear spring working group,
>
> draft-tgraf-opsawg-ipfix-srv6-srh defines new IPFIX entities where the SRH
> and associated control-plane related dimensions are exposed to enable SRv6
> data-plane visibility.
>
> The draft has been introduced and presented at IETF 113 to OPSAWG and SPRING
> where we collected the first comments and requested adoption at OPSAWG.
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2F113%2Fmaterials%2Fslides-113-opsawg-export-of-segment-routing-ipv6-information-in-ipfix-01&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mCoyzP3JTr5Nw8OtAEQMjHiZMnS9sQ%2BiqOcQ7WqCIO8%3D&reserved=0
>
> We just published -04 version and would like to collect additional comments
> and feedback.
>
> The main changes between version -03 and -04 are:
>
> - srhSegmentLocatorLength and srhSegmentEndpointBehavior has been added
> and included in the use case and operational section description
> - aligned IE naming according to
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc7012%23section-2.3&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=66odyGUs0s1NdH2R5CRBivrOPYhR3R6Eg3Sk%2FUvbMfo%3D&reserved=0
> - updated srhFlagsIPv6 registry
> - Added "Compressed SRv6 Segment List Decomposition" in operational
> consideration section
> - Added data-template and data-record examples for
> srhSegmentIPv6ListSection and srhSectionIPv6 in example section
>
> Best wishes
> Thomas
>
> -----Original Message-----
> From: internet-dra...@ietf.org <internet-dra...@ietf.org>
> Sent: Wednesday, June 29, 2022 6:35 AM
> To: Benoit Claise <benoit.cla...@huawei.com>; Pierre Francois
> <pierre.franc...@insa-lyon.fr>; Graf Thomas, INI-NET-TCZ-ZH1
> <thomas.g...@swisscom.com>
> Subject: New Version Notification for draft-tgraf-opsawg-ipfix-srv6-srh-04.txt
>
>
> A new version of I-D, draft-tgraf-opsawg-ipfix-srv6-srh-04.txt
> has been successfully submitted by Thomas Graf and posted to the IETF
> repository.
>
> Name: draft-tgraf-opsawg-ipfix-srv6-srh
> Revision: 04
> Title: Export of Segment Routing IPv6 Information in IP Flow
> Information Export (IPFIX)
> Document date: 2022-06-28
> Group: Individual Submission
> Pages: 21
> URL:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-04.txt&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xVlzsQvE%2BpREDbsZmkmVqHew15%2Bx9dblz%2FP0qngjzoA%3D&reserved=0
> Status:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-04&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FtTISdsS0UbtC5X5hXUzZDeMRK6oLbzrjbbtDfahfy0%3D&reserved=0
> Htmlized:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U4otznTjlgB052bmNi7SYYt7rAm5MtZ3XAgRv4bWyEc%3D&reserved=0
> Diff:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-tgraf-opsawg-ipfix-srv6-srh-04&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dQK2AMJKbQl4NddWlyww8Vfn9qwfl1vf03Bu9dTZncA%3D&reserved=0
>
>
> Abstract:
> This document introduces new IP Flow Information Export (IPFIX)
> information elements to identify the SRv6 Segment Routing Header
> dimensions, the SRv6 Control Plane Protocol and the SRv6 Endpoint
> Behavior that traffic is being forwarded with.
>
>
>
>
>
> The IETF Secretariat
>
_______________________________________________
spring mailing list
spr...@ietf.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fspring&data=05%7C01%7CThomas.Graf%40swisscom.com%7Cc18fbb1e9fda48b71c6408da6e1e5884%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637943373849634565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ivJyL%2Fo9U5X1TQMLSKvzr80ZNU0vEs6uQMVN8WsD3Hs%3D&reserved=0
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
