Subject: Re: [Netconf] server-model #47: introduce a 2nd timeout for periodic connections for when there's data to send?

From: Kent Watsen <[email-masked]>
Date: Mon, 18 May 2015 22:09:15 +0000

>>OLD:
>>
>>                  For messages the NETCONF server wants to send to
>>                  to the NETCONF client, the NETCONF server should
>>                  proactively connect to the NETCONF client, if
>>                  not already, to send the messages immediately.";
>>
>>NEW
>>
>>                  For messages the NETCONF server wants to send to
>>                  to the NETCONF client, the NETCONF server may
>>                  proactively connect to the NETCONF client, if
>>                  not already, to send its messages sooner than
>>                  its periodic timeout would have it do.";
>
>The English is broken.
>   s/, if not already,/ (if it is not already connected)/
>
>The English is awkward.
>   s/its periodic timeout would have it do/specified by its periodic
>timeout/
>
>Anthropomorphisms are annoying:
>   s/the NETCONF server wants to send/to be sent by the NETCONF server/

Taking Randy's comments into account, and trimming it down to a more
direct statement:

   For messages to be sent by the NETCONF server
   to the NETCONF client, the NETCONF server may
   proactively connect to the NETCONF client
   sooner than specified by its periodic timeout.

Kent