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
Hello Ferdi,
We have following text in section 3 of the draft:
A meter qualifies if the traffic arrival rate is based on agreed upon
rate and variability. A meter is generically modeled as qualifying
rate and variability defined as a token bucket. Single rate meter
On 01 Jul 2015, at 09:21, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 08:54:07AM +0200, Ladislav Lhotka wrote:
Juergen Schoenwaelder j.schoenwael...@jacobs-university.de writes:
On Tue, Jun 30, 2015 at 04:07:10PM +0200, Ladislav Lhotka
On Wed, Jul 1, 2015 at 6:01 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 01 Jul 2015, at 14:33, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 02:03:15PM +0200, Ladislav Lhotka wrote:
On 01 Jul 2015, at 09:21, Juergen Schoenwaelder
On 01 Jul 2015, at 14:33, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 02:03:15PM +0200, Ladislav Lhotka wrote:
On 01 Jul 2015, at 09:21, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 08:54:07AM
Hello Susan,
- Topology model which is a composite of:
o Generic topology model:
draft-ietf-i2rs-yang-network-topo-01https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/
o L3 topology model:
On Wed, Jul 01, 2015 at 02:03:15PM +0200, Ladislav Lhotka wrote:
On 01 Jul 2015, at 09:21, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 08:54:07AM +0200, Ladislav Lhotka wrote:
Juergen Schoenwaelder j.schoenwael...@jacobs-university.de
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
FYI,
There was discussion of IEEE/Ethernet models a while back. I wanted to
let everyone know that an initial one was just pushed.
https://github.com/YangModels/yang/tree/master/experimental/ieee
—Tom
___
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
Hi,
I am going to update the draft so the conformance leaf
is an enumeration with 'implement' and 'import' enums.
The 'none' enum is not needed because the deviations are
listed inside the module entry. A module server would return
the conformance for the proxied server, not itself.
No new
13 matches
Mail list logo
