On Fri, Jun 17, 2016 at 9:54 AM, The IESG wrote:
> The IESG has approved the following document:
> - 'The YANG 1.1 Data Modeling Language'
> (draft-ietf-netmod-rfc6020bis-14.txt) as Proposed Standard
>
> This document is the product of the NETCONF Data Modeling
Hi All
I'd like to support Option B below.
>> B) no explicit support is required for models to support
>>applied configuration -- and that the WG needs to
>>formalize an opstate solution based on the approach
>>discussed in [4] and [5].
Thanks
Kiran
>> All,
>>
>> We
On Fri, Jun 17, 2016 at 11:22 AM, Lou Berger wrote:
> Tom,
>
> Thanks for the perspective. I'm a little unsure if you're expecting
> a response or just making a statement, so if you're looking for
> something specific and don't see it below -- please let me know.
>
> On
Tom,
Thanks for the perspective. I'm a little unsure if you're expecting
a response or just making a statement, so if you're looking for
something specific and don't see it below -- please let me know.
On 6/17/2016 11:15 AM, t.petch wrote:
> Lou
>
> By now, 17th June, I see solid support
The IESG has approved the following document:
- 'The YANG 1.1 Data Modeling Language'
(draft-ietf-netmod-rfc6020bis-14.txt) as Proposed Standard
This document is the product of the NETCONF Data Modeling Language
Working Group.
The IESG contact persons are Benoit Claise and Joel Jaeggli.
A URL
Then this probably needs to be more clearly spelled out.
/js
On Fri, Jun 17, 2016 at 01:34:31PM +, Sterne, Jason (Nokia - CA) wrote:
> Hi Juergen,
>
> This model may be used in cases where no events are sent on any wire. Only
> events sent on a 'remote' log-action would need to conform to
Lou
By now, 17th June, I see solid support for one option but only see
comments from a somewhat small number of participants
The majority of the authors of the 172 YANG files I have in an
archive are probably unaware of this discussion and yet some at least
will be affected. What concerns me is
RFC 6020bis Section 9.7.2 is silent on the question of whether bit names can be
repeated in a bits value, e.g is “uno dos dos tres” valid or invalid? Obviously
repetition is not to be encouraged but is it forbidden? Maybe this is a case
where the robustness principle should be applied? Thanks,
Benoit,
Martin has posted revision -14 and I (in my role as document shepherd)
believe -14 addresses all comments that we received during the IESG
process. Please press any necessary buttons to continue the process.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the NETCONF Data Modeling Language of the IETF.
Title : The YANG 1.1 Data Modeling Language
Author : Martin Bjorklund
Filename:
On Thu, Jun 16, 2016 at 03:58:48PM +0200, Martin Bjorklund wrote:
> Anyway, I think my original proposed fix to this issue should work:
>
> OLD:
>
>o The context node is the node in the accessible tree for which the
> "must" statement is defined.
>
> NEW:
>
>o If the "must"
Ladislav Lhotka wrote:
>
> > On 16 Jun 2016, at 15:58, Martin Bjorklund wrote:
> >
> > Ladislav Lhotka wrote:
> >>
> >>> On 16 Jun 2016, at 15:12, Andy Bierman wrote:
> >>>
> >>>
> >>>
> >>> On Mon, Jun 13, 2016 at 8:30
In ietf-syslog-types, there is a mapping of facility names to a
limited number space on the wire. Unfortunately, this mapping is not
available in a machine readable form. But for those names listed in
RFC 5424, there is at least a mapping defined in human readable form
in the description clauses.
13 matches
Mail list logo