Andy Bierman wrote:
> On Mon, Apr 30, 2018 at 7:09 AM, Ladislav Lhotka wrote:
>
> > Andy Bierman writes:
> >
> > > On Fri, Apr 27, 2018 at 8:13 AM, Ladislav Lhotka wrote:
> > >
> > >> On Fri, 2018-04-27 at 16:47 +0200,
Kent Watsen wrote:
>
> Lada writes:
> > Andy writes:
> >>IMO, the yang-data defined in RFC 8040 has a clear purpose, and it
> >>is sufficient for that purpose, which is a YANG representation of
> >>an instance document (such as a protocol message or file).
> >
> > The same
On Wed, 2018-05-02 at 09:16 +0200, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > On Fri, 2018-04-27 at 12:19 +0100, Robert Wilton wrote:
> > >
> > > On 27/04/2018 12:03, Ladislav Lhotka wrote:
> > > > On Fri, 2018-04-27 at 11:23 +0100, Robert Wilton wrote:
> > > > > On
On Wed, 2018-05-02 at 11:36 +0200, Juergen Schoenwaelder wrote:
> On Wed, May 02, 2018 at 11:25:06AM +0200, Martin Bjorklund wrote:
> >
> > The primary use case is not "generic RPC messages", but standalone
> > instance documents, error-info structures, etc.
> >
> > > This doesn't seem to be a
Hi Juergen,
Some thoughts in-lined.
With Regards,
Rohit R Ranade
-Original Message-
From: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
Sent: 25 April 2018 16:12
To: Rohit R Ranade
Cc: netc...@ietf.org; netmod@ietf.org
Subject: Re:
On Wed, May 02, 2018 at 11:25:06AM +0200, Martin Bjorklund wrote:
>
> The primary use case is not "generic RPC messages", but standalone
> instance documents, error-info structures, etc.
>
> > This doesn't seem to be a fundamental change in YANG's scope, or
> > architecture.
The proper solution
Ladislav Lhotka wrote:
> On Wed, 2018-05-02 at 09:16 +0200, Martin Bjorklund wrote:
> > Ladislav Lhotka wrote:
> > > On Fri, 2018-04-27 at 12:19 +0100, Robert Wilton wrote:
> > > >
> > > > On 27/04/2018 12:03, Ladislav Lhotka wrote:
> > > > > On Fri, 2018-04-27 at
On 02/05/2018 08:25, Martin Bjorklund wrote:
Andy Bierman wrote:
On Mon, Apr 30, 2018 at 7:09 AM, Ladislav Lhotka wrote:
Andy Bierman writes:
On Fri, Apr 27, 2018 at 8:13 AM, Ladislav Lhotka wrote:
On Fri,
Robert Wilton wrote:
>
>
> On 02/05/2018 08:25, Martin Bjorklund wrote:
> > Andy Bierman wrote:
> >> On Mon, Apr 30, 2018 at 7:09 AM, Ladislav Lhotka
> >> wrote:
> >>
> >>> Andy Bierman writes:
> >>>
> On Fri, Apr
On Wed, May 02, 2018 at 11:28:42AM +, Rohit R Ranade wrote:
> Hi Juergen,
>
> Some thoughts in-lined.
>
> With Regards,
> Rohit R Ranade
>
> -Original Message-
> From: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
> Sent: 25 April 2018 16:12
> To: Rohit R
Hi all,
I've seen some older threads about 'when' handling and they ended up creating a
lot of debate about behavior & intentions (and about how well the text is
written in the specs).
I'm hoping that the community out there is in agreement on yes vs no for the
questions below.
Given the
Hi,
The discussion about yang-data is stuck because the NETMOD WG does not
understand or does not agree on what it means to abuse a YANG extension
and use it improperly.
If a tool implementing a standard cannot do so without implementing
certain extensions, then those extensions are not
Hi Kent,
No, I'm not aware of any IPR that applies to this draft.
Regards,
Lisa
On Tue, May 1, 2018 at 1:03 PM, Kent Watsen wrote:
> Thank you, Mahesh and Sonal.
>
> I'm still waiting to hear from Lisa and Dana. Neither have been heard
> from since the pen moved a
13 matches
Mail list logo