Hi Tom, I realized that IANA text similar to RFC 7224 will be required before publishing the model. However, I was pressed for time and wanted to assure people agreed with the structure before adding it.
A bigger question is whether IANA has the bandwidth to maintain an increasing number of YANG models. Direct correlation to a registry would be facilitated by the decoupling of IETF YANG models from the RFC process (an ongoing discussion). Thanks, Acee On 5/12/17, 7:06 AM, "t.petch" <ie...@btconnect.com> wrote: >Acee > >I don't understand what you are doing. > >Martin suggested >" Since it is based on an IANA >registry, >>should it be in a separate IANA-maintained module, like iana-if-type >>in RFC 7224?" > >but you have not done that. You have produced a separate module in >which IANA appears hundreds of times but that does not make it an >IANA-maintained module IMO. Look at RFC7224 s.3 to see what I think is >missing. > >Tom Petch > > >----- Original Message ----- >From: "Acee Lindem (acee)" <a...@cisco.com> >Cc: <rtgwg@ietf.org> >Sent: Wednesday, May 10, 2017 10:54 PM >Subject: Re: I-D Action: draft-ietf-rtgwg-routing-types-03.txt > > >> This version addresses Stewart’s RTG Directorate comments and Radek’s >YANG >> Doctor comments. It also splits iana-routing-types into a separate >module. >> >> Thanks, >> Acee >> >> On 5/10/17, 5:47 PM, "rtgwg on behalf of internet-dra...@ietf.org" >> <rtgwg-boun...@ietf.org on behalf of 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 Routing Area Working Group of the >IETF. >> > >> > Title : Routing Area Common YANG Data Types >> > Authors : Xufeng Liu >> > Yingzhen Qu >> > Acee Lindem >> > Christian Hopps >> > Lou Berger >> > Filename : draft-ietf-rtgwg-routing-types-03.txt >> > Pages : 32 >> > Date : 2017-05-10 >> > >> >Abstract: >> > This document defines a collection of common data types using the >> > YANG data modeling language. These derived common types are >designed >> > to be imported by other modules defined in the routing area. >> > >> > >> >The IETF datatracker status page for this draft is: >> >https://datatracker.ietf.org/doc/draft-ietf-rtgwg-routing-types/ >> > >> >There are also htmlized versions available at: >> >https://tools.ietf.org/html/draft-ietf-rtgwg-routing-types-03 >> >>https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-routing-types-03 >> > >> >A diff from the previous version is available at: >> >https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-routing-types-03 >> > >> > >> >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. >> > >> >Internet-Drafts are also available by anonymous FTP at: >> >ftp://ftp.ietf.org/internet-drafts/ >> > >> >_______________________________________________ >> >rtgwg mailing list >> >rtgwg@ietf.org >> >https://www.ietf.org/mailman/listinfo/rtgwg >> >> _______________________________________________ >> rtgwg mailing list >> rtgwg@ietf.org >> https://www.ietf.org/mailman/listinfo/rtgwg >> > _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg
