Re: [TICTOC] Eric Rescorla's No Objection on draft-ietf-tictoc-1588v2-yang-10: (with COMMENT)

Jiangyuanlong <jiangyuanlong@huawei.com> Thu, 11 October 2018 09:42 UTC

Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B6D130E1C; Thu, 11 Oct 2018 02:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 uG_MEgM1lgnf; Thu, 11 Oct 2018 02:42:18 -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 4A3D8130E02; Thu, 11 Oct 2018 02:42:18 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 9AF5DAE497E6F; Thu, 11 Oct 2018 10:42:14 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 11 Oct 2018 10:42:16 +0100
Received: from DGGEML532-MBS.china.huawei.com ([169.254.7.198]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0399.000; Thu, 11 Oct 2018 17:42:06 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "tictoc-chairs@ietf.org" <tictoc-chairs@ietf.org>, "draft-ietf-tictoc-1588v2-yang@ietf.org" <draft-ietf-tictoc-1588v2-yang@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>, Karen O'Donoghue <odonoghue@isoc.org>
Thread-Topic: Eric Rescorla's No Objection on draft-ietf-tictoc-1588v2-yang-10: (with COMMENT)
Thread-Index: AQHUYPZIEcJZucvsCEm0kmweayeuE6UZw5RQ
Date: Thu, 11 Oct 2018 09:42:06 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBC218231@dggeml532-mbs.china.huawei.com>
References: <153921639003.5775.17570593827856629386.idtracker@ietfa.amsl.com>
In-Reply-To: <153921639003.5775.17570593827856629386.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.171.86]
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/tictoc/Sgbgy3VF-BBmYZQWXLJjnxaOtbo>
Subject: Re: [TICTOC] Eric Rescorla's No Objection on draft-ietf-tictoc-1588v2-yang-10: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 09:42:22 -0000

Hi Eric,

Thanks for your review and comments, please see my replies prefixed with [YJ].

Regards,
Yuanlong

> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@rtfm.com]
> Sent: Thursday, October 11, 2018 8:07 AM
> To: The IESG
> Cc: tictoc-chairs@ietf.org; draft-ietf-tictoc-1588v2-yang@ietf.org;
> tictoc@ietf.org; odonoghue@isoc.org; Karen O'Donoghue
> Subject: Eric Rescorla's No Objection on draft-ietf-tictoc-1588v2-yang-10:
> (with COMMENT)
> 
> Eric Rescorla has entered the following ballot position for
> draft-ietf-tictoc-1588v2-yang-10: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-yang/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Rich version of this review at:
> https://mozphab-ietf.devsvcdev.mozaws.net/D3264
> 
> 
> I concur with Ben Campbell's DISCUSS.
> 
> COMMENTS
> S 1.
> >      2008.
> >
> >      o  When the IEEE 1588 standard is revised (e.g. the IEEE 1588
> >      revision in progress at the time of writing this document), it will
> >      add some new optional features to its data sets.  The YANG module
> >      of this document MAY be revised and extended to support these new
> 
> Nit: this looks like it's more a statement of fact than normative
> langauge.
> 
[YJ] For consistency, "MAY" in this bullet will change to "may", and "can" in bullet 4 will also change to "may".

> 
> S 1.
> >      dedicated YANG module for its profile. The profile's YANG module
> >      SHOULD use YANG "import" to import the IEEE 1588-2008 YANG
> module
> >      as its foundation.  Then the profile's YANG module SHOULD use
> YANG
> >      "augment" to add any profile-specific enhancements.
> >
> >      o  A product that conforms to a profile standard can also create
> 
> Is the "can" in this statement different from the "may" in the
> previous bullet.
> 
[YJ] resolved as above.
> 
> S 7.
> >      create derivative works from this document. Those IEEE forms and
> >      mechanisms will be updated as needed for any future IETF YANG
> >      modules for IEEE 1588 (The signed forms are held by the IEEE
> >      Standards Association department of Risk Management and
> Licensing.).
> >      This will help to make the future transfer of work from IETF to
> >      IEEE occur as smoothly as possible.
> 
> I don't mean to be overly legal, but why is it that you think that the
> named authors consent is what's relevant here as opposed to the IETF,
> or everyone who has submitted text?
> 
[YJ] None of the authors are legal experts;) but during the development of this appendix, we did diligently solicit the guidance from quite a few ADs (such as Suresh), and the texts reflect exactly the legal advices we got from the IETF legal counsel for IPR matters and the IEEE Standards Association Manager of Standards Intellectual Property. Please also refer to RFC 4663 for the similar procedural texts.