RE: Last Call: <draft-ietf-tictoc-1588v2-yang-09.txt> (YANG Data Model for IEEE 1588-2008) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom,

Thanks a lot for your good comments.
Please see my comments inline.

B.R.,
Yuanlong

-----Original Message-----
From: tom petch [mailto:daedulus@xxxxxxxxxxxxx] 
Sent: Wednesday, August 29, 2018 6:32 PM
To: ietf@xxxxxxxx
Cc: tictoc-chairs@xxxxxxxx; draft-ietf-tictoc-1588v2-yang@xxxxxxxx; tictoc@xxxxxxxx; suresh@xxxxxxxxxx
Subject: Re: Last Call: <draft-ietf-tictoc-1588v2-yang-09.txt> (YANG Data Model for IEEE 1588-2008) to Proposed Standard

Looks good; I commented on an earlier version of this document and my comments have been addressed.

Two further thoughts at this time.

The Security Considerations makes no mention of  RESTCONF, which makes me think that this is not the usual template for this section.
[JYL] Good catch, we will stick to the newest template for the next revision.

And I am curious as to what the final wording of A.2 will be.
Currently, it says
"Those IEEE forms and
   mechanisms will be updated as needed during the development of this
   document ..."
so that the IEEE has the IPR to use this RFC as a basis for future work.
The development of this document is nearly, but not quite, complete so have the forms been produced and signed or when will they be, should the RFC reference the forms and what form of words will this paragraph use in the RFC as published? It is a bit like IANA Considerations where the I-D is proposing an action but the RFC says it has been done.  As I say, I am curious to see how this is handled.
[JYL] These texts reflects the situation when the draft was adopted in the TICTOC WG, and the precaution proposed at that time by the IEEE 1588. Under the leadership of AD and WG chairs, all the authors had already signed a non-exclusive license for IEEE to create derivative works from this work (including the newest YANG module of the RFC-to-be), and no updates of those IEEE forms or mechanism is foreseen, I think we can remove this sentence safely.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@xxxxxxxx>
To: "IETF-Announce" <ietf-announce@xxxxxxxx>
Cc: <tictoc-chairs@xxxxxxxx>; <draft-ietf-tictoc-1588v2-yang@xxxxxxxx>;
<tictoc@xxxxxxxx>; <suresh@xxxxxxxxxx>
Sent: Friday, August 24, 2018 5:13 PM

> The IESG has received a request from the Timing over IP Connection and 
> Transfer of Clock WG (tictoc) to consider the following document: -
'YANG
> Data Model for IEEE 1588-2008'
>   <draft-ietf-tictoc-1588v2-yang-09.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
final
> comments on this action. Please send substantive comments to the 
> ietf@xxxxxxxx mailing lists by 2018-09-07. Exceptionally, comments may
be
> sent to iesg@xxxxxxxx instead. In either case, please retain the
beginning of
> the Subject line to allow automated sorting.
>
> Abstract
>
>    This document defines a YANG data model for the configuration of
>    IEEE 1588-2008 devices and clocks, and also retrieval of the
>    configuration information, data set and running states of IEEE
>    1588-2008 clocks. The YANG module in this document conforms to the
>    Network Management Datastore Architecture (NMDA).
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-yang/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-yang/ballot/
>
> No IPR declarations have been submitted directly on this I-D.





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux