On Tue, Oct 20, 2020 at 04:28:45PM +0200, Martin Björklund wrote:
> Hi,
>
> Ram Polisetty Subbaiah wrote:
> > Thanks Martin,
> >
> > One more follow up question:
> >
> > If in case both Client and Server are compatible only with Yang 1.0,
> > how client/server are supposed to
> > handle
Hi,
Ram Polisetty Subbaiah wrote:
> Thanks Martin,
>
> One more follow up question:
>
> If in case both Client and Server are compatible only with Yang 1.0,
> how client/server are supposed to
> handle capabilities advertisement for submodules? By any chance is it
> a limitation in 1.0?
If
Thanks Martin,
One more follow up question:
If in case both Client and Server are compatible only with Yang 1.0, how
client/server are supposed to
handle capabilities advertisement for submodules? By any chance is it a
limitation in 1.0?
Thanks,
Ram
On 20/10/20, 7:34 PM, "Martin Björklund"
Ram Polisetty Subbaiah wrote:
> Hi,
>
> As per RFC 6020:
>
> ===
> https://tools.ietf.org/html/rfc6020#section-5.6.4.1 Modules
>Servers indicate the names of supported modules via the
>message. Module namespaces are encoded as the base URI in the
>capability string, and the
Hi,
As per RFC 6020:
===
https://tools.ietf.org/html/rfc6020#section-5.6.4.1 Modules
Servers indicate the names of supported modules via the
message. Module namespaces are encoded as the base URI in the
capability string, and the module name is encoded as the "module"
parameter
