[OPSAWG] Fwd: New Version Notification for draft-sun-opsawg-sdwan-service-model-01.txt

"Wubo (lana)" <lana.wubo@huawei.com> Mon, 22 October 2018 09:10 UTC

Return-Path: <lana.wubo@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1E6130DFB; Mon, 22 Oct 2018 02:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 xdVoer8mnTZV; Mon, 22 Oct 2018 02:10:14 -0700 (PDT)
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 44D05130DFF; Mon, 22 Oct 2018 02:10:13 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C7A0045B016D1; Mon, 22 Oct 2018 10:10:07 +0100 (IST)
Received: from DGGEMI401-HUB.china.huawei.com (10.3.17.134) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 22 Oct 2018 10:10:09 +0100
Received: from DGGEMI526-MBX.china.huawei.com ([169.254.8.122]) by dggemi401-hub.china.huawei.com ([10.3.17.134]) with mapi id 14.03.0399.000; Mon, 22 Oct 2018 17:09:58 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: New Version Notification for draft-sun-opsawg-sdwan-service-model-01.txt
Thread-Index: AdRp4Z1b1CcbZAiMRM2R6bzHWra/dg==
Date: Mon, 22 Oct 2018 09:09:58 +0000
Message-ID: <520ECC8D9CA1724BA1CE492DF898F6A339699D@DGGEMI526-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.189.23]
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/opsawg/QBRxRM1knk3uIke7iDOkSKOk2mk>
Subject: [OPSAWG] Fwd: New Version Notification for draft-sun-opsawg-sdwan-service-model-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 09:10:17 -0000

Dear all,

We would like to define a CE-based VPN service model to differentiate from PE-based L3&L2 service model. The link is at https://tools.ietf.org/html/draft-sun-opsawg-sdwan-service-model-01

Since we feel the SD-WAN related work in IETF, like https://tools.ietf.org/html/draft-dukes-spring-sr-for-sdwan-00, https://tools.ietf.org/html/draft-rosen-bess-secure-l3vpn-01,
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-02, are all enhanced CE-based VPN. But there is no consistent SD-WAN or CE-based VPN service definition.
In the drafts, each assumes a different SD-WAN functionality of CE, like hybrid WAN and L3-L7 flow classification in SR for sdwan draft, and L3 virtual network separation inside IPSEC VPN 
In secure L3VPN draft.

So, in this draft, based on our understanding of SD-WAN service and together with other SD-WAN draft, we define the SD-WAN main service components and hope that this will help
clarifying the main service feature of SD-WAN and  helping to automate the service management.

We'd like to solicit more comments on whether this service model meets your thought of the SD-WAN service.

Thanks,

 Bo, on behalf of the co-authors

> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-
> drafts@ietf.org]
> 发送时间: 2018年10月22日 15:53
> 收件人: Qin Wu <bill.wu@huawei.com>; Honglei Xu
> <sunqiong.bri@chinatelecom.cn>; Wubo (lana)
> <lana.wubo@huawei.com>; Qiong Sun
> <sunqiong.bri@chinatelecom.cn>; Wubo (lana)
> <lana.wubo@huawei.com>
> 主题: New Version Notification for draft-sun-opsawg-
> sdwan-service-model-01.txt
> 
> 
> A new version of I-D, draft-sun-opsawg-sdwan-service-
> model-01.txt
> has been successfully submitted by Bo Wu and posted to
> the IETF repository.
> 
> Name:		draft-sun-opsawg-sdwan-service-model
> Revision:	01
> Title:		A YANG Data Model for SD-WAN VPN
> Service Delivery
> Document date:	2018-10-21
> Group:		Individual Submission
> Pages:		40
> URL:            https://www.ietf.org/internet-drafts/draft-sun-
> opsawg-sdwan-service-model-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-sun-
> opsawg-sdwan-service-model/
> Htmlized:       https://tools.ietf.org/html/draft-sun-opsawg-
> sdwan-service-model-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-
> sun-opsawg-sdwan-service-model
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-sun-
> opsawg-sdwan-service-model-01
> 
> Abstract:
>    This document defines a SD-WAN VPN service model to
> enable a Service
>    Provider to deliver SD-WAN VPN services to its customers
> by
>    provisioning the CE devices on behalf of the customer.
> This document
>    is based on provider-provisioned CE-based VPNs as
> described in
>    [RFC4110].
> 
>    This model provides an abstracted view of the SD-WAN
> VPN service
>    configuration components, and is intended to be
> instantiated at the
>    management system to deliver the overall service.
> 
> 
> 
> 
> 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