Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh
mohamed.boucadair@orange.com Tue, 20 September 2022 09:13 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D20E5C15258C for <opsawg@ietfa.amsl.com>; Tue, 20 Sep 2022 02:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IsFoDUYKD1O for <opsawg@ietfa.amsl.com>; Tue, 20 Sep 2022 02:12:56 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEA6DC1522CA for <opsawg@ietf.org>; Tue, 20 Sep 2022 02:12:55 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar26.francetelecom.fr (ESMTP service) with ESMTPS id 4MWwn21DbczFqrG; Tue, 20 Sep 2022 11:12:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1663665174; bh=2R+m/aLi50dY/Sgrx/N4YwLGbK6uvvWY4FyqWNOp2G8=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=CeAKXQFt1mnxmj3ts8ctovDem2SmaR8+vjHeJeww7VCm1/l8H3zaZ5hD8yIItxD+T 7VNm4AKMLSacZX8O9ytv++5y3OOrIRXhvFwC4+4aXK3M0Ltur5QOShoHgByrJFAjkV QBR92wi/8EwyYXdaR+vpn/Jt1+NzanlGa+JMnLqyKQRGLs5TwdISSg40RLqASG+x5W KHFQjjdfHD8FtIDkPuLEWH5BuIDnnU7SNZnSJ3r5WlzNduJAIl27X4A5MyRbE1zf/7 8+mrtXzTu0+QlHHIV6fDSBpuls2X0c017FzX5dZSl7kDPUgGUX2HvnJz7JxnQ/MMLL A2RAR1j/x4WWw==
From: mohamed.boucadair@orange.com
To: "Thomas.Graf@swisscom.com" <Thomas.Graf@swisscom.com>, "benoit.claise@huawei.com" <benoit.claise@huawei.com>, "jclarke=40cisco.com@dmarc.ietf.org" <jclarke=40cisco.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
CC: "pierre.francois@insa-lyon.fr" <pierre.francois@insa-lyon.fr>
Thread-Topic: CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh
Thread-Index: AQHYsz7GkNenOfX58E6FatPIULX/CK3SJj0ggA7LiHCAAN6FcIACIE0AgALtrICAACWe0IABMTIw
Content-Class:
Date: Tue, 20 Sep 2022 09:12:53 +0000
Message-ID: <9620163534144e7193de5aa95a7377cf@orange.com>
References: <BN9PR11MB5371EF97C81F4D53CFD5FC77B86D9@BN9PR11MB5371.namprd11.prod.outlook.com> <30955_1662452342_63170276_30955_240_1_24f1bf268bbf4ea08f058aa6ee5d31a6@orange.com> <ZRAP278MB0176383B6F6427DA40FC924889499@ZRAP278MB0176.CHEP278.PROD.OUTLOOK.COM> <51222224a12d463fba8c84fe9cdc2044@orange.com> <8aa51620-98df-003b-3e7a-bec5bb8c9602@huawei.com> <18795_1663590103_63285ED7_18795_259_1_0bebdd34f5e94100ae01191f38a6bad1@orange.com> <ZRAP278MB017638782DB932F3D9D04EF0894D9@ZRAP278MB0176.CHEP278.PROD.OUTLOOK.COM>
In-Reply-To: <ZRAP278MB017638782DB932F3D9D04EF0894D9@ZRAP278MB0176.CHEP278.PROD.OUTLOOK.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-09-20T09:02:06Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=060c19a4-e035-4c3f-bf70-ae61d6e9511a; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.53]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0005_01D8CCE1.EBE1A090"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/X3PbGM8LYYTUStSjOZzmPyLCExc>
Subject: Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2022 09:13:00 -0000
Hi Thomas, This is a useful addition. Thanks. A more general question is to check whether one can report the identity of the EHs that form the Header Chain, but this is not specific to this draft. The current ipv6ExtensionHeaders does not allow for that. Cheers, Med De : Thomas.Graf@swisscom.com <Thomas.Graf@swisscom.com> Envoyé : lundi 19 septembre 2022 16:47 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; benoit.claise@huawei.com; jclarke=40cisco.com@dmarc.ietf.org; opsawg@ietf.org Cc : pierre.francois@insa-lyon.fr Objet : RE: CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi Med, Benoit will feedback on your reply. In the meanwhile I like to take the opportunity to get your feedback on an additional operational consideration section I added based on an off list feedback I received from a software developer implementing the draft document. https://raw.githubusercontent.com/graf3net/draft-tgraf-opsawg-ipfix-sr v6-srh/main/draft-ietf-opsawg-ipfix-srv6-srh-01.txt 5.3. Multiple Segment Routing Headers [RFC8200] describes the support of multiple extension headers in one IPv6 packet. Allowing the use of multiple SRH per SRv6 packet. The export of the same IE multiple times in one data-record and data- template is supported and the order within the packet SHOULD be preserved in the IPFIX export according to Section 8 of [RFC7011]. If the network node is not capable to export IPFIX for more than one SRH, it MUST export IPFIX for the active SRH. Best wishes Thomas From: mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com> > Sent: Monday, September 19, 2022 2:22 PM To: Benoit Claise <benoit.claise@huawei.com <mailto:benoit.claise@huawei.com> >; Graf Thomas, INI-NET-TCZ-ZH1 <Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com> >; jclarke=40cisco.com@dmarc.ietf.org <mailto:jclarke=40cisco.com@dmarc.ietf.org> ; opsawg@ietf.org <mailto:opsawg@ietf.org> Cc: pierre.francois@insa-lyon.fr <mailto:pierre.francois@insa-lyon.fr> Subject: RE: CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi Benoît, Thank you for the follow-up. Actually, the more I look into this, the more Im convinced that we dont need a new registry for the flags and that the statement Values for this Information Element are listed in the "IPFIX IPv6 SRH Flags" registry is restrictive (inaccurate(?)). The flags should be exported as ** observed ** not as set in the registry. Think about discarded packets because some flags are set (including those already for which a meaning is already defined such as the O flag) while the processing of these flags is not supported by a router. In such cases, one use of the srhFlagsIPv6 IE would be to display the erroneous set of flags together with some error counters. The values of the IE is not taken from the IANA registry. That said, I fully agree that the spec has to indicate Data Type Semantics: flags for that IE. The same would apply for the srhSegmentEndpointBehavior IE. Please let me know if Im missing something. Thanks. Cheers, Med De : Benoit Claise <benoit.claise@huawei.com <mailto:benoit.claise@huawei.com> > Envoyé : samedi 17 septembre 2022 17:39 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com> >; Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com> ; jclarke=40cisco.com@dmarc.ietf.org <mailto:jclarke=40cisco.com@dmarc.ietf.org> ; opsawg@ietf.org <mailto:opsawg@ietf.org> Cc : pierre.francois@insa-lyon.fr <mailto:pierre.francois@insa-lyon.fr> ; me <benoit.claise@huawei.com <mailto:benoit.claise@huawei.com> > Objet : Re: CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi Med, Thanks for your comments. I visited IANA in Philly to validate this propose, but we could re-evaluate & discuss about it. We need a registry because just telling that we take the value from https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml #segment-routing-header-flags <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww .iana.org%2Fassignments%2Fipv6-parameters%2Fipv6-parameters.xhtml%23se gment-routing-header-flags&data=05%7C01%7CThomas.Graf%40swisscom.com%7 C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9beec35d19b557a1%7 C0%7C0%7C637991869075461857%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata =RPddE%2B%2Fs5hf57k6SLdcLXoaHRcNvWrmZHj7BRUOmdAc%3D&reserved=0> is not sufficient as we also need to specify the following IPFIX fields: - Abstract Data Type. (unsigned8 in this srhFlagsIPv6 case) - Data Type Semantics (flags in srhFlagsIPv6 case) Now, if your point is that we don't really to mention the initial values ... Initial values in the registry are defined by the table below. +--------+-------------------+--------------------------------------+ | Value | Description | Reference | +--------+-------------------+--------------------------------------+ | 0-1 | Unassigned | | +--------+-------------------+--------------------------------------+ | 2 | O-flag | [RFC-ietf-6man-spring-srv6-oam-13] | +--------+-------------------+--------------------------------------+ | 3-7 | Unassigned | | +--------+-------------------+--------------------------------------+ Table 2: "IPFIX IPv6 SRH Flags" registry ... I agree it's not strictly necessary but it helps (me/the IPFIX experts) to understand, from this document, which type of values are currently available. See inline. On 9/16/2022 9:34 AM, mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com> wrote: Hi Thomas, Thank you for preparing this revised version. I think almost all my comments are addressed in this version. However, I still dont see the need to have new registries that only mirror existing ones. For example, and unless I missed some subtleties, it would be sufficient to say that the flag values are taken from <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww .iana.org%2Fassignments%2Fipv6-parameters%2Fipv6-parameters.xhtml%23se gment-routing-header-flags&data=05%7C01%7CThomas.Graf%40swisscom.com%7 C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9beec35d19b557a1%7 C0%7C0%7C637991869075461857%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata =RPddE%2B%2Fs5hf57k6SLdcLXoaHRcNvWrmZHj7BRUOmdAc%3D&reserved=0> https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml #segment-routing-header-flags rather than adding the following in the I-D: +--------+-------------------+--------------------------------------+ | Value | Description | Reference | +--------+-------------------+--------------------------------------+ | 0-1 | Unassigned | | +--------+-------------------+--------------------------------------+ | 2 | O-flag | [RFC-ietf-6man-spring-srv6-oam-13] | +--------+-------------------+--------------------------------------+ | 3-7 | Unassigned | | +--------+-------------------+--------------------------------------+ Table 2: "IPFIX IPv6 SRH Flags" registry which is similar in term of encoding and values as what was set by RFC9256: IANA has registered the following in the "Segment Routing Header Flags" subregistry in the "Internet Protocol Version 6 (IPv6) Parameters" registry: +=====+=============+===========+ | Bit | Description | Reference | +=====+=============+===========+ | 2 | O-flag | RFC 9259 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdat atracker.ietf.org%2Fdoc%2Fhtml%2Frfc9259&data=05%7C01%7CThomas.Graf%40 swisscom.com%7C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9bee c35d19b557a1%7C0%7C0%7C637991869075461857%7CUnknown%7CTWFpbGZsb3d8eyJW IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000% 7C%7C%7C&sdata=hwt7%2B8ZNGywoq1JE5w3K69aJzKWAB%2FS5hGBaY1zGc1A%3D&rese rved=0> | +-----+-------------+-----------+ BTW, I guess you initially meant: NEW: Table 2: "IPFIX IPv6 SRH Flags" registry Note to IANA: Add a note to the "Segment Routing Header Flags" registry so that new values are echoed in the new "IPFIX IPv6 SRH Flags You are right (since https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml #segment-routing-header-flags <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww .iana.org%2Fassignments%2Fipv6-parameters%2Fipv6-parameters.xhtml%23se gment-routing-header-flags&data=05%7C01%7CThomas.Graf%40swisscom.com%7 C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9beec35d19b557a1%7 C0%7C0%7C637991869075618077%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata =s9tARTFkRk8glE4DupqLcAhhy%2BMmzYg7r3J6SDgnJDY%3D&reserved=0> is "IETF review" while https://www.iana.org/assignments/ipfix/ipfix.xhtml <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww .iana.org%2Fassignments%2Fipfix%2Fipfix.xhtml&data=05%7C01%7CThomas.Gr af%40swisscom.com%7C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420 d9beec35d19b557a1%7C0%7C0%7C637991869075618077%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C 3000%7C%7C%7C&sdata=EOo9JHuX%2FtnEdhZLMDYLcNEm1kPP3UZSJaosxvW%2F5aY%3D &reserved=0> is "Expert Review") instead of CURRENT: Table 2: "IPFIX IPv6 SRH Flags" registry Note to IANA: Add a note to the registry so that new values are echoed in the new "IPFIX SRv6 EndPoint Behavior The same comment applies for the values that can be directly taken from https://www.iana.org/assignments/segment-routing/segment-routing.xhtml #srv6-endpoint-behaviors <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww .iana.org%2Fassignments%2Fsegment-routing%2Fsegment-routing.xhtml%23sr v6-endpoint-behaviors&data=05%7C01%7CThomas.Graf%40swisscom.com%7C6319 709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C 0%7C637991869075618077%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nUMh LgiV68H%2BxHg088641Nqz5l4%2F982T7PIqvQozPxo%3D&reserved=0> . Yes OLD: Table 4: "IPFIX SRV6 Endpoint Behavior" registry Note to IANA: Add a note to the registry so that new values are echoed in the new "IPFIX SRv6 EndPoint Behavior NEW: Table 4: "IPFIX SRV6 Endpoint Behavior" registry Note to IANA: Add a note to the "IPFIX SRV6 Endpoint Behavior" registry so that new values are echoed in the new "IPFIX SRv6 EndPoint Behavior Regards, Benoit Cheers, Med De : Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com> <mailto:Thomas.Graf@swisscom.com> <Thomas.Graf@swisscom.com> Envoyé : jeudi 15 septembre 2022 20:08 À : BOUCADAIR Mohamed INNOV/NET <mailto:mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com>; jclarke=40cisco.com@dmarc.ietf.org <mailto:jclarke=40cisco.com@dmarc.ietf.org> ; opsawg@ietf.org <mailto:opsawg@ietf.org> Cc : benoit.claise@huawei.com <mailto:benoit.claise@huawei.com> ; pierre.francois@insa-lyon.fr <mailto:pierre.francois@insa-lyon.fr> Objet : RE: CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Dear Med, Many thanks for the comprehensive review. Much appreciated. We merged all your input to the upcoming -01 release. https://raw.githubusercontent.com/graf3net/draft-tgraf-opsawg-ipfix-sr v6-srh/main/draft-ietf-opsawg-ipfix-srv6-srh-01.txt <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw .githubusercontent.com%2Fgraf3net%2Fdraft-tgraf-opsawg-ipfix-srv6-srh% 2Fmain%2Fdraft-ietf-opsawg-ipfix-srv6-srh-01.txt&data=05%7C01%7CThomas .Graf%40swisscom.com%7C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7 420d9beec35d19b557a1%7C0%7C0%7C637991869075618077%7CUnknown%7CTWFpbGZs b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D %7C3000%7C%7C%7C&sdata=vVgucAUtUeEWlOVvGVT0KcTD38ZEzWWjbT8Oky7ZewQ%3D& reserved=0> The diff to the current -00 version can be found here: https://www.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draf t-ietf-opsawg-ipfix-srv6-srh-00.txt&url2=https://raw.githubusercontent .com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/main/draft-ietf-opsawg -ipfix-srv6-srh-01.txt For some we need further clarifications if we addressed them correctly. I would appreciate if you could clarify the following three points: Med> Section 2, remark: "Why do we need three IE, srhSegmentIPv6ListSection, srhSegmentIPv6BasicList and srhSectionIPv6, to expose SRH Segment List Thomas> Section 5.1 should provide the answer. If that should not be sufficient, please suggest how this could be better expressed. Med> Section 2: remark: "as series of n octets" is not clearly comprehensible. Thomas> Extended to "as series of n octets in IPFIX". Does that makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas From: OPSAWG <opsawg-bounces@ietf.org <mailto:opsawg-bounces@ietf.org> > On Behalf Of mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com> Sent: Tuesday, September 6, 2022 10:19 AM To: Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org <mailto:jclarke=40cisco.com@dmarc.ietf.org> >; opsawg@ietf.org <mailto:opsawg@ietf.org> Subject: Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi all, I support. FWIW, the authors may found some quick comments at: 1. pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-tgra f-opsawg-ipfix-srv6-srh-05-rev%20Med.pdf <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit hub.com%2Fboucadair%2FIETF-Drafts-Reviews%2Fraw%2Fmaster%2Fdraft-tgraf -opsawg-ipfix-srv6-srh-05-rev%2520Med.pdf&data=05%7C01%7CThomas.Graf%4 0swisscom.com%7C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9be ec35d19b557a1%7C0%7C0%7C637991869075618077%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000 %7C%7C%7C&sdata=T80wbeWCWmQvaeFdojbZ6gneZOhBK6Xb%2F1S%2FjhNb81c%3D&res erved=0> 2. doc: <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit hub.com%2Fboucadair%2FIETF-Drafts-Reviews%2Fraw%2Fmaster%2Fdraft-tgraf -opsawg-ipfix-srv6-srh-05-rev%2520Med.doc&data=05%7C01%7CThomas.Graf%4 0swisscom.com%7C6319709d35cb4bc603e408da9a39853d%7C364e5b87c1c7420d9be ec35d19b557a1%7C0%7C0%7C637991869075618077%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000 %7C%7C%7C&sdata=ia3D%2BZMNzo4Lv44lKO12Ba%2BfRniDXAnnwYprHveHN5k%3D&res erved=0> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-tgra f-opsawg-ipfix-srv6-srh-05-rev%20Med.doc Cheers, Med De : OPSAWG <opsawg-bounces@ietf.org <mailto:opsawg-bounces@ietf.org> > De la part de Joe Clarke (jclarke) Envoyé : jeudi 18 août 2022 22:14 À : opsawg@ietf.org <mailto:opsawg@ietf.org> Objet : [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. Wed like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IETF 114 there does seem to be interest in adopting this in opsawg, but we need a formal adoption poll. Please review and provide your adoption thoughts no later than September 1, 2022. 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. ______________________________________________________________________ ___________________________________________________ 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.
- [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ip… Joe Clarke (jclarke)
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Zafar Ali (zali)
- Re: [OPSAWG] FW: CALL FOR ADOPTION: draft-tgraf-o… Chongfeng Xie
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Paolo Lucente
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Haoyu Song
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Alex Huang Feng
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Paolo Volpato
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Qin Wu
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Benoit Claise
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Ahmed Abdelsalam (ahabdels)
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Diego R. Lopez
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Giuseppe Fioccola
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Benoit Claise
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Joe Clarke (jclarke)
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Thomas.Graf
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Benoit Claise
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Thomas.Graf
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Benoit Claise
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Thomas.Graf
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… mohamed.boucadair
- Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsaw… Benoit Claise