Re: [Softwires] Questions for authors of draft-ietf-softwire-map-mib-11

"Liubing (Leo)" <leo.liubing@huawei.com> Thu, 16 November 2017 03:05 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B00412943A; Wed, 15 Nov 2017 19:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 YQCyTuwl9xqz; Wed, 15 Nov 2017 19:05:00 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F20FD126CC4; Wed, 15 Nov 2017 19:04:59 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5018DB4225585; Thu, 16 Nov 2017 03:04:56 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 16 Nov 2017 03:04:31 +0000
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.94]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0361.001; Thu, 16 Nov 2017 11:04:23 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>
CC: Ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" <softwires@ietf.org>, "draft-ietf-softwire-map-mib@ietf.org" <draft-ietf-softwire-map-mib@ietf.org>
Thread-Topic: Questions for authors of draft-ietf-softwire-map-mib-11
Thread-Index: AdNehv6RD+4sivxWTSeLMw8d49LC5g==
Date: Thu, 16 Nov 2017 03:04:23 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C78D6BC0@nkgeml514-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.146.85]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/xScAOWgU17ZHx2L2R8-Ca81cLsA>
Subject: Re: [Softwires] Questions for authors of draft-ietf-softwire-map-mib-11
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 03:05:03 -0000

Hi Dear chairs and all,

I confirm that I have no IPR related to this draft. And I'm not aware of any IPR related.

B.R.
Bing Liu
-----Original Message-----
From: Yong Cui [mailto:cuiyong@tsinghua.edu.cn]
Sent: Tuesday, November 14, 2017 4:27 PM
To: Yu Fu
Cc: Ian Farrer; softwires@ietf.org; draft-ietf-softwire-map-mib@ietf.org;
Yuchi Chen; Dong Jiang
Subject: Questions for authors of draft-ietf-softwire-map-mib-11

Hi, authors of draft-ietf-softwire-map-mib-11,

Before we submit this doc to IESG, we need to have the following answer from each of your authors.

(7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why?

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

BTW, if  there are any existing implementations of the protocol, please also send to the list.

Additionally, there are two comments from nits. 
  == Unused Reference: 'RFC7598' is defined on line 627, but no explicit
     reference was found in the text

  -- Obsolete informational reference (is this intentional?): RFC 7749
     (Obsoleted by RFC 7991)



Cheers,

Yong