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

"Steve Wood (swood1)" <swood1@cisco.com> Mon, 08 July 2019 14:59 UTC

Return-Path: <swood1@cisco.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 9D1CF1201EC for <opsawg@ietfa.amsl.com>; Mon, 8 Jul 2019 07:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=BOb7y2DQ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Ro8C2o+t
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 KCRqeeeBUTKC for <opsawg@ietfa.amsl.com>; Mon, 8 Jul 2019 07:59:45 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1691201E9 for <opsawg@ietf.org>; Mon, 8 Jul 2019 07:59:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6418; q=dns/txt; s=iport; t=1562597985; x=1563807585; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=2M/fEcr2ozAjdQTpbOMfeVNagSFtYRPwyuZcvFjDpk4=; b=BOb7y2DQNWjn3Cuz3REE1HVMlhsSlba+5VVC74q9QS3kKZ4zUz8leK+7 DO5ud5ecA0Gwu+XgX2Be4u8qxDdDTK0+6Xvj7Z3Ek/PQC8ekxqBj8Jmag 8VMGSUjARrpSDMeduwbun64INuwum+FMOiNalPoUGQ69zjX9lYemVf1b0 A=;
IronPort-PHdr: 9a23:RXpK5B8Imza2Uf9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVdWaDkr3ddbhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BKAADpWCNd/5BdJa1lHAEBAQQBAQcEAQGBUwcBAQsBgUNQA2pVIAQLKIQcg0cDhFKJdoI2JZdGgS4UgRADVAkBAQEMAQEYCwoCAQGDekYCF4IhIzQJDgEDAQEEAQECAQVtijcMhUoBAQEBAwEBEBERDAEBLAkDCwQCAQYCEQQBAQMCIwMCAgIlCxQBCAgCBAESIoMAAYFqAx0BAgyOCpBgAoE4iGBxgTKCeQEBBYE2Ag5BgnMYghIJgQwoAYteghaBOAwTgU5+PoJhAQECAQEWgQ+DQjKCJoExAYp6gkSFIJZGBgMCgheGVo0uG4IsbYY0jjGNMIEwhhCPfQIEAgQFAg4BAQWBUDiBWHAvISoBc4FOCYI4g3GFFIU/coEpjUgBAQ
X-IronPort-AV: E=Sophos;i="5.63,466,1557187200"; d="scan'208";a="591281377"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jul 2019 14:59:44 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x68ExhX6030837 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jul 2019 14:59:43 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 09:59:42 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 09:59:42 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 8 Jul 2019 09:59:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2M/fEcr2ozAjdQTpbOMfeVNagSFtYRPwyuZcvFjDpk4=; b=Ro8C2o+tf6oRZkmvnN2dOk9iD9vNAZLNNVHG/NGykDeRvKhofR3XgJEGn++CVJyWHGyRAKYtI0jM5EaWFYJYN+qIGAqfGecBV8iUYAwP64AsL1sxsgKR9c/M/ejqrSMqISQ3VhO7vjy7S5+JtnO7SF5/tej8ob2IXjwjUokwbUc=
Received: from BYAPR11MB3157.namprd11.prod.outlook.com (20.177.126.222) by BYAPR11MB3350.namprd11.prod.outlook.com (20.177.186.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.15; Mon, 8 Jul 2019 14:45:25 +0000
Received: from BYAPR11MB3157.namprd11.prod.outlook.com ([fe80::b4e2:a46e:6cfe:a8fc]) by BYAPR11MB3157.namprd11.prod.outlook.com ([fe80::b4e2:a46e:6cfe:a8fc%6]) with mapi id 15.20.2052.019; Mon, 8 Jul 2019 14:45:25 +0000
From: "Steve Wood (swood1)" <swood1@cisco.com>
To: "Wubo (lana)" <lana.wubo@huawei.com>, Tianran Zhou <zhoutianran@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-sun-opsawg-sdwan-service-model-03.txt
Thread-Index: AQHVNZvG9escw7iTIEO9luZNF7Y72A==
Date: Mon, 08 Jul 2019 14:45:24 +0000
Message-ID: <BD8F2573-B807-4039-9057-9D014CA547CF@cisco.com>
References: <b973760a1f074cfd84f042e47e765cba@huawei.com>
In-Reply-To: <b973760a1f074cfd84f042e47e765cba@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=swood1@cisco.com;
x-originating-ip: [2001:420:c0c4:1007::2cb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6a2422e4-c634-4be6-def4-08d703b2e960
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3350;
x-ms-traffictypediagnostic: BYAPR11MB3350:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BYAPR11MB3350FCAA9EA8108BD91F6AC391F60@BYAPR11MB3350.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(396003)(346002)(136003)(39860400002)(376002)(199004)(189003)(13464003)(6486002)(68736007)(6436002)(110136005)(15650500001)(6246003)(8936002)(6116002)(305945005)(53546011)(2906002)(8676002)(316002)(2501003)(81156014)(81166006)(14444005)(478600001)(33656002)(58126008)(256004)(6512007)(86362001)(99286004)(71190400001)(71200400001)(53936002)(14454004)(6306002)(7736002)(66556008)(64756008)(25786009)(446003)(102836004)(76116006)(66476007)(6506007)(91956017)(66946007)(966005)(73956011)(76176011)(2616005)(229853002)(5660300002)(476003)(46003)(66574012)(11346002)(186003)(36756003)(486006)(66446008); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3350; H:BYAPR11MB3157.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: S89nPlXL4YCW7kFHd9qh7InZaOmjd32cRJOKol36tHconKqgzf6rgb3cEZY3A4USl68bg2Q24leGX2lamT59yWzashl8KQPCyRtGR4yUiF7gRy2NEVgri5ZGnYoV1Swv2+/egXsUbIJ4yECdBT/OVNghwJlcJUxNsfJsnre5Y/diU2xvv1vCzDk4HvUR8c1lOdi5aXCdYL9/7mJ+kZw4ZaYogwoDh+Da2bXg63iNpMpgFEthWXreflLVR8oF/yWQP8+MsIOq+VAyvq8eGhThRDV/xnGI9/ghKlZ83wNh1G+ki+5zj8Q0GIpxHofHE4fEeypOvKFFF4rY2edEWChRwK8agK1A9kW59kFCVeADufiRfrHM0t/GGXqf2ail3olrwLgDKlpIYl3TuGoc2mLKZZxPKXs52+OEYUeM7k5VQ6U=
Content-Type: text/plain; charset="utf-8"
Content-ID: <5745576D5753A140A0328A711643B08F@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a2422e4-c634-4be6-def4-08d703b2e960
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 14:45:24.8977 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: swood1@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3350
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/WCReqFz6Ej_vQnAUdFLhX0d5I1w>
Subject: Re: [OPSAWG] New Version Notification for draft-sun-opsawg-sdwan-service-model-03.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, 08 Jul 2019 14:59:49 -0000

Tianran,

The major difference between the two drafts is that the Sun draft attempts to prescribe the Overlay dataplane and control plane.  The OSE model does not attempt to do this, it only prescribes the external interfaces.

As for the subject matter of the draft, I do not know OPSAWG charter well, but based in the name/subject matter of the WG I could see your point that the Sun draft may be a better fit for RTGWG as well.   But it would be better to let the draft authors comment to their reasoning for that.

Steve
    
    -----邮件原件-----
    发件人: Tianran Zhou 
    发送时间: 2019年7月1日 15:54
    收件人: Wubo (lana) <lana.wubo@huawei.com>; opsawg@ietf.org
    主题: RE: New Version Notification for draft-sun-opsawg-sdwan-service-model-03.txt
    
    Hi Bo,
    
    Very helpful to describe the difference between the OSE service model and this SD-WAN service model.
    A further question is why do you think the OPSAWG is the right home for the this service model when the OSE service model is working in RTGWG.
    I see you joined both drafts, I am interested to know your thoughts on this.
    
    Thanks,
    Tianran
    
    > -----Original Message-----
    > From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Wubo (lana)
    > Sent: Monday, July 01, 2019 2:57 PM
    > To: opsawg@ietf.org
    > Subject: [OPSAWG] New Version Notification for 
    > draft-sun-opsawg-sdwan-service-model-03.txt
    > 
    > Dear WG,
    > 
    > We submitted the 03 version to better align with the MEF SD-WAN project.
    > https://tools.ietf.org/html/draft-sun-opsawg-sdwan-service-model-03
    > 
    > Charles Eckel, as a new co-author, helped update the references for 
    > the MEF specification and polish the entire text for readability.
    > 
    > We also added Appendix 2 to explain the difference between the RTGWG 
    > OSE model and the SD-WAN model, as the last IETF meeting had concerns 
    > about overlapping work.
    > 
    > Further Comments, suggestions, input are welcome.
    > 
    > Best Regards,
    > Bo (on behalf of coauthors)
    > 
    > 
    > 
    > -----邮件原件-----
    > 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
    > 发送时间: 2019年6月29日 15:42
    > 收件人: Qiong Sun <sunqiong.bri@chinatelecom.cn>; Charles Eckel 
    > <eckelcu@cisco.com>; Wubo (lana) <lana.wubo@huawei.com>; Honglei Xu 
    > <sunqiong.bri@chinatelecom.cn>; Wubo (lana) <lana.wubo@huawei.com>; 
    > Qin Wu <bill.wu@huawei.com>
    > 主题: New Version Notification for
    > draft-sun-opsawg-sdwan-service-model-03.txt
    > 
    > 
    > A new version of I-D, draft-sun-opsawg-sdwan-service-model-03.txt
    > has been successfully submitted by Bo Wu and posted to the IETF repository.
    > 
    > Name:		draft-sun-opsawg-sdwan-service-model
    > Revision:	03
    > Title:		A YANG Data Model for SD-WAN Service Delivery
    > Document date:	2019-06-29
    > Group:		Individual Submission
    > Pages:		48
    > URL:
    > https://www.ietf.org/internet-drafts/draft-sun-opsawg-sdwan-service-mo
    > de
    > l-03.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-03
    > Htmlized:
    > https://datatracker.ietf.org/doc/html/draft-sun-opsawg-sdwan-service-m
    > od
    > el
    > Diff:
    > https://www.ietf.org/rfcdiff?url2=draft-sun-opsawg-sdwan-service-model
    > -0
    > 3
    > 
    > Abstract:
    >    This document provides a YANG data model for an SD-WAN service.  An
    >    SD-WAN service is a connectivity service offered by a service
    >    provider network to provide connectivity across different locations
    >    of a customer network or between a customer network and an external
    >    network, such as the Internet or a private/public cloud network.
    >    This connectivity is provided as an overlay constructed using one of
    >    more underlay networks.  The model can be used by a service
    >    orchestrator of a service provider to request, configure, and manage
    >    the components of an SD-WAN 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
    > 
    > _______________________________________________
    > OPSAWG mailing list
    > OPSAWG@ietf.org
    > https://www.ietf.org/mailman/listinfo/opsawg