IETF Logo Mail Archive

[Teas] 答复: Discussion on Control Plane Considerations for Enhanced VPN (draft-dong-teas-enhanced-vpn-control-plane)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 07 November 2019 02:10 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD6E1200C3; Wed, 6 Nov 2019 18:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 CQ2Ea7ktsecC; Wed, 6 Nov 2019 18:10:25 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 04F0912008F; Wed, 6 Nov 2019 18:10:24 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 763FA760CA22FD9F5DFE; Thu, 7 Nov 2019 02:10:21 +0000 (GMT)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 7 Nov 2019 02:10:21 +0000
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 7 Nov 2019 02:10:20 +0000
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 7 Nov 2019 02:10:20 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 7 Nov 2019 10:10:16 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Takuya Miyasaka <ta-miyasaka@kddi-research.jp>, "draft-dong-teas-enhanced-vpn-control-plane@ietf.org" <draft-dong-teas-enhanced-vpn-control-plane@ietf.org>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Discussion on Control Plane Considerations for Enhanced VPN (draft-dong-teas-enhanced-vpn-control-plane)
Thread-Index: AQHVlQoeUGuLFAbKeUCOjEF09PBxn6d+9MbA
Date: Thu, 07 Nov 2019 02:10:15 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927CD33BE5F@NKGEML515-MBX.china.huawei.com>
References: <1dc33a97-289a-f4e6-8043-2c0c1472d3f0@kddi-research.jp>
In-Reply-To: <1dc33a97-289a-f4e6-8043-2c0c1472d3f0@kddi-research.jp>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Wly-OaqoRGIKthHj8WzTl4-jpxI>
Subject: [Teas] 答复: Discussion on Control Plane Considerations for Enhanced VPN (draft-dong-teas-enhanced-vpn-control-plane)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 02:10:27 -0000

Hi Takuya, 

Thanks a lot for your review and comments. Please see my replies inline with [Jie]:

-----邮件原件-----
发件人: Takuya Miyasaka [mailto:ta-miyasaka@kddi-research.jp] 
发送时间: 2019年11月7日 9:24
收件人: draft-dong-teas-enhanced-vpn-control-plane@ietf.org
抄送: teas@ietf.org
主题: Discussion on Control Plane Considerations for Enhanced VPN (draft-dong-teas-enhanced-vpn-control-plane)

Dear authors of draft-dong-teas-enhanced-vpn-control-plane,

Thanks for introducing this new draft [1] which describes a control plane consideration for Enhanced VPN. IMO, this document needs to deliver another considerations or technical notes for the way to assign a dedicated segment routing SID for a reserved resources on a network node.

[Jie] Agreed this also needs to be considered. As the current version of this document is generic considerations about control plane, the segment routing specific descriptions are not included yet. In next version we could add some generic descriptions about the assignment and distribution of resource identifiers, and we may add some descriptions about the SR based mechanism.

Furthermore, as for the distributed control plane (section 3.1), why don't you mention the SR-policy (draft-ietf-spring-segment-routing-policy)? I think the SR-Policy can be a candidate approach for the control plane of Enhanced VPN; especially BGP based L3VPN (RFC4364) is utilized for the overlay of Enhanced VPN.

[Jie] Yes, BGP SR policy is part of the control plane for the SR based mechanism, the reason of not mentioning it is the same as the above. Later we could add it as a candidate technology for the SR based mechanism.

Best regards,
Jie


   [1]
https://datatracker.ietf.org/doc/draft-dong-teas-enhanced-vpn-control-plane/

Regards,
Takuya

v2.23.0 | Report a Bug | By Email