Re: [babel] info and data models -- feedback requested

That would suggest we should add a reset action for the packet log. We don’t currently have one.
Barbara

From: Donald Eastlake <d3e3e3@gmail.com>

Hi Mahesh and Barbara,

Speaking just as a WG member, it seems to me more flexible for the clearing of statistics and the enablement of statistics to be separate actions. You can always do both if that's wht you want.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com<mailto:d3e3e3@gmail.com>

On Fri, Jan 17, 2020 at 3:13 PM Mahesh Jethanandani <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>> wrote:

> On Jan 17, 2020, at 7:32 AM, STARK, BARBARA H <bs7652@att.com<mailto:bs7652@att.com>> wrote:
>
> There are 2 items related to the info/data models that have been swirling around in my head over the past month.
>
> 1. Since the most recent drafts of rfc6126bis now have 2 examples of initial interval settings (for cases where fast convergence is desired, or where slow convergence is acceptable and less chattiness is desired), I don't like that we have no means for the user to express what their preference is around this (in case an implementation could support both cases). Should we have something at the top level of the model like:
> boolean                rw converge-fast;
>
>   converge-fast:  Indicates whether the user wants the network to converge
>      quickly (which will cause Babel messages to be sent more frequently), or
>      prefers fewer Babel messages with slower time to convergence.  Fast
>      convergence is desired if "true". An implementation MAY choose to expose
>      this parameter as read-only ("ro").
>
> 2. In BBF, I got a comment related to babel-stats-enable and babel-packet-log-enable. It's unspecified as to whether previous data is discarded when the stats or log are enabled, or the new log entries are appended / existing counts incremented. I tend to agree that the lack of a statement will lead to inconsistency, and would prefer consistent behavior. Mahesh and I had a brief exchange where we disagreed on what the preferred behavior should be -- which suggests there is definitely a strong likelihood of different implementations choosing different behavior in the absence of guidance.

And to clarify the disagreement between Barbara and I was …

The Babel information and data models define a boolean flag that enables/disables the collection of statistics. The Babel data model in addition has an ‘action’ YANG statement defined to clear the statistics being collected. Barbara’s assumption with enabling the boolean flag was that it would implicitly clear all the statistics. But the data model with a separate ‘action’ statement requires it to be called explicitly to clear the statistics.

Unfortunately, there isn’t a way in YANG to invoke the calling of an ‘action’ statement when a certain attribute value toggles. Implementations can choose to make it implicit by including the call to the ‘action’ statement as part of enabling statistics. But it is not something YANG can enforce.

So the question is - should the information model require that enabling of statistics collection also clear the statistics (even if the YANG model cannot enforce it) or leave it to implementations to decide/enforce?

Cheers.

>
> I realize we're past last call. But I think these are important.
>
> Barbara
>
> _______________________________________________
> babel mailing list
> babel@ietf.org<mailto:babel@ietf.org>
> https://www.ietf.org/mailman/listinfo/babel<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_babel&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=Ervar6YVPnCewTWpMGUQdvrWDl--UTRIKVyMm-SEvF4&s=DhjYNDHNRPLsBhCPPje6e653wL9I_VCvgpjEGykc0aA&e=>

Mahesh Jethanandani
mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>

_______________________________________________
babel mailing list
babel@ietf.org<mailto:babel@ietf.org>
https://www.ietf.org/mailman/listinfo/babel<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_babel&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=Ervar6YVPnCewTWpMGUQdvrWDl--UTRIKVyMm-SEvF4&s=DhjYNDHNRPLsBhCPPje6e653wL9I_VCvgpjEGykc0aA&e=>