Re: [spring] Update and request to adopt draft-dong-spring-sr-for-enhanced-vpn

"li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com> Fri, 20 December 2019 03:55 UTC

Return-Path: <li_zhenqiang@hotmail.com>
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 8EFFF12006F; Thu, 19 Dec 2019 19:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.124
X-Spam-Level:
X-Spam-Status: No, score=-1.124 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
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 Bp2WVE0g_7H8; Thu, 19 Dec 2019 19:54:59 -0800 (PST)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255051.outbound.protection.outlook.com [40.92.255.51]) (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 AF76F120047; Thu, 19 Dec 2019 19:54:58 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Tu2RshW3k1PHu6lstZC1ZKhUSDBA1jWuhm9x8ODyaN+CwkLvDvJ0GJCqCINvwIzloeV+7NY67yJir6gtqNBeobH8VfWu7UuzWXAW90jF4bT7qYZZdkKI04MinQh7sWMtvv46iUh14dCpp+myAlIvIeC7zy8jaYfWRCyHrLNaUoXLIMAbj+5dA1R+45jpzBdnWfJ7v6tdSkn3D07BNaQaP20YP4OqHuj7mVgaHj9aczXt+gq46CWCu0IgwKJCZBJ4OKhRwsR+9cl8n+GVdHp2QoP3akXl/+jL6NRDtBOpSjEfm53EppjdZm+m3gEPL2vzpfyWphgPDd3MyV5g+AJciw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1zX2cStFJrMtsotedPYsyW4hCsWWUxx+1Y70YkpIFQo=; b=bjVt+FYJDH573b0vnkX/IpQNkTn31AO52DBDLZLD8KCdeNjfZ1XgiKKhuNptWHHISwlyfPPIMFLsdOjv/BJrG1bwiTJURTug1Cce13V4FwQNFJQJmyVFRc29jPDmSLlta895UUNm/juxq+WnSZ9fUyNHsylpGb1yTcqUYhEMriKQbMb5eLjeRY6LYDUPMpFx+rzMBMsc1WNQ8Y9kui0CmriG5yQHzuaEx/8/nwzMPvhNk+C34kVyXOeAk8Bunti6kFsciKeQmAp2xKzvxAbEFSM6OhoFgOKKUhbCXjoDnqIq4Y6v9g93kQrIffRx8mgBMGZk9VqBIjTN3x8aK+5TTw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hotmail.com; dmarc=pass action=none header.from=hotmail.com; dkim=pass header.d=hotmail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1zX2cStFJrMtsotedPYsyW4hCsWWUxx+1Y70YkpIFQo=; b=pWN9QZOxx+9g4HYTCbgSpHZTd2/aQbQDE5lh5XR/R0mM8QTqCLDv6hkKn1PHanUGwDzCr6xVy02McYFPDIaCv3LKeEcoVt8vdg2EcOZRJUSHpyKlNJPeTDpet3DU1R/Iz+tzjHHLwm8RzwIgvPh5oZC6lBmi8pb6Y/PM2LstyCO5Qxj8Up2kYY8xks2XsLM09hue5pCJm5RwWTTbLf8qRM8IiRSwC2ykdT15ERv/Al2K4B1lKACIjQzyjVEsFaN5tvmoUyWTZy0b2ibc5/BXYm0fA0JnobI482Ea6dBvWNV4Ro9F8uw7E9Y5DYd8uZ/FEESDLRm2GzDef7QV7flxbA==
Received: from HK2APC01FT053.eop-APC01.prod.protection.outlook.com (10.152.248.55) by HK2APC01HT115.eop-APC01.prod.protection.outlook.com (10.152.249.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.14; Fri, 20 Dec 2019 03:54:54 +0000
Received: from HK0PR03MB4066.apcprd03.prod.outlook.com (10.152.248.59) by HK2APC01FT053.mail.protection.outlook.com (10.152.249.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.14 via Frontend Transport; Fri, 20 Dec 2019 03:54:54 +0000
X-IncomingTopHeaderMarker: OriginalChecksum:367EEA580BCB53BF9471D0030CA602F0F7829D3D752D687CCB8FDE605D192593; UpperCasedChecksum:D40EFD0C6363DA8417B7FF466426AD7CEB01181C531DFA085DB364BD07201F43; SizeAsReceived:7764; Count:50
Received: from HK0PR03MB4066.apcprd03.prod.outlook.com ([fe80::ad00:a3b6:1bac:6f52]) by HK0PR03MB4066.apcprd03.prod.outlook.com ([fe80::ad00:a3b6:1bac:6f52%7]) with mapi id 15.20.2559.012; Fri, 20 Dec 2019 03:54:54 +0000
Date: Fri, 20 Dec 2019 11:55:06 +0800
From: "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "spring@ietf.org" <spring@ietf.org>
Cc: "spring-chairs@ietf.org" <spring-chairs@ietf.org>
References: <76CD132C3ADEF848BD84D028D243C927CD4F18A0@NKGEML515-MBX.china.huawei.com>
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.156[cn]
Message-ID: <HK0PR03MB4066565C1E5AFE69635EFD27FC2D0@HK0PR03MB4066.apcprd03.prod.outlook.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart638112861148_=----"
X-ClientProxiedBy: HK2PR02CA0179.apcprd02.prod.outlook.com (2603:1096:201:21::15) To HK0PR03MB4066.apcprd03.prod.outlook.com (2603:1096:203:9d::21)
X-Microsoft-Original-Message-ID: <2019122011550533263434@hotmail.com>
MIME-Version: 1.0
Received: from cmcc-PC (183.243.243.19) by HK2PR02CA0179.apcprd02.prod.outlook.com (2603:1096:201:21::15) with Microsoft SMTP Server (version=TLS1_1, cipher=) via Frontend Transport; Fri, 20 Dec 2019 03:54:52 +0000
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.156[cn]
X-Microsoft-Original-Message-ID: <2019122011550533263434@hotmail.com>
X-TMN: [VpoYupmpMKIDmKhyiF8+78JEJVcnmdXV]
X-MS-PublicTrafficType: Email
X-IncomingHeaderCount: 50
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-Correlation-Id: ba8c1573-5cbd-4ed5-50d6-08d785005ea4
X-MS-TrafficTypeDiagnostic: HK2APC01HT115:
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: wd5RPibheCco/L0ZGBZW6vzLPXdwjgPvNDr4uUzqnJp6RnAeBS2BkVh3UbyG1ZQbTgDZjRMVHANO1N8H23rQaGnxTFsieNtkPSW42qZH70BOCXSzxP2DgohYqZ8cBuW7LkM6wqbHKDmN7iB6ewSgwrQIbdhjd3M6O07Z1xgzyPAW1LJLvYkoleSeZnBtpTlhMi1Vu8jnGi7euCcMwqduti69pJGa5tJngKxvIV3OoU4=
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ba8c1573-5cbd-4ed5-50d6-08d785005ea4
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Dec 2019 03:54:53.8990 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT115
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/pAkXVep-WZw3urVnGnA4Kdh6SXQ>
Subject: Re: [spring] Update and request to adopt 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: Fri, 20 Dec 2019 03:55:02 -0000

Dear All,

Resource awareness segment routing is essential for enhanced VPN.  This feature also enriches SPRING by taking the resource of each hop enroute into account when doing the source routing.
Hope all the comments and suggestions are incorporated in this version. As a co-author I believe it is ready for WG adoption call.

Best Regards,
Zhenqiang Li


li_zhenqiang@hotmail.com
 
From: Dongjie (Jimmy)
Date: 2019-12-16 18:36
To: spring@ietf.org
CC: spring-chairs@ietf.org
Subject: [spring] Update and request to adopt draft-dong-spring-sr-for-enhanced-vpn
Dear WG, 
 
We just submitted a new revision of draft-dong-spring-sr-for-enhanced-vpn to solve the comments and suggestions received both during IETF106 and on the mail list.
 
The major changes are:
 
1. Following the chairs' suggestion, we reduced the description about network slicing and enhanced VPN service from the abstract, introduction and the following sections, so that it mainly focuses on the SR based data plane mechanism, use case and procedures. 
 
2. Solve the comments received from Sasha (thanks again).
 
3. Some editorial changes. 
 
After this update, this document describes a generic mechanism to enhance SR with resource awareness, and the major content of the document has been stable. Thus the co-authors believe it is ready for SPRING WG to adopt it, and would like to solicit to initiate the adoption poll on this document. Thanks. 
 
Best regards,
Jie
 
-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, December 16, 2019 5:13 PM
To: Takuya Miyasaka <ta-miyasaka@kddi.com>; Zhenqiang Li <li_zhenqiang@hotmail.com>; Fengwei Qin <qinfengwei@chinamobile.com>; Stewart Bryant <stewart.bryant@gmail.com>; Yongqing Zhu <zhuyq.gd@chinatelecom.cn>; Dongjie (Jimmy) <jie.dong@huawei.com>
Subject: New Version Notification for draft-dong-spring-sr-for-enhanced-vpn-06.txt
 
 
A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-06.txt
has been successfully submitted by Jie Dong and posted to the IETF repository.
 
Name: draft-dong-spring-sr-for-enhanced-vpn
Revision: 06
Title: Segment Routing for Resource Partitioned Virtual Networks
Document date: 2019-12-16
Group: Individual Submission
Pages: 18
URL:            https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-06.txt
Status:         https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
Htmlized:       https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-06
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dong-spring-sr-for-enhanced-vpn
Diff:           https://www.ietf.org/rfcdiff?url2=draft-dong-spring-sr-for-enhanced-vpn-06
 
Abstract:
   This document describes the mechanism to associate Segment Routing
   Identifiers (SIDs) with network resource attributes.  The resource-
   aware SIDs retain their original functionality, with the additional
   semantics of identifying the set of network resources available for
   the packet processing action.  These SIDs can be used to build SID
   lists with reserved network resources, which can be used for many
   network scenarios.  One typical use case is to provide SR virtual
   networks with required network topology and resource attributes.  The
   proposed mechanism is applicable to both segment routing with MPLS
   data plane (SR-MPLS) and segment routing with IPv6 data plane (SRv6).
 
 
                                                                                  
 
 
Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
 
The IETF Secretariat
 
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring