On Mon, Dec 18, 2017 at 1:03 PM, Lou Berger <lber...@labn.net> wrote:
> On 12/18/2017 04:01 PM, Andy Bierman wrote: > > > > > > On Mon, Dec 18, 2017 at 12:56 PM, Juergen Schoenwaelder > > <j.schoenwael...@jacobs-university.de > > <mailto:j.schoenwael...@jacobs-university.de>> wrote: > > > > On Mon, Dec 18, 2017 at 03:35:55PM -0500, Lou Berger wrote: > > > > > > Given the context (YANG module, and this WG), I think it should be > > > 6087bis (which is the same as 6087 in this respect). > > > > Does RFC 6087 formally update RFC 3688? > > > > > > Not intentionally. > > The 3688 text should probably be used instead of 6087bis. > > > yikes. really? so you think rfc6087 and the netmod RFCs were wrong? > > Not wrong, but the more generic text applies to all WGs, not just NETMOD WG. The YANG module contact info has the WG details. Since the NETMOD WG is long-lived, it may be better to list NETMOD WG. It doesn't seem to matter since this info is not in the registry anyway. > Thanks, > Lou > Andy > > > > > Andy > > > > > > > > Registrant Contact > > The individual/organization that is the registration contact > for > > the component being registered. Ideally, this will be the name > > and pertinent physical and network contact information. In the > > case of IETF developed standards, the Registrant will be the > IESG. > > > > /js > > > > > I'll put in the publication request as soon as this update is made. > > > > > > > Interestingly, it seems the "Registrant Contact" is not stored > > in the > > > > IANA maintained registry... > > > > > > > > > > true. > > > > > > Thanks, > > > Lou > > > > > > > /martin > > > > > > > > > > > >> Lou > > > >> > > > >> > > > >>> /js > > > >>> > > > >>> On Mon, Dec 18, 2017 at 03:00:26PM -0500, Lou Berger wrote: > > > >>>> Martin, Authors, > > > >>>> > > > >>>> is there a reason that the draft says: > > > >>>> > > > >>>> Registrant Contact: The IESG. > > > >>>> > > > >>>> vs the typical: > > > >>>> > > > >>>> Registrant Contact: The NETMOD WG of the IETF. > > > >>>> > > > >>>> Thanks, > > > >>>> > > > >>>> Lou > > > >>>> > > > >>>> On 12/18/2017 4:39 AM, Martin Bjorklund wrote: > > > >>>>> Hi, > > > >>>>> > > > >>>>> This version addresses the WGLC comments received. > > Specifically, I > > > >>>>> have added ietf-hardware-state, a config false version of > > > >>>>> ietf-hardware for non-NMDA implementations, in an Appendix. > > Please > > > >>>>> review the new text and the description statement in that > > module. > > > >>>>> > > > >>>>> I have also added a reference to the tree diagram draft and > > use the > > > >>>>> latest security guidelines template text. > > > >>>>> > > > >>>>> > > > >>>>> /martin > > > >>>>> > > > >>>>> internet-dra...@ietf.org <mailto:internet-dra...@ietf.org> > > wrote: > > > >>>>>> A New Internet-Draft is available from the on-line > > Internet-Drafts directories. > > > >>>>>> This draft is a work item of the Network Modeling WG of the > > IETF. > > > >>>>>> > > > >>>>>> Title : A YANG Data Model for Hardware > > Management > > > >>>>>> Authors : Andy Bierman > > > >>>>>> Martin Bjorklund > > > >>>>>> Jie Dong > > > >>>>>> Dan Romascanu > > > >>>>>> Filename : draft-ietf-netmod-entity-06.txt > > > >>>>>> Pages : 54 > > > >>>>>> Date : 2017-12-18 > > > >>>>>> > > > >>>>>> Abstract: > > > >>>>>> This document defines a YANG data model for the > > management of > > > >>>>>> hardware on a single server. > > > >>>>>> > > > >>>>>> > > > >>>>>> The IETF datatracker status page for this draft is: > > > >>>>>> https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/ > > <https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/> > > > >>>>>> > > > >>>>>> There are also htmlized versions available at: > > > >>>>>> https://tools.ietf.org/html/draft-ietf-netmod-entity-06 > > <https://tools.ietf.org/html/draft-ietf-netmod-entity-06> > > > >>>>>> > > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-entity-06 > > <https://datatracker.ietf.org/doc/html/draft-ietf-netmod-entity-06> > > > >>>>>> > > > >>>>>> A diff from the previous version is available at: > > > >>>>>> > > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-entity-06 > > <https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-entity-06> > > > >>>>>> > > > >>>>>> > > > >>>>>> Please note that it may take a couple of minutes from the > > time of submission > > > >>>>>> until the htmlized version and diff are available at > > tools.ietf.org <http://tools.ietf.org>. > > > >>>>>> > > > >>>>>> Internet-Drafts are also available by anonymous FTP at: > > > >>>>>> ftp://ftp.ietf.org/internet-drafts/ > > <ftp://ftp.ietf.org/internet-drafts/> > > > >>>>>> > > > >>>>>> _______________________________________________ > > > >>>>>> netmod mailing list > > > >>>>>> netmod@ietf.org <mailto:netmod@ietf.org> > > > >>>>>> https://www.ietf.org/mailman/listinfo/netmod > > <https://www.ietf.org/mailman/listinfo/netmod> > > > >>>>>> > > > >>>>> _______________________________________________ > > > >>>>> netmod mailing list > > > >>>>> netmod@ietf.org <mailto:netmod@ietf.org> > > > >>>>> https://www.ietf.org/mailman/listinfo/netmod > > <https://www.ietf.org/mailman/listinfo/netmod> > > > >>>>> > > > >>>> _______________________________________________ > > > >>>> netmod mailing list > > > >>>> netmod@ietf.org <mailto:netmod@ietf.org> > > > >>>> https://www.ietf.org/mailman/listinfo/netmod > > <https://www.ietf.org/mailman/listinfo/netmod> > > > > > > _______________________________________________ > > > netmod mailing list > > > netmod@ietf.org <mailto:netmod@ietf.org> > > > https://www.ietf.org/mailman/listinfo/netmod > > <https://www.ietf.org/mailman/listinfo/netmod> > > > > -- > > Juergen Schoenwaelder Jacobs University Bremen gGmbH > > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | > Germany > > Fax: +49 421 200 3103 <http://www.jacobs-university.de/ > > <http://www.jacobs-university.de/>> > > > > > >
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
