Alex Campbell writes:
Capabilities, features and deviations indicate the type of requests the router
can respond to.
The capability advertisement may not affect the router, but the capability
itself directly does.
The capability advertisement tells the client that the router can answer
> On Oct 25, 2018, at 06:12, Christian Hopps wrote:
>
> Hi Joel, WG,
>
> I published a new draft some days ago covering the specific concerns and
> editorial changes requested during WGLC. This included the addition of an
> extension statement which covered machine parsing of pre-defined
Hi Rob,
We've more privately discussed the bug-fix scenario and I'm sympathetic to it;
however, the requirement as written does not restrict itself to fixing module
definition bugs (e.g., a pattern or other value constraint) in some small but
incompatible way -- instead it's wide open and
On Thu, Oct 25, 2018 at 8:26 AM, Christian Hopps wrote:
>
>
> > On Oct 20, 2018, at 1:55 PM, Joe Clarke wrote:
> >
> > * New requirement 1.4 for supporting over-arching software releases
>
>
This text?
1.4 The solution MUST allow for modules to be versioned by
software
Hi Chris,
I think that there are two things driving this requirement:
What I regard as the key one, is that we want to be able to support the
software that we have shipped. In particular, we may need to fix bugs
(perhaps at the operators request) to a YANG model that has already been
Hi Joel, WG,
I published a new draft some days ago covering the specific concerns and
editorial changes requested during WGLC. This included the addition of an
extension statement which covered machine parsing of pre-defined tags which was
mentioned by multiple people, and is the only
Suupport
Scan the artwork for horizontal tab characters. If any horizontal
tab characters appear, either resolve them to space characters or
exit, forcing the input provider to convert them to space characters
themselves first.
Support this only more strongly, e.g. the general