Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt - IPR Call

Qin Wu <bill.wu@huawei.com> Thu, 25 July 2019 01:20 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498161200B9; Wed, 24 Jul 2019 18:20:16 -0700 (PDT)
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 fiOhAPjVgC2A; Wed, 24 Jul 2019 18:20: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 67957120625; Wed, 24 Jul 2019 18:20:14 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A8D433EC72271276BD74; Thu, 25 Jul 2019 02:20:12 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 25 Jul 2019 02:20:12 +0100
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.207]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 25 Jul 2019 09:18:04 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
CC: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "'andersliu(刘琛)'" <andersliu@tencent.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology@ietf.org>
Thread-Topic: WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt - IPR Call
Thread-Index: AdVCgk73ThAX9/suQM6moAS1lHIUBwAA06CA
Date: Thu, 25 Jul 2019 01:18:04 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA8836825@nkgeml513-mbs.china.huawei.com>
References: <00df01d54283$fa247560$ee6d6020$@ndzh.com>
In-Reply-To: <00df01d54283$fa247560$ee6d6020$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.182.159]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/yZMS52JaDdVWNUj7AgD7bdLs41k>
Subject: Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt - IPR Call
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 01:20:16 -0000

Thanks Sue for the followup. The proposed next step looks good to me.
I will fix YANGlint issue and inform other authors about IPR call.

-Qin
________________________________________
发件人: Susan Hares [shares@ndzh.com]
发送时间: 2019年7月25日 8:57
收件人: i2rs@ietf.org
抄送: Dongjie (Jimmy); 'andersliu(刘琛)'; mohamed.boucadair@orange.com; draft-ietf-i2rs-yang-l2-network-topology@ietf.org
主题: WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt  -  IPR Call

Qin:

Thank you for catching up with these edits.   The Yanglint still has an
error in this draft.   Would take of this while I start the IPR Call?

This draft has been through WG LC 3 times with the same technical content in
I2RS.   It has been through 3 early  reviews.

 After these delays, I need to move rapidly to close this work with the
following 3 steps:

1) All authors need to send in their IPR Statement by Friday 7/26
2) We'll do a 2 week WG call (7/26 to 8/9/2019) and cross post to rtgwg WG
3)   At the same time, we will ask for another Yang Doctor review of this
document.

Our AD (Martin) have indicated that I have this one last attempt to get
consensus.

Would you also help your co-authors respond to the IPR statement?

Sue Hares