Presumably you will have to decide on a sensible default value to use.
What value will your actual device use after the software upgrade? That should
be the value it stores in the data tree when performing the upgrade.
From: netmod
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Modeling WG of the IETF.
Title : YANG Data Extensions
Authors : Andy Bierman
Martin Bjorklund
Bob,
I will add your wording in the next revision.
Thanks,
Clyde
From: Bob Harold
Date: Monday, March 5, 2018 at 11:06 AM
To: Clyde Wildes
Cc: "netmod@ietf.org"
Subject: Re: [netmod] draft-ietf-netmod-syslog-model-23
On Fri, Mar 2,
On Fri, Mar 2, 2018 at 5:13 PM, Clyde Wildes (cwildes)
wrote:
> Bob,
>
>
>
> Syslog message severity is set in RFC 5424 Table 2. The model in
> draft-ietf-netmod-syslog-model-23 conforms to that specification. A lower
> number means higher severity.
>
>
>
Thanks. Can we add
> On Mar 5, 2018, at 6:27 AM, Martin Bjorklund wrote:
>
> Martin Bjorklund > wrote:
>> Juergen Schoenwaelder wrote:
>>> On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin Bjorklund wrote:
>
On 2018-03-05 16:06, Ladislav Lhotka wrote:
> On Mon, 2018-03-05 at 15:49 +0100, Per Hedeland wrote:
>> On 2018-03-05 15:41, Ladislav Lhotka wrote:
>>> On Mon, 2018-03-05 at 15:26 +0100, Martin Bjorklund wrote:
Juergen Schoenwaelder wrote:
> On Mon,
On Mon, 2018-03-05 at 15:49 +0100, Per Hedeland wrote:
> On 2018-03-05 15:41, Ladislav Lhotka wrote:
> > On Mon, 2018-03-05 at 15:26 +0100, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > > On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin
On 2018-03-05 15:41, Ladislav Lhotka wrote:
> On Mon, 2018-03-05 at 15:26 +0100, Martin Bjorklund wrote:
>> Juergen Schoenwaelder wrote:
>>> On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin Bjorklund wrote:
>
> So it seems the running code got it
On Mon, 2018-03-05 at 15:26 +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin Bjorklund wrote:
> > > >
> > > > So it seems the running code got it right. ;-)
> > >
> > > As the author of that
Juergen Schoenwaelder wrote:
> On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin Bjorklund wrote:
> > >
> > > So it seems the running code got it right. ;-)
> >
> > As the author of that code, I think that was purely by accident...
> >
> > But I'm not
On 03/05/2018 02:54 PM, Martin Bjorklund wrote:
Juergen Schoenwaelder wrote:
On Mon, Mar 05, 2018 at 02:14:26PM +0100, Vladimir Vassilev wrote:
On 03/05/2018 01:50 PM, Juergen Schoenwaelder wrote:
I prefer that the choice/case nodes do not have any
On Mon, Mar 05, 2018 at 02:54:18PM +0100, Martin Bjorklund wrote:
> >
> > So it seems the running code got it right. ;-)
>
> As the author of that code, I think that was purely by accident...
>
> But I'm not convinced it is the correct solution. We have one example
> in the other thread where
The following errata report has been verified for RFC7950,
"The YANG 1.1 Data Modeling Language".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5274
--
Status: Verified
Type: Technical
Juergen Schoenwaelder wrote:
> On Mon, Mar 05, 2018 at 02:14:26PM +0100, Vladimir Vassilev wrote:
> > On 03/05/2018 01:50 PM, Juergen Schoenwaelder wrote:
> >
> > > I prefer that the choice/case nodes do not have any flags since they
> > > are not having a
On Mon, Mar 05, 2018 at 02:14:26PM +0100, Vladimir Vassilev wrote:
> On 03/05/2018 01:50 PM, Juergen Schoenwaelder wrote:
>
> > I prefer that the choice/case nodes do not have any flags since they
> > are not having a config true/false property on their own. And less
> > clutter is better.
>
>
Hi,
This errata is correct and should be accepted.
I think the actual URI to use is less important, so the proposed URI
is fine.
/martin
RFC Errata System wrote:
> The following errata report has been submitted for RFC7950,
> "The YANG 1.1 Data Modeling Language".
On 03/05/2018 01:50 PM, Juergen Schoenwaelder wrote:
I prefer that the choice/case nodes do not have any flags since they
are not having a config true/false property on their own. And less
clutter is better.
'choice' statements have 'config' substatement while 'case' do not. I
myself figured
I prefer that the choice/case nodes do not have any flags since they
are not having a config true/false property on their own. And less
clutter is better.
/js
On Mon, Mar 05, 2018 at 12:26:27PM +0100, Martin Bjorklund wrote:
> Hi,
>
> Lifting this issue to its own thread.
>
> With this
Hi,
Lifting this issue to its own thread.
With this snippet:
choice subnet {
case prefix-length {
leaf prefix-length {
type uint8;
}
}
case netmask {
leaf netmask {
type yang:dotted-quad;
}
}
}
pyang prints
Hi,
We have a question with respect to YANG models using features. Assume that a
part of the model is defined under a feature and that this feature-dependent
part defines a leaf as mandatory.
module servers {
namespace "http://www.example.com/servers;;
prefix servers;
import
20 matches
Mail list logo