Subject: Re: [Teas] I-D Action: draft-ietf-teas-yang-rsvp-16.txt refresh reduction

From: t petch <[email-masked]>
Date: Mon, 9 Aug 2021 12:09:49 +0100

Looking at the coverage of refresh reduction, I struggle.  For the most
part this I-D uses different terminology to the referenced RFC2961 and
in places I cannot bridge the gap. The I-D talks of ACK messages, the
RFC has  MESSAGE_ID_ACK .  Bundle is ok but reliable-ack and
reliable-retransmit I am uncertain about; the RFC has refresh and
srefresh.  (I think that 'leaf summary-max-size' would be better named
'leaf srefresh-max-size' if that is what it is).

The RFC has
"When a node supports the periodic generation of
    standard refresh messages while Srefreshes are being used, the
    frequency of generation of standard refresh messages relative to the
    generation of summary refreshes SHOULD be configurable by the network
    administrator. "
which appears not to be included; perhaps worth a note to say that it
isn't.

The RFC has
   "Suggested default values are an initial retransmission timeout (Rf)
    of 500ms, a power of 2 exponential back-off (Delta = 1) and a retry
    limit (Rl) of 3."
which I do not see unless that is, in part,
        leaf reliable-retransmit-time {
          type uint32;
          units "milliseconds";
          default "50";

Of course, networks were somewhat different when the RFC was published
but since it is referenced, then I think that there should be a bridge
linking this I-D to it, even if the terminology, concepts, values and
such like are no longer used.

        leaf reliable-srefresh {
          type empty;
why empty as opposed to boolean or presence container for other srefresh
objects?

Tom Petch

> ----- Original Message -----
> From: "Tarek Saad" <tsaad=[email-masked]>
> To: <[email-masked]>; <[email-masked]>
> Sent: Friday, February 19, 2021 8:11 PM
> Subject: Re: [Teas] I-D Action: draft-ietf-teas-yang-rsvp-16.txt
>
>
> > This revision includes editorial updates as well as the addition of
> "Appendix A" for example instance data tree using this model.
> > With these changes, the authors believe I-D is ready to progress to
> WGLC.
> >
> > Tarek (for authors)
> >
> > ?On 2/19/21, 3:00 PM, "Teas on behalf of [email-masked]"
> <[email-masked] on behalf of [email-masked]> wrote:
> >
> >
> >     A New Internet-Draft is available from the on-line
Internet-Drafts
> directories.
> >     This draft is a work item of the Traffic Engineering
Architecture
> and Signaling WG of the IETF.
> >
> >             Title           : A YANG Data Model for Resource
> Reservation Protocol (RSVP)
> >             Authors         : Vishnu Pavan Beeram
> >                               Tarek Saad
> >                               Rakesh Gandhi
> >                               Xufeng Liu
> >                               Igor Bryskin
> >     Filename        : draft-ietf-teas-yang-rsvp-16.txt
> >     Pages           : 57
> >     Date            : 2021-02-19
> >
>