Re: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation
Sure, this would be fine. And I’ve seen the back and forth with IANA. Joe From: thomas.g...@swisscom.com Date: Saturday, October 8, 2022 at 2:28 AM To: Joe Clarke (jclarke) , opsawg-cha...@ietf.org Cc: opsawg@ietf.org , pierre.franc...@insa-lyon.fr , benoit.cla...@huawei.com Subject: RE: draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Dear Joe, My apology for late reply. That works for us. We are in touch with IANA and the IPFIX doctors to clarify the points raised by Med in regards to the srhFlagsIPv6 and the srhSegmentEndpointBehavior registry. Once this has been clarified we will publish -02 version. We would like to request a 15min slot for IETF 115 to present an update on the latest document updates and some feedback on two running code implementations from the hackathon where we use IPFIX entities from the PEN space. Could we raise the question to the WG in this slot wherever we have consensus that early allocation is warranted or not? Best wishes Thomas From: Joe Clarke (jclarke) Sent: Friday, September 23, 2022 7:49 PM To: Graf Thomas, INI-NET-TCZ-ZH1 ; opsawg-cha...@ietf.org Cc: opsawg@ietf.org; pierre.franc...@insa-lyon.fr Subject: Re: draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Hey, Thomas. I’m a wee bit nervous declaring stability since IETF 115 hasn’t happened yet, but I do think you’re on track, and I can request of the WG their thoughts as to whether there is consensus that early allocation is warranted. So, I think a, b, and d from Section 2 are met (speaking for ADs on d). I just want to make sure we’re not bit by anything at the ‘thon at 115. In terms of process, once we are satisfied that c is met, it is on us (chairs) to request approval from the ADs. You do not need to contact IANA. If this is approved, we will make that request. Joe From: OPSAWG mailto:opsawg-boun...@ietf.org>> on behalf of thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com> mailto:thomas.g...@swisscom.com>> Date: Friday, September 23, 2022 at 8:27 AM To: opsawg-cha...@ietf.org<mailto:opsawg-cha...@ietf.org> mailto:opsawg-cha...@ietf.org>> Cc: opsawg@ietf.org<mailto:opsawg@ietf.org> mailto:opsawg@ietf.org>>, pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> mailto:pierre.franc...@insa-lyon.fr>> Subject: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Dear OPSAWG chairs, We believe that the draft is reaching stable state. At IETF 115 hackathon in November we will have one open-source and one closed-source implementation of draft-ietf-opsawg-ipfix-srv6-srh-01. Therefore we believe we are satisfying the conditions for early allocation of code points as described https://www.rfc-editor.org/rfc/rfc7120#section-2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7120%23section-2=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=VMcciwuXkPGjvdoRl1ATOZ9euXNGpVYu4%2BjRs29lVfY%3D=0>. With your permission we would like to go ahead an get in contact with IANA and clarify Med's comments on the srhFlagsIPv6 https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.1<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05%23section-4.1=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lI%2FReXBvtm%2BUG8lvX4EaxzWjP4kyJIlJ2KNcYbO3zf8%3D=0> and srhSegmentEndpointBehavior https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.11<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05%23section-4.11=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=5t1P8t5m2CCXeq0T73f393uxz1COqndnumNubNI1uvg%3D=0> registry commented at https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/pull/15/commits/470424596d9eeaa368a497a1a53f19573b764df9<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgraf3net%2Fdraft-tgraf-opsawg-ipfix-srv6-srh%2Fpull%2F15%2Fcommits%2F470424596d9eeaa368a497a1a53f19573b764df9=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec3
Re: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation
Dear Joe, My apology for late reply. That works for us. We are in touch with IANA and the IPFIX doctors to clarify the points raised by Med in regards to the srhFlagsIPv6 and the srhSegmentEndpointBehavior registry. Once this has been clarified we will publish -02 version. We would like to request a 15min slot for IETF 115 to present an update on the latest document updates and some feedback on two running code implementations from the hackathon where we use IPFIX entities from the PEN space. Could we raise the question to the WG in this slot wherever we have consensus that early allocation is warranted or not? Best wishes Thomas From: Joe Clarke (jclarke) Sent: Friday, September 23, 2022 7:49 PM To: Graf Thomas, INI-NET-TCZ-ZH1 ; opsawg-cha...@ietf.org Cc: opsawg@ietf.org; pierre.franc...@insa-lyon.fr Subject: Re: draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Hey, Thomas. I'm a wee bit nervous declaring stability since IETF 115 hasn't happened yet, but I do think you're on track, and I can request of the WG their thoughts as to whether there is consensus that early allocation is warranted. So, I think a, b, and d from Section 2 are met (speaking for ADs on d). I just want to make sure we're not bit by anything at the 'thon at 115. In terms of process, once we are satisfied that c is met, it is on us (chairs) to request approval from the ADs. You do not need to contact IANA. If this is approved, we will make that request. Joe From: OPSAWG mailto:opsawg-boun...@ietf.org>> on behalf of thomas.g...@swisscom.com<mailto:thomas.g...@swisscom.com> mailto:thomas.g...@swisscom.com>> Date: Friday, September 23, 2022 at 8:27 AM To: opsawg-cha...@ietf.org<mailto:opsawg-cha...@ietf.org> mailto:opsawg-cha...@ietf.org>> Cc: opsawg@ietf.org<mailto:opsawg@ietf.org> mailto:opsawg@ietf.org>>, pierre.franc...@insa-lyon.fr<mailto:pierre.franc...@insa-lyon.fr> mailto:pierre.franc...@insa-lyon.fr>> Subject: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Dear OPSAWG chairs, We believe that the draft is reaching stable state. At IETF 115 hackathon in November we will have one open-source and one closed-source implementation of draft-ietf-opsawg-ipfix-srv6-srh-01. Therefore we believe we are satisfying the conditions for early allocation of code points as described https://www.rfc-editor.org/rfc/rfc7120#section-2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7120%23section-2=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=VMcciwuXkPGjvdoRl1ATOZ9euXNGpVYu4%2BjRs29lVfY%3D=0>. With your permission we would like to go ahead an get in contact with IANA and clarify Med's comments on the srhFlagsIPv6 https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.1<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05%23section-4.1=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lI%2FReXBvtm%2BUG8lvX4EaxzWjP4kyJIlJ2KNcYbO3zf8%3D=0> and srhSegmentEndpointBehavior https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.11<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05%23section-4.11=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=5t1P8t5m2CCXeq0T73f393uxz1COqndnumNubNI1uvg%3D=0> registry commented at https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/pull/15/commits/470424596d9eeaa368a497a1a53f19573b764df9<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgraf3net%2Fdraft-tgraf-opsawg-ipfix-srv6-srh%2Fpull%2F15%2Fcommits%2F470424596d9eeaa368a497a1a53f19573b764df9=05%7C01%7CThomas.Graf%40swisscom.com%7Cc04f98e70a394d3dfaf408da9d8bec35%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637995521546125933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=C4a9Dct8AAlifLBvbAGuvScQ35NKdGnPRDZYahNxZqs%3D=0> first and then go ahead with the IPFIX entity early allocation. Best wishes Thomas smime.p7s Description: S/MIME Cryptographic Signature ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation
Hey, Thomas. I’m a wee bit nervous declaring stability since IETF 115 hasn’t happened yet, but I do think you’re on track, and I can request of the WG their thoughts as to whether there is consensus that early allocation is warranted. So, I think a, b, and d from Section 2 are met (speaking for ADs on d). I just want to make sure we’re not bit by anything at the ‘thon at 115. In terms of process, once we are satisfied that c is met, it is on us (chairs) to request approval from the ADs. You do not need to contact IANA. If this is approved, we will make that request. Joe From: OPSAWG on behalf of thomas.g...@swisscom.com Date: Friday, September 23, 2022 at 8:27 AM To: opsawg-cha...@ietf.org Cc: opsawg@ietf.org , pierre.franc...@insa-lyon.fr Subject: [OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation Dear OPSAWG chairs, We believe that the draft is reaching stable state. At IETF 115 hackathon in November we will have one open-source and one closed-source implementation of draft-ietf-opsawg-ipfix-srv6-srh-01. Therefore we believe we are satisfying the conditions for early allocation of code points as described https://www.rfc-editor.org/rfc/rfc7120#section-2. With your permission we would like to go ahead an get in contact with IANA and clarify Med's comments on the srhFlagsIPv6 https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.1 and srhSegmentEndpointBehavior https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.11 registry commented at https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/pull/15/commits/470424596d9eeaa368a497a1a53f19573b764df9 first and then go ahead with the IPFIX entity early allocation. Best wishes Thomas ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
[OPSAWG] draft-ietf-opsawg-ipfix-srv6-srh-01 - RFC 7120 IANA early code point allocation
Dear OPSAWG chairs, We believe that the draft is reaching stable state. At IETF 115 hackathon in November we will have one open-source and one closed-source implementation of draft-ietf-opsawg-ipfix-srv6-srh-01. Therefore we believe we are satisfying the conditions for early allocation of code points as described https://www.rfc-editor.org/rfc/rfc7120#section-2. With your permission we would like to go ahead an get in contact with IANA and clarify Med's comments on the srhFlagsIPv6 https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.1 and srhSegmentEndpointBehavior https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh-05#section-4.11 registry commented at https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/pull/15/commits/470424596d9eeaa368a497a1a53f19573b764df9 first and then go ahead with the IPFIX entity early allocation. Best wishes Thomas smime.p7s Description: S/MIME Cryptographic Signature ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
