Hi Benoit,

Benoit Claise <bcla...@cisco.com> writes:

> Dear all,
>
> As a contributor, I browsed through draft-ietf-netmod-yang-metadata

Thanks.

>ay
> -
>         The set of annotations must be extensible in a distributed manner
>         so as to allow for defining new annotations without running into
>         the risk of collisions with annotations defined and used by
>         others.
>
> What does "in a distributed manner" mean?

It means that different parties needn't coordinate the names and use of
annotations, as long as they don't choose conflicting YANG module names
or namespace URIs.

>
>
>
> - In the introduction, you mention:
>     Typical use cases are:
>
>     o  Deactivating a subtree in a configuration datastore while keeping
>        the data in place.
>
>     o  Complementing data model information with instance-specific data.
>
>     o  RPC operations may use metadata annotations for various purposes
>        in both requests and responses.  For example, the <edit-config>
>        operation in the NETCONF protocol (seesection 7.2 of [RFC6241] 
> <https://tools.ietf.org/html/rfc6241#section-7.2>)
>        uses annotations in the form of XML attributes for identifying the
>        point in the configuration and type of the operation.
>
>
> Don't you have any other examples than those 3?
> What about showing these examples with the spec. in this document?
> Note: I see that the first one is documented with module
> example-inactive

Well, the backlash I received with
draft-lhotka-netmod-yang-annotations-00 (expired) show that whilst there
is consensus about general utility of annotations, practical definitions
may be controversial. I could add the annotations from the above draft
as examples here but I fear they could still make for unnecessary
discussions.

Martin already pointed out in his review that it may be wiser to replace
the "inactive" annotation with something less controversial.

>
>
> - Please correct the IANA considerations as in RFC7277, in particular the 
> Registrant Contact:
>     This document registers a URI in the "IETF XML Registry" [RFC3688 
> <https://tools.ietf.org/html/rfc3688>].
>     Following the format inRFC 3688 <https://tools.ietf.org/html/rfc3688>, 
> the following registration has been
>     made.
>
>         URI: urn:ietf:params:xml:ns:yang:ietf-ip
>
>         Registrant Contact: The NETMOD WG of the IETF.
>
>         XML: N/A; the requested URI is an XML namespace.

OK, will do.

Thanks, Lada

>
> Regards, Benoit
>>
>> All,
>>
>> Today is the cutoff date for the Last Call for this draft, but the 
>> author indicated that comments received today or tomorrow can be 
>> incorporated into the draft-update being worked on.  So, if you have 
>> any lingering reviews, please send them before as soon as possible.
>>
>> Thanks!
>> Kent
>>
>>
>>
>> From: Kent Watsen <kwat...@juniper.net <mailto:kwat...@juniper.net>>
>> Date: Monday, June 15, 2015 at 6:49 PM
>> To: "netmod@ietf.org <mailto:netmod@ietf.org>" <netmod@ietf.org 
>> <mailto:netmod@ietf.org>>
>> Subject: [netmod] WG Last Call for draft-ietf-netmod-yang-metadata-01 
>> (until 2015-06-29)
>>
>>
>> This is a notice to start a NETMOD WG last call for the document 
>> "Defining and Using Metadata with YANG":
>>
>> https://tools.ietf.org/html/draft-ietf-netmod-yang-metadata-01
>>
>> Please indicate your support by Monday June 29, 2015 at 9PM EST.
>> We are not only interested in receiving defect reports, we are equally
>> interested in statements of the form:
>>
>>   "I have reviewed I-D XYZ and I found no issues"
>>   "I have implemented the data model in I-D XYZ"
>>   "I am implementing the data model in I-D XYZ"
>>   "I am considering to implement the data model in I-D XYZ"
>>
>> This is the first Last Call for this document.
>>
>> Kent, as NETMOD co-chair
>>
>>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to