Re: [Netconf] closure on dynamic model changes

[Ariel Otilibili Anieli <[e-mail]>]

Hi Jeff, hi Kent,

Below some comments.

Regards,
Ariel

Quoting Kent Watsen <[e-mail]>:

> Hi Jeff,
>
> I'm not aware of such an error-app-tag.   I'm doubtful any such   
> support to exists as the official stance is that YANG modules are   
> forever backwards compatible (sans deviations).
If errors occur in the case you described, Kent, I would expect the  
base NETCONF protocol to raise them.
>
> Kent
>
>
> On 7/11/18, 5:58 PM, "Jeffrey Ladouceur (jladouce)"   
> <[e-mail]<mailto:[e-mail]>> wrote:
>
> Hi Kent,
>
> The client can receive notification and can poll the checksum to   
> determine if the module set has changed.
The name of that checksum is 'module-set-id'  
(https://tools.ietf.org/html/rfc7895#section-2.1.1). For example, this  
request,

<nc:rpc message-id="urn:uuid:11e17c21-1157-4d68-981f-5a3367a38ed0"  
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <nc:get>
     <nc:filter select="//module-set-id" type="xpath"/>
   </nc:get>
</nc:rpc>

Gives back,

<rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"  
message-id="urn:uuid:11e17c21-1157-4d68-981f-5a3367a38ed0"  
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   <data>
     <modules-state xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library">
       <module-set-id>326a180da22645fc532760d9d068e187</module-set-id>
     </modules-state>
   </data>
</rpc-reply>

>
> I?m also trying to determine if there was acceptance with regards to  
>  returning an error app tag of ?capabilities-changed? when a client   
> sends an RPC which could potentially no longer work as expected.
>
> Regards,
> Jeff
>
>
>
> From: Kent Watsen <[e-mail]>
> Date: Wednesday, July 11, 2018 at 5:48 PM
> To: Jeffrey Ladouceur <[e-mail]>, "[e-mail]"   
> <[e-mail]>
> Subject: Re: [Netconf] closure on dynamic model changes
>
> Hi Jeff,
>
> Both RFC 7895 and rfc7895bis (almost RFC 8407) define a checksum a   
> client can poll, as well as a notification a client can receive, to   
> determine when a server's module set has changed.
>
> Kent
>
>
> On 7/11/18, 5:34 PM, "Netconf on behalf of Jeffrey Ladouceur   
> (jladouce)"   
> <[e-mail]<mailto:[e-mail]> on behalf  
>  of   
> jladouce=[e-mail]<mailto:jladouce=[e-mail]>>   
> wrote:
>
> Hello netconf experts,
>
> I?m trying to determine if there was closure on the topic of dynamic  
>  model changes and the impact on any connected netconf clients.
>
> The last message appears to be 8 years ago:
>
> https://www.ietf.org/mail-archive/web/netconf/current/msg05982.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail-2Darchive_web_netconf_current_msg05982.html&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=Z5JgjQUnS4iOxPJ2YqJzFJTEW4Pyl-q8NHvml9iW0kc&s=YawnPBrkjAh6mZNBG8fY0VN0Rl8hqYwz_4uxbQc7zCE&e=>
>
> Has there been any standards agreement since the above post or any   
> other discussions ?
>
> Kindest regards,
> Jeff
>
>
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr