[+netconf, since this discussion regards a netconf draft]
> But possibly a useful discussion to have may be what the members of the
> NETCONF WG perceives is the future for the IETF network management
> protocols.
I'm an advocate for RESTCONF being as capable as NETCONF, and perhaps
more capabl
On 09/05/2018 17:47, Juergen Schoenwaelder wrote:
On Wed, May 09, 2018 at 05:15:12PM +0100, Robert Wilton wrote:
+1 for a generic solution.
At the moment RFC 8040 states that ETAGS only apply to configuration, so
they don't necessarily help with operational data.
Perhaps we should be introdu
On Wed, May 09, 2018 at 05:15:12PM +0100, Robert Wilton wrote:
>
> At the moment RFC 8040 states that ETAGS only apply to configuration, so
> they don't necessarily help with operational data.
>
Do you refer to this:
The server MUST maintain an entity-tag for the top-level
{+restconf}/data
On Wed, May 09, 2018 at 05:15:12PM +0100, Robert Wilton wrote:
> +1 for a generic solution.
>
> At the moment RFC 8040 states that ETAGS only apply to configuration, so
> they don't necessarily help with operational data.
>
> Perhaps we should be introducing something like ETAG support for operat
Hi Juergen,
On 09/05/2018 10:53, Juergen Schoenwaelder wrote:
On Wed, May 09, 2018 at 09:12:12AM +, Rohit R Ranade wrote:
On Wed, May 09, 2018 at 02:31:15AM +, Rohit R Ranade wrote:
Hi All,
1. "import-only-module" is currently under the "module-set" list. How
does the client
On Wed, May 09, 2018 at 09:12:12AM +, Rohit R Ranade wrote:
> On Wed, May 09, 2018 at 02:31:15AM +, Rohit R Ranade wrote:
> > Hi All,
> >
> >
> > 1. "import-only-module" is currently under the "module-set" list. How
> > does the client benefit by learning which module-set imports w
On Wed, May 09, 2018 at 02:31:15AM +, Rohit R Ranade wrote:
> Hi All,
>
>
> 1. "import-only-module" is currently under the "module-set" list. How
> does the client benefit by learning which module-set imports which modules ?
All non import-only modules of the schema are
On Wed, May 09, 2018 at 02:31:15AM +, Rohit R Ranade wrote:
> Hi All,
>
>
> 1. "import-only-module" is currently under the "module-set" list. How
> does the client benefit by learning which module-set imports which modules ?
All non import-only modules of the schema are
On Wed, May 09, 2018 at 05:45:46AM +, Rohit R Ranade wrote:
> Hi All,
>
> Continuing with the below queries.
>
> 5. For a module like "ietf-netconf-notifications", which implements only
> notifications. I think this module is not suitable to be put in any of the
> data-stores. So a separat
To: netmod@ietf.org
Subject: [netmod] Query about draft-ietf-netconf-rfc7895bis-06
Hi All,
1. "import-only-module" is currently under the "module-set" list. How
does the client benefit by learning which module-set imports which modules ?
2. Whether we can keep
Hi All,
1. "import-only-module" is currently under the "module-set" list. How
does the client benefit by learning which module-set imports which modules ?
2. Whether we can keep the "import-only-module" as a sibling to
module-set. And let it list all the imported modules.
3. Sect
11 matches
Mail list logo
