Re: [spring] WG Adoption Call fordraft-dong-spring-sr-for-enhanced-vpn Thu, 16 July 2020 09:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7FD3A3A0063; Thu, 16 Jul 2020 02:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id a7nWTghj2EpW; Thu, 16 Jul 2020 02:19:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6DEDA3A005B; Thu, 16 Jul 2020 02:19:47 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 8F4F4ACF22EF0255D447; Thu, 16 Jul 2020 17:19:45 +0800 (CST)
Received: from ([]) by with SMTP id 06G9JWQv047076; Thu, 16 Jul 2020 17:19:32 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Thu, 16 Jul 2020 17:19:32 +0800 (CST)
Date: Thu, 16 Jul 2020 17:19:32 +0800 (CST)
X-Zmail-TransId: 2afb5f101ba4b203e3e9
X-Mailer: Zmail v1.0
Message-ID: <>
Mime-Version: 1.0
From: <>
To: <>, <>
Cc: <>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 06G9JWQv047076
Archived-At: <>
Subject: Re: [spring] =?utf-8?q?WG_Adoption_Call_fordraft-dong-spring-sr-for-?= =?utf-8?q?enhanced-vpn?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Jul 2020 09:19:51 -0000

Dear WG,

I don't support WG adoption.

It is not a new idea for each Virtual Network to have its own SIDs.

e.g. The earlist description of the SID be allocated per flex-algorithm and related metric

 information was in draft-hegdeppsenak-isis-sr-flex-algo-00(2017.7.17) (now is draft-ietf-isis-sr-flex-algo) . 

The earlist description of the SID be allocated per MT was in draft-filsfils-spring-segment-routing-04(2014.7.3)

(now is RFC8402 ), and draft-peng-lsr-network-slicing-00(2019.2.25) describe the

SID be allocated per AII(alias alice).  For slice resources,  

induced slice-id(AII) for slice resources management, and can differentiate them (e.g. L2 link or L3 interface,

section 7 ), and how to compute SR-BE or SR-TE path according to AII combined with other criteria.



-----Original Message-----From: spring <> On Behalf Of James GuichardSent: Wednesday, July 15, 2020 8:17 PMTo: spring@ietf.orgCc: spring-chairs@ietf.orgSubject: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpnDear WG:  This email begins a 2 week WG adoption call for <>  ending Wednesday 29th July 2020.    Please speak up if you support or oppose adopting this document into the WG. Please also provide comments/reasons for that support (or lack thereof). Silence will not be considered consent.  Thanks!  Jim, Joel & Bruno      _______________________________________________spring mailing