From nobody Tue Jun 13 05:33:52 2023 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADCE3C14CE4D for ; Tue, 13 Jun 2023 05:33:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ruijie-com-cn.20200927.dkim.feishu.cn 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 yC0sEwZw3Uok for ; Tue, 13 Jun 2023 05:33:47 -0700 (PDT) Received: from s01.bc.larksuite.com (s01.bc.larksuite.com [209.127.230.17]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 6DACEC14CE2E for ; Tue, 13 Jun 2023 05:33:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=s1; d=ruijie-com-cn.20200927.dkim.feishu.cn; t=1686659617; h=from:subject:mime-version:from:date:message-id:subject:to:cc: reply-to:content-type:mime-version:in-reply-to:message-id; bh=25zjqEDz94vA0ujHNz9hsYqP1ZMq7N+IxCJizR8zFec=; b=SLPjB0gxxIJ8y7Xa6lyAEJeeeYXx4HXkfxcYRmTsUqaycZKJmmACqCvDsxaXAbDXyzYGNc pZc2l2OVtqYoYTlU2fI4PYO7KCo/kDTnWEaokcQaNi1KXscYUbJU9MjinQWd8qOllI0LkG Vcjq7/2ueYq4nrxZ05tVi1KVMi54pe5npqesydaDOylhTMDltNRgK6hABe63f5zxp2iaVE uXLQcBkOnjo4deZ5as0hOABOjyW4Wsdb/MRrHQfL20TODSLiriEDSG2wHhhsSCKdmrMci2 33WFO14W+yfku2CwIdV3bFi7YexAOMWgjuOG7OcBzNlu59gVPZY6XhjSfpq+jg== Date: Tue, 13 Jun 2023 20:33:36 +0800 From: "Xuewei Wang" X-Lms-Return-Path: Content-Type: multipart/alternative; boundary=47f768f72ae0cdc92c18bbc2b23b94d83c5c7a0449724b53ad20cb552bba In-Reply-To: <07fa01d98d64$33adbb50$9b0931f0$@com> Message-Id: <29e540a2652de0cf2773fffcb38edf59fc548f6e.cb5c85e2.7245.4032.b570.2849c54a2d73@feishu.cn> To: "Weiqiang Cheng" Cc: "'spring'" , , "'Changwang Lin'" , "'Ruibo Han'" , "'Yuanxiang Qiu'" Mime-Version: 1.0 Archived-At: Subject: Re: [spring] FW: New Version Notification for draft-cheng-spring-distribute-srv6-locator-by-dhcp-00.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2023 12:33:51 -0000 --47f768f72ae0cdc92c18bbc2b23b94d83c5c7a0449724b53ad20cb552bba Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Hi=EF=BC=8CWG=EF=BC=8C I think this is a very valuable solution for the SRv6 location for the CPE = scenario. As a vendor, we have tested this solution in our lab, which is ea= sy to implement. > From: "Weiqiang Cheng" > Date: Tue, May 23, 2023, 18:49 > Subject: [spring] FW: New Version Notification for draft-cheng-spring-di= stribute-srv6-locator-by-dhcp-00.txt > To: "'spring'" > Cc: , "'Changwang Lin'", "'Ruibo Han'", "'Yuanxiang Qiu'" > Hi, All >=20 > According to the discussion results of the DHC WG and SPRING WG chairs af= ter IETF-116, [draft-cheng-dhc-distribute-srv6-locator-by-dhcp] will be pro= gressed in SPRING WG. > Now we have uploaded the replacement draft [draft-cheng-spring-distribute= -srv6-locator-by-dhcp]. > Document Link: https://datatracker.ietf.org/doc/draft-cheng-spring-distr= ibute-srv6-locator-by-dhcp/ >=20 > This proposal follows the IPv6 Prefix allocation process of DHCPv6 and pr= oposes a method of dynamically assigning SRv6 Locator to endpoints through = DHCPv6. > It defines an Identity Association for SRv6 Locator (IA_SRV6_LOCATOR) Opt= ion.=20 > With this option, Locator Prefix and Block-len, Func-len, Args-len can be= dynamically distributed for SRv6 endpoints in SRv6 network. > Based on this method, centralized management of SRv6 Locator prefix resou= rces can be achieved, and network deployment can also be effectively simpli= fied. >=20 > The draft has been presented in DHC WG at IETF115 and 116, as well in SPR= ING WG at IETF116. The feedback were positive. >=20 > Sincerely ask for your feedback. >=20 > Best Regards=EF=BC=8C >=20 > Weiqiang Cheng >=20 > -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6----- > =E5=8F=91=E4=BB=B6=E4=BA=BA: internet-drafts@ietf.org [mailto:internet-dr= afts@ietf.org]=20 > =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2023=E5=B9=B45=E6=9C=8818=E6=97=A5 = 17:48 > =E6=94=B6=E4=BB=B6=E4=BA=BA: Changwang Lin; Ruibo Han; Weiqiang Cheng; Yu= anxiang Qiu > =E4=B8=BB=E9=A2=98: New Version Notification for draft-cheng-spring-distr= ibute-srv6-locator-by-dhcp-00.txt >=20 >=20 > A new version of I-D, draft-cheng-spring-distribute-srv6-locator-by-dhcp-= 00.txt > has been successfully submitted by Weiqiang Cheng and posted to the > IETF repository. >=20 > Name: draft-cheng-spring-distribute-srv6-locator-by-dhcp > Revision: 00 > Title: Distribute SRv6 Locator by DHCP > Document date: 2023-05-18 > Group: Individual Submission > Pages: 15 > URL: https://www.ietf.org/archive/id/draft-cheng-spring-distri= bute-srv6-locator-by-dhcp-00.txt > Status: https://datatracker.ietf.org/doc/draft-cheng-spring-distr= ibute-srv6-locator-by-dhcp/ > Htmlized: https://datatracker.ietf.org/doc/html/draft-cheng-spring-= distribute-srv6-locator-by-dhcp >=20 >=20 > Abstract: > In SRv6 network, locators need to be assigned to each SRv6 Endpoint, > and segments are created based on locators. This document describes > the method of assigning locators to SRv6 Endpoints through DHCPv6. >=20 > = =20 >=20 >=20 > The IETF Secretariat >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring --47f768f72ae0cdc92c18bbc2b23b94d83c5c7a0449724b53ad20cb552bba Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8
Hi=EF=BC=8CWG=EF=BC=8C
I think this is a very va= luable solution for the SRv6 location for the CPE scenario. As a vendor, we= have tested this solution in our lab, which is easy to implement.
<= div style=3D"word-break: break-word;">
From: "Weiqi= ang Cheng"<chengweiqiang@chinamobile.com>
<= span style=3D"white-space:nowrap;">Date: Tue, May 23, 2023, 18:49
Subject: [s= pring] FW: New Version Notification for draft-cheng-spring-distribute-srv6-= locator-by-dhcp-00.txt
To: "'spring'&= #34;<spring@ietf.org>=
Cc: <spring-chairs@ietf.org>, "'Changwang Lin'"<linchangwang.04414@h3c.com>,= "'Ruibo Han'"<hanruibo@chinamobile.com= >, "'Yuanxiang Q= iu'"<qiuyuanxiang= @h3c.com>
Hi, All According to the discussion results of the DHC WG and SPRING WG chairs afte= r IETF-116, [draft-cheng-dhc-distribute-srv6-locator-by-dhcp] will be progr= essed in SPRING WG. Now we have uploaded the replacement draft [draft-cheng-spring-distribute-s= rv6-locator-by-dhcp]. Document Link: https://datatracker.ietf.org/doc/draft-cheng-spring-distribute-srv= 6-locator-by-dhcp/ This proposal follows the IPv6 Prefix allocation process of DHCPv6 and prop= oses a method of dynamically assigning SRv6 Locator to endpoints through DH= CPv6. It defines an Identity Association for SRv6 Locator (IA_SRV6_LOCATOR) Optio= n.=20 With this option, Locator Prefix and Block-len, Func-len, Args-len can be d= ynamically distributed for SRv6 endpoints in SRv6 network. Based on this method, centralized management of SRv6 Locator prefix resourc= es can be achieved, and network deployment can also be effectively simplifi= ed. The draft has been presented in DHC WG at IETF115 and 116, as well in SPRIN= G WG at IETF116. The feedback were positive. Sincerely ask for your feedback. Best Regards=EF=BC=8C Weiqiang Cheng -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6----- =E5=8F=91=E4=BB=B6=E4=BA=BA: internet-drafts@ietf.org [<= a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank" ref=3D"noopene= r noreferrer">mailto:internet-drafts@ietf.org]=20 =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2023=E5=B9=B45=E6=9C=8818=E6=97=A5 17= :48 =E6=94=B6=E4=BB=B6=E4=BA=BA: Changwang Lin; Ruibo Han; Weiqiang Cheng; Yuan= xiang Qiu =E4=B8=BB=E9=A2=98: New Version Notification for draft-cheng-spring-distrib= ute-srv6-locator-by-dhcp-00.txt A new version of I-D, draft-cheng-spring-distribute-srv6-locator-by-dhcp-00= .txt has been successfully submitted by Weiqiang Cheng and posted to the IETF repository. Name: draft-cheng-spring-distribute-srv6-locator-by-dhcp Revision: 00 Title: Distribute SRv6 Locator by DHCP Document date: 2023-05-18 Group: Individual Submission Pages: 15 URL: https://www.ietf.org/archive/id/draft-cheng-spring-distribute= -srv6-locator-by-dhcp-00.txt Status: https://datatracker.ietf.org/doc/draft-cheng-spring-distribute-srv= 6-locator-by-dhcp/ Htmlized: https://datatracker.ietf.org/doc/html/draft-cheng-spring-distr= ibute-srv6-locator-by-dhcp Abstract: In SRv6 network, locators need to be assigned to each SRv6 Endpoint, and segments are created based on locators. This document describes the method of assigning locators to SRv6 Endpoints through DHCPv6. = =20 The IETF Secretariat _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
--47f768f72ae0cdc92c18bbc2b23b94d83c5c7a0449724b53ad20cb552bba--