Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Adrian Farrel <adrian@olddog.co.uk> Sat, 30 January 2021 22:20 UTC

Return-Path: <adrian@olddog.co.uk>
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 833673A11E2; Sat, 30 Jan 2021 14:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOYUbJ9LQ8jG; Sat, 30 Jan 2021 14:20:19 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBD003A11DE; Sat, 30 Jan 2021 14:20:18 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 10UMKCaq007334; Sat, 30 Jan 2021 22:20:12 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B662B2203C; Sat, 30 Jan 2021 22:20:12 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id A0E652203B; Sat, 30 Jan 2021 22:20:12 +0000 (GMT)
Received: from LAPTOPK7AS653V ([84.93.31.76]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 10UMKAOg017854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Jan 2021 22:20:11 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'James Guichard'" <james.n.guichard@futurewei.com>, <spring@ietf.org>
Cc: <spring-chairs@ietf.org>
References: <MN2PR13MB42061AD1E295598F1F2726BDD2BB9@MN2PR13MB4206.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB42061AD1E295598F1F2726BDD2BB9@MN2PR13MB4206.namprd13.prod.outlook.com>
Date: Sat, 30 Jan 2021 22:20:11 -0000
Organization: Old Dog Consulting
Message-ID: <05b301d6f756$1485ced0$3d916c70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05B4_01D6F756.14864400"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGPDWyPdOZKMreitsHnlsMR1NOhUarQiHPA
Content-Language: en-gb
X-Originating-IP: 84.93.31.76
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25942.003
X-TM-AS-Result: No--27.507-10.0-31-10
X-imss-scan-details: No--27.507-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25942.003
X-TMASE-Result: 10--27.506700-10.000000
X-TMASE-MatchedRID: pS5owHKhBO3xIbpQ8BhdbI61Z+HJnvsOqb3/o5s+OcMifM7JMNHW63Q4 CU9HBITiuP4VM8YVMbACMCdGk/vT2FIeiyfGop1w9FQh3flUIh6C7C2rJeUToT0nqBp2UmIcoNo j//QtCHnNQVq7ISSt23q+qg096V49cjlZPhT8y9dT2G3xw+NXjslX1bMdPZPl+7PAkASTOu4I8a OzlvOesgZ94CKFuq+oZrA2ENe58M+JFjt3LWJs9dHurEkvKDeGi+TAnPnbttgtferJ/d7Ab0qGu emFds7ikIKSuYRlV8ZgBKW7UCfQnj+1BAh3nhn4AjoaSw0EjFUBUaQbj8IYpgi1B3nqCfsh0u5f aGP8ztTsprnGvhQwVw+wyJIhO/VV+uca9k73v6XbDD1in4vngG6QZz5cxMdzaOWLD7G8i10M6XB tKTGUp2oc4RlmNe+5ijW7tCcpBuoDrIy6s0Qwc2izU21XpNt7X93p52Kh3thtw+n+iKWyyKn9D3 t+sZBo0zwyZu9/XbZlghp/75fDQTQBHfwe/rpP+ACG5oWJ7tLfVqwz+CynaZ0oD5Lw3bToEqSmD x1CZ0qJmZ8FliAav78tQ+d++9tXeGs4plHuj5RkGI+vgRTxMBnxEnh+qZeGR6RHdVK85hXaOBWa EqUPGCOEfEoxqcEMalJg/GEaUw3ygTNqQkscDyI9MxSOQ6CSwLaQzTC7PNa418IO7BSGULo/OM8 4ZNIDrCCXG3Lpn8QAFmb/zOv8CEtZ7yRXqpTqnVTWWiNp+v+dNwtHz5PMSl+R8S49dvCo5c4evW ooWMO7sLiGJ4XBUoAy6p60ZV621ROx5lZ1Rh7+xOhjarOnHgM5kYUazKEVsOzOncrmCoOxM60Uk 4iTGiD0+biPgGqcFtf2MFK9dwkSpdmfAJsH95iatPGVTeLI
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/aY9y8SynVFGiNfTJQaRMtIVODpw>
Subject: Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 22:20:22 -0000

Thanks, Jim,

 

I've been following the enhanced VPN work in TEAS and I see it as a key
piece of the network slicing work.

 

It's time that we had some protocol solutions that serve the VPN framework,
and this is a suitable starting point. I like that it is not specifying
additional protocol widgets but has looked at what we already have and is
pointing up ways to use those tools to deliver new function.

 

I see Robert's point about the resource reservation aspects of traffic
engineering applied to an SR network, but this is not an insurmountable
problem. The question might be asked, "Why would you want to do that?" but
that is a question that (as Yakov would have said) the market can decide. It
seems that there are a couple of vendors and a couple of operators who have
an interest.

 

So I think we should adopt this draft and see whether we can turn it into
something that has great utility.

 

Cheers,

Adrian

 

From: spring <spring-bounces@ietf.org> On Behalf Of James Guichard
Sent: 27 January 2021 11:47
To: spring@ietf.org
Cc: spring-chairs@ietf.org
Subject: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

 

Dear WG:

 

This message starts a 2 week WG adoption call for
https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
ending February 10th 2021.

 

After review of the document please indicate support (or not) for WG
adoption to the mailing list and if you are willing to work on the document,
please state this explicitly. This gives the chairs an indication of the
energy level of people in the working group willing to work on this
document. Please also provide comments/reasons for your support (or lack
thereof) as this is a stronger way to indicate your (non) support as this is
not a vote.

 

Thanks!

 

Jim, Bruno & Joel