[OPSAWG] RE CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Qin Wu <bill.wu@huawei.com> Fri, 14 August 2020 06:10 UTC
Return-Path: <bill.wu@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 5B45E3A0D62 for <opsawg@ietfa.amsl.com>; Thu, 13 Aug 2020 23:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 5kELcID_5XS2 for <opsawg@ietfa.amsl.com>; Thu, 13 Aug 2020 23:09:59 -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 E2CE63A0D5F for <opsawg@ietf.org>; Thu, 13 Aug 2020 23:09:58 -0700 (PDT)
Received: from lhreml708-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8E1A7213A6B0721399A8 for <opsawg@ietf.org>; Fri, 14 Aug 2020 07:09:57 +0100 (IST)
Received: from lhreml708-chm.china.huawei.com (10.201.108.57) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 14 Aug 2020 07:09:57 +0100
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Fri, 14 Aug 2020 07:09:56 +0100
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.234]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0487.000; Fri, 14 Aug 2020 14:09:52 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>, opsawg <opsawg@ietf.org>
Thread-Topic: RE CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Thread-Index: AdZyAVGAmooZDqT4TD2avgFE7d1wxQ==
Date: Fri, 14 Aug 2020 06:09:52 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAAD9044C5@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.164.120.119]
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/iQiBiIe5RHM-4Lmux0wMFzOUqVQ>
Subject: [OPSAWG] RE CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
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: Fri, 14 Aug 2020 06:10:00 -0000
Support, it is important to decouple network layer from service layer and avoid layer violation. -Qin -----邮件原件----- 发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2020年8月13日 20:49 收件人: opsawg <opsawg@ietf.org> 主题: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the status of the L3NM, L2NM, and the VPN common work. While this VPN common YANG module started as an individual document (per the chairs’ request), the L2NM and L3NM modules need to choose a direction for how to handle common typedefs and groupings between them. On the virtual meeting we did a hum which indicated “Pianissimo” support. Again, the hum system had some interesting rules, so this is not conclusive, but seems to favor that this common module work should exist as its own, standalone document that both L2NM and L3NM will consume. In this manner, one would not need to import either L2NM or L3NM to make use of/extend these common attributes. To that end, the chairs would like a call for adoption of draft-bgbw-opsawg-vpn-common. Additionally, comments on the approach and the choice of common attributes are welcome, especially from those that were unable to attend the IETF 108 virtual meeting. This serves as a two week call for adoption ending on August 27, 2020. Thanks. Joe _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg