Re: Francesca Palombini's Discuss on draft-ietf-bfd-rfc9127-bis-02: (with DISCUSS and COMMENT)

Mahesh Jethanandani <mjethanandani@gmail.com> Wed, 06 April 2022 18:08 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1513A0D79; Wed, 6 Apr 2022 11:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJ5eWjyFDHv4; Wed, 6 Apr 2022 11:08:08 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A97F3A0D71; Wed, 6 Apr 2022 11:08:08 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id j21so5891572qta.0; Wed, 06 Apr 2022 11:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=tucQMVeyfTpqJlHhlSTYc0yPP6C7BBibibaYBOdRvq4=; b=UkIuuYcu9OsMGrQ2ihoVJODJ0SAL9w6+dmfr9rJfbEsP4vlSJo4Ksy2tTk+s3FF/i4 74YgoYxY7SyI5WHDaZ0JbqdyAeYFaC8Ya7nVkuL4Mc86O70Q9yWgTtYYaQNhFh+bcbaW J1y73Sv5ObxgmSM3dFTYEjKnDZO6fGg8H6XLJPTy20AoIp/MfvGDDsQa51eYdMMO4//J 1ZetMzg78wzP2TeO/QBFXOh0FdkjEGvYlXFRh/B2Z3XuOpAgBZ/Gi2m7j5BtLTIFapqG J+oLU1nYe7hR2zebCijtTK0QsT333Ltwmdtf0svmWpfYgBJ2OLI57TqD//S38btfKRSY kKCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=tucQMVeyfTpqJlHhlSTYc0yPP6C7BBibibaYBOdRvq4=; b=JDnrzB2Pj2NCKRxdVlQ5DOBi4oHgC2YC0V0PhJv2coK8oh/VYIAtMM8IR/j9ZN7f5l JshWJgzX73O+wJXgFsA3Qn2LlTtlv20g2ijjSJynEZlNs2eiqha2d6kFAMPq4L/o0/R1 hhn13hufgHwCM1FYeq8QHuCCjjEuZwuIKXe1ZmCGwlzV2mrRl6gBjynceemMxv3VqlTs LHagt0m1+HthAQERFe78jqPD9sXwaE+P83jK0j2rYS9E0dbP+WDD/VML+4qsJeVaQrgV v6YeeaA6ug/c/KYRyii1JuInjxaI2ijYdnvUoEv1jv1B18PswzHP24u2M5JlqxiVrN/v 8y0Q==
X-Gm-Message-State: AOAM530pkpD7hhTThyHZRlT1WcmjOipmM4EorZBeicxMCkRfpdOK4Ycr 6MGgLVRmrF8ZbZEfA2O58IzJlLsUne/KBQ==
X-Google-Smtp-Source: ABdhPJwZzHMrP35BOxMAxi3qg5BWbidd61AiGTGVGp+gWvX6lonNirtVpIk4Rz/QtO7XOZwNRW8pdw==
X-Received: by 2002:a37:a52:0:b0:67b:3225:4aaa with SMTP id 79-20020a370a52000000b0067b32254aaamr6338643qkk.525.1649268486625; Wed, 06 Apr 2022 11:08:06 -0700 (PDT)
Received: from smtpclient.apple (adsl-70-234-233-187.dsl.rcsntx.sbcglobal.net. [70.234.233.187]) by smtp.gmail.com with ESMTPSA id t3-20020a05620a0b0300b00699c6a9b2d1sm5580240qkg.32.2022.04.06.11.08.05 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Apr 2022 11:08:06 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <BC63A60E-8A72-4166-8D39-5D0CDEE63FA5@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FC49B56B-69C4-4F8E-BBF4-E4F7DD187A9D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: Francesca Palombini's Discuss on draft-ietf-bfd-rfc9127-bis-02: (with DISCUSS and COMMENT)
Date: Wed, 06 Apr 2022 11:08:04 -0700
In-Reply-To: <164925535261.10923.737216833603993234@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-bfd-rfc9127-bis@ietf.org, bfd-chairs@ietf.org, "rtg-bfd@ietf. org" <rtg-bfd@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>
To: Francesca Palombini <francesca.palombini@ericsson.com>
References: <164925535261.10923.737216833603993234@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/S53OW52xgZefSl6ZCMEJBzs8R0M>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2022 18:08:12 -0000

Hi Francesca,

Thank you for the review. Please inline for the responses.

> On Apr 6, 2022, at 7:29 AM, Francesca Palombini via Datatracker <noreply@ietf.org> wrote:
> 
> Francesca Palombini has entered the following ballot position for
> draft-ietf-bfd-rfc9127-bis-02: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-bfd-rfc9127-bis/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Thank you for the work on this document.
> 
> I have noticed one easy to fix error in the examples, and I additionally have
> two comments I'd like to talk about before the document is approved - these are
> non blocking, but answers are appreciated.
> 
> Thanks,
> Francesca
> 
> 1. -----
> 
>   In this case, an interface named "Bundle-Ether1" of interface type
>   "ieee8023adLag" has a desired transmit interval and required receive
>   interval set to 10 ms.
> 
> FP: But the example actually uses intervals of 100ms:
> 
>                   <desired-min-tx-interval>
>                     100000
>                   </desired-min-tx-interval>
>                   <required-min-rx-interval>
>                     100000
>                   </required-min-rx-interval>

Fixed. Will be published as part of the next update.

> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> 
> 2. -----
> 
>        This version of this YANG module is part of RFC 9127; see the
>        RFC itself for full legal notices.";
> 
> FP: Just double checking as I am not sure about what's common for new revisions
> of existing modules - Should it be this RFC number, rather than or additionally
> to 9127? (several occurrences in the doc)

Good catch. The new revision should refer to this RFC number (XXXX), while maintaining the older revision (2021-10-21) for RFC 9127. Will update.

> 
> 3. -----
> 
> Section 2.1.1.
> 
> FP: I was expecting to see some text about expected behavior if both
> "min-interval" and any of the other interval parameters are (incorrectly) used
> at the same time. I expect a value should be discarded, which one? Also, maybe
> a bit of a late comment and I will leave it to the authors and wg to decide if
> including it is worth it, in Section 3 it would have been useful to see one
> example using the "min-interval".

The min-interval and other other interval parameters (desired-min-tx-interval and required-min-rx-interval) are a choice statement. You get to either select the min-interval or the other two interval values.

Thanks.

> 
> 
> 


Mahesh Jethanandani
mjethanandani@gmail.com