Re: Yangdoctors last call review of draft-ietf-bfd-rfc9127-bis-01

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 03 February 2022 17:29 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 AE6EB3A1141; Thu, 3 Feb 2022 09:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 n2E4l4C04B0q; Thu, 3 Feb 2022 09:29:06 -0800 (PST)
Received: from mail-oo1-xc2c.google.com (mail-oo1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (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 CB4A53A1159; Thu, 3 Feb 2022 09:29:02 -0800 (PST)
Received: by mail-oo1-xc2c.google.com with SMTP id o192-20020a4a2cc9000000b00300af40d795so2059085ooo.13; Thu, 03 Feb 2022 09:29:02 -0800 (PST)
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=UZ3NooTbzMtbaf4jiMgCK0gQ005zswGOxDab6g6lbVA=; b=huUf8jygQ6P6aWTEjz85HzwkZz37v1RhZP87t8c/Wy6a2ZYY8rJGcqJHX7K0aWCj+c Ug/Sp/fPtSyl+3F4c/OO+QNeloxLhu4J3eCC/FUR5EHrqQ2ZgwcMZrp6yraeGjL8toir WB4tLEwSfAZYO9RHi2sTYhOAkIL4pdhwEcIRH4n10Y9pTKznfVeOYrm0J/IDfXZQe3Fp qU80lm0wnjzMcT2XGpUT6W+ABLDeMbFOLwFmyYTapDLNBNDsp9Ln/KB3sV4OMh1LmjJE Qq8QhIfyiv2LLXUQtQ2Oo4Hmg4p6tvDBKRKhbet4eY/N5Ja6AcS3d6yBRb19+iTgJ+yO TF4Q==
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=UZ3NooTbzMtbaf4jiMgCK0gQ005zswGOxDab6g6lbVA=; b=C5bnhGoTq0pugTS7vDA4gkaL9KlyPtA5OAVrZXN5c2RwH+isgpNjd0Xq16fQ7CciAw 6OgLfBx16RcTNMu0LH0mS/nhFWV8hY06bPwI2Vc6L+fgdF8ioCilTEtexixQpUGx4rui ExA1TSioFSgK3/KjVF3KY0I9rsNmeDF7De3s9MmVvRVU3CXEGMKNSI0FJrMCrgeegEHj ZD5lBN7cFeZ6NJlmHp8xMRoaaAugjwXXnbS8HsBR3ukB3Xn3kWXtlBlcBfsVaiOCZZbk /cIPhaewb2x0E/ab6TZXFxF0qUZE2O7nw8oxSyo50f6HQLDMFtAtQ2vwjveQJwrIBCpk X00g==
X-Gm-Message-State: AOAM531+FQ+RNzAarrrt5uym5LV2xHyi3u1FmiOjAZI5n0/zrgVqC6CC jtP/Mmi6IAFuh4wDNxOwCk0d6zjk+Qc=
X-Google-Smtp-Source: ABdhPJwXrPHGiHq+s4wCrTRv16ffzr4WUmdAQNwGQaDz3L17Jod3cQLXX+wqhaU3c2eT1Cf4UpAcFA==
X-Received: by 2002:a05:6870:3a32:: with SMTP id du50mr389802oab.80.1643909340960; Thu, 03 Feb 2022 09:29:00 -0800 (PST)
Received: from smtpclient.apple (adsl-70-234-233-187.dsl.rcsntx.sbcglobal.net. [70.234.233.187]) by smtp.gmail.com with ESMTPSA id p21sm18752817oov.2.2022.02.03.09.28.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Feb 2022 09:29:00 -0800 (PST)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <E68495BC-E0D3-4192-9C7F-C4E6F1EF8E9A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3916ABC0-8E4D-4657-8255-1F35511E29A5"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: Yangdoctors last call review of draft-ietf-bfd-rfc9127-bis-01
Date: Thu, 03 Feb 2022 09:28:59 -0800
In-Reply-To: <164388736861.32491.11649774516476095771@ietfa.amsl.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, draft-ietf-bfd-rfc9127-bis.all@ietf.org, last-call@ietf.org, "rtg-bfd@ietf. org" <rtg-bfd@ietf.org>
To: Jan Lindblad <janl@tail-f.com>
References: <164388736861.32491.11649774516476095771@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/eZ38Owhv5m_b-LwZjvSOcKIyJPQ>
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: Thu, 03 Feb 2022 17:29:20 -0000

Hi Jan,

Thanks first of all for the review.

> On Feb 3, 2022, at 3:22 AM, Jan Lindblad via Datatracker <noreply@ietf.org> wrote:
> 
> Reviewer: Jan Lindblad
> Review result: Ready with Issues
> 
> This is the last call YANG Doctor review of draft-ietf-bfd-rfc9127-bis.
> Browsing the mail archives, this has been a long story. Realizing that the
> context of the bis is to fix a particular issue, I have focused only on the
> diffs from RFC 9127. I feel any additional nitpicks I might find in a complete
> review would not be welcome at this stage.
> 
> I have reviewed the diffs, and find them fulfill the desired technical goals.
> Since this update breaks backwards compatibility as defined in RFC 6020 sec 10
> and RFC 7950 sec 11, the process for approving this change has been discussed
> at length. One argument that has been put forward for going ahead is that the
> previous version of this module was released only a short time ago, so there is
> no proliferation of impacted systems in the field.
> 
> Another argument has been that the YANG Versioning Design Team is working on
> updated backwards compatibility rules. The Ver-DT proposed updates to the
> compatibility rules would indeed allow a change of this kind under certain
> conditions. A key condition for allowing such a break with the backwards
> compatibility is that the module revision history announces this break clearly
> to all readers. This is not the case in the -01 version of the modules.
> 
>   revision 2022-01-04 {
>       description
>         "Updates to add client configuration parameters feature.";
> 
> In my YANG Doctor opinion, updating the revision statement to clearly state
> that this version is not backwards compatible with the previous version is an
> absolute requirement. I think it would also be fair to module readers to add a
> few sentences explaining what's going on here.

How does this sound?

OLD:
      "Updates to add client configuration parameters feature.";

NEW:
      "Updates to add client configuration parameters feature.
       This update breaks backward compatability with earlier
       version of the model. The new feature prevents up to 
       three client configuration parameters from being
       included, where they were not needed.";


Thanks.


Mahesh Jethanandani
mjethanandani@gmail.com