But don't get mw wrong, syntactically annotations would be allowed
everywhere although in some places they may be a no-op.
OK
This is also valid, see sec. 7.7.6 in RFC 6020:
snip/
I see, thanks.
True, I'd rather we can find a solution for annotating XML lists. Until
then, the draft
Kent Watsen kwat...@juniper.net writes:
Maybe I don't understand your response, but if we agree that annotations
are a server-level thing (not module-specific), then I do not agree
that a
module's description should be able to say that an annotation should be
ignored in other modules.
It
Kent Watsen kwat...@juniper.net writes:
1. In Section 3, it says:
snip/
Does this mean that the annotation A can be used by *any* module
the server advertises, or just the modules that define/import
annotation A?
For all modules implemented by the server, no import is needed.
Good,
Martin Bjorklund m...@tail-f.com writes:
Ladislav Lhotka lho...@nic.cz wrote:
On 01 Jul 2015, at 16:25, Benoit Claise bcla...@cisco.com wrote:
Hi Lada,
ay
-
The set of annotations must be extensible in a distributed manner
so as to allow for defining new
Benoit Claise bcla...@cisco.com writes:
Hi Lada,
- 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.
Maybe I don't understand your response, but if we agree that annotations
are a server-level thing (not module-specific), then I do not agree
that a
module's description should be able to say that an annotation should be
ignored in other modules.
It depends on the annotation's semantics, and
Hi Kent,
thanks for reviewing the document.
Kent Watsen kwat...@juniper.net writes:
[As an individual contributor]
Already many comments have been made, hopefully he below comments are new:
1. In Section 3, it says:
By advertising a YANG module in which metadata annotation A is
On 01 Jul 2015, at 16:25, Benoit Claise bcla...@cisco.com wrote:
Hi Lada,
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
On Wed, Jul 1, 2015 at 7:41 AM, Benoit Claise bcla...@cisco.com wrote:
Hi Lada,
- 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
1. In Section 3, it says:
snip/
Does this mean that the annotation A can be used by *any* module
the server advertises, or just the modules that define/import
annotation A?
For all modules implemented by the server, no import is needed.
Good, but I think the text should say this
Ladislav Lhotka lho...@nic.cz wrote:
On 01 Jul 2015, at 16:25, Benoit Claise bcla...@cisco.com wrote:
Hi Lada,
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
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
[mailto:netmod-boun...@ietf.org] On Behalf Of Kent Watsen
Sent: Monday, June 29, 2015 6:14 AM
To: netmod@ietf.org
Subject: Re: [netmod] WG Last Call for draft-ietf-netmod-yang-metadata-01
(until 2015-06-29)
All,
Today is the cutoff date for the Last Call for this draft, but the author
indicated
[As an individual contributor]
Already many comments have been made, hopefully he below comments are new:
1. In Section 3, it says:
By advertising a YANG module in which metadata annotation A is
defined using the md:annotation statement, a server specifies
support for the syntax of
From: Kent Watsen kwat...@juniper.netmailto:kwat...@juniper.net
Date: Monday, June 15, 2015 at 6:49 PM
To: netmod@ietf.orgmailto:netmod@ietf.org
netmod@ietf.orgmailto: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
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
On Mon, Jun 15, 2015 at 10:49:32PM +, Kent Watsen wrote:
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
On 17 Jun 2015, at 13:51, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jun 17, 2015 at 01:41:56PM +0200, Ladislav Lhotka wrote:
Well, but it is exactly what Kent objected against. It is the requirement to
support “old clients” that causes the trouble here
Ladislav Lhotka lho...@nic.cz wrote:
On 17 Jun 2015, at 12:12, Martin Bjorklund m...@tail-f.com wrote:
Ladislav Lhotka lho...@nic.cz wrote:
Hi Martin,
thanks for the review.
Martin Bjorklund m...@tail-f.com writes:
o Last paragraph of section 3 and the description in the
Hi Martin,
thanks for the review.
Martin Bjorklund m...@tail-f.com writes:
Hi,
I have reviewed this document, and here are my comments. I have some
technical issues; apart from that I think this document is ready
for publication.
I have also implemented this statement in pyang (see the
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
21 matches
Mail list logo
