>> I think it would be better to use a more generic term for rpc +
>> actions. Maybe operations:
>>
>>YANG is a data modeling language used to model configuration data,
>>state data, operations, and notifications for network management
>>protocols.
>
>I like 'operations' and the
On Wed, May 25, 2016 at 12:12:11PM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Mon, May 23, 2016 at 03:43:09PM +0200, Martin Bjorklund wrote:
> >
> > > wor...@ariadne.com (Dale R. Worley) wrote:
> > > >
> > > > - Abstract
> > > >
>
Ladislav Lhotka wrote:
>
> > On 24 May 2016, at 16:33, Dale R. Worley wrote:
> >
> > (I've not received some of the discussion e-mails, so I am just now
> > responding.)
> >
> > Ladislav Lhotka writes:
> >> This follows from the fact that
Martin Bjorklund writes:
>>
>>if-feature-expr = "(" if-feature-expr ")" /
>> if-feature-expr sep boolean-operator sep
>>if-feature-expr /
>> not-keyword sep if-feature-expr /
>>
Ladislav Lhotka wrote:
>
> > On 23 May 2016, at 15:43, Martin Bjorklund wrote:
> >
> >
> >> - section 3.1
> >>
> >> There is an overall question regarding whitespace in XML in
> >> "non-significant" places. Is it allowed in the XML representation of
> >> data
> On 23 May 2016, at 15:43, Martin Bjorklund wrote:
>
>
>> - section 3.1
>>
>> There is an overall question regarding whitespace in XML in
>> "non-significant" places. Is it allowed in the XML representation of
>> data trees? And if so, precisely what whitespace is allowed?
Hi,
Thank you for your thorough review! Comments inline.
wor...@ariadne.com (Dale R. Worley) wrote:
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please treat these