Re: [netmod] AD review of draft-ietf-netmod-rfc6021-bis-00.txt

[Benoit Claise <[e-mail]>]

Hi Juergen,

Please publish a new version, and the WG agrees on the solution.

Regards, Benoit
> Benoit,
>
> do you prefer to get a revised module before you do the IETF last call
> or do you just want the editors to track those changes and we post a
> revision at some later point during the process?
>
> /js
>
> On Fri, Mar 22, 2013 at 06:24:57PM +0100, Benoit Claise wrote:
>> Juergen, NETMOD participants,
>>
>> Two comments
>>
>> 1.
>> For the ip-address-no-zone, ipv4-address-no-zone, and
>> ipv6-address-no-zone, don't you need a reference to the zone
>> information in the description?
>>
>>       description
>>          "The ip-address-no-zone type represents an IP address without
>>           zone information in an IP version neutral way.  The format
>>           of the textual representations implies the IP version.";
>>
>> Doesn't give me a pointer to what a zone information is. So I don't
>> know what ip-address-no-zone is.
>> Note: I faced the zone issue only a year ago. Before that, I had no
>> clue what it was.
>>
>>
>> 2.
>> The section "Appendix A. Changes from RFC 6021" is pretty light:
>>
>>       This version adds new type definitions to the YANG modules. For
>>     the further details, see the revision statement of the YANG modules.
>>
>> Take it or leave it. However, I can tell that its resolution will
>> please some IESG members, specifically because the rfcdiff tool
>> doesn't do a good job of comparing RFC6021 with
>> draft-ietf-netmod-rfc6021-bis-00.txt
>>
>> Proposal
>>
>>       This version adds new type definitions to the YANG modules. The
>>     first YANG module, ietf-yang-types adds the following new data
>>     types: yang-identifier, hex-string, uuid, and dotted-quad. The
>>     second YANG module, ietf-inet-types, adds the following new data
>>     types: ip-address-no-zone, ipv4-address-no-zone, and
>>     ipv6-address-no-zone.
>>
>> Regards, Benoit (OPS AD)