Re: New Version Notification for draft-acee-rtgwg-vrrp-rfc8347bis-03.txt

Yingzhen Qu <yingzhen.ietf@gmail.com> Sat, 02 March 2024 05:38 UTC

Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF21C14F6BA; Fri, 1 Mar 2024 21:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCPN_s3SY8-Y; Fri, 1 Mar 2024 21:38:47 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDD75C14F6B2; Fri, 1 Mar 2024 21:38:46 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2d29111272eso38731031fa.0; Fri, 01 Mar 2024 21:38:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709357925; x=1709962725; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dSqYHjvSCeemT6kSluoo9zKazVBHiQl92+qCUwyxSm4=; b=XQVh2RJvU5AwF7jlo5J4SxNnXdC3PJKfses7/bLOVjHOcT8bzMTW5MVg1ipoJb6y6q gw3btPYdsrEo8OB+GRHLFjwZywU9Fjser+mP4baHgp1RTm8kBi2+gzhAY7Z6wSyFO0eu D8c9Yp3gNvhVHSVWqL/meGmAoBnA7dxdttLlOWCuTBJFshFjqqtAVZNSUBw1vCuDr/By /6A6QTJnJT+Ymqi8AInEz1AorXj6MI+AyGpUA4LY1Ka4qGG3BLtF4v9BOj4t7O++C5EN ytb7fLLFt14ZS0lMMoPsY6iF7dp9uf3NIo8mPQtIn9rURiNqcVT8eHU/+sm00+FDM0cO nW5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709357925; x=1709962725; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dSqYHjvSCeemT6kSluoo9zKazVBHiQl92+qCUwyxSm4=; b=YCcvSfEp9Y/7Q9SKkKSCh72XkxQmLvqjF6272PY8lv+a6une0rkv3qEgt20EPOpInw rrOY01Q7k6CKW2xaGx5v0pKeBR2K97VZ9SnOnvRTlz4m2qGK1H8EZidBZe+z8Vr5l78H ZT1svDL6lTFpAfdWfteTZ5A0vXvM0OptHv5jVcaf3hpKkxG4seo+tuJgj5H4oY25c9lm SejjnmJNahWmuIJrIQsgWrZu+lEaCQKEKBSvQuLglP5gb16B6mh0QYC3XIz0/h/5f9F0 n/jnT7EhQkqdQ42QikAXRd59n4mmEvDj8Nl1oXvSr4F4NLZhewtHB5+Oyxqnv7czm8eD r03A==
X-Forwarded-Encrypted: i=1; AJvYcCVtY3Wrl0BfcLtNF3aFUJlWr2NjTBjcqepMRloj4Csgw1zaEi5OfVKAfmsleGdY3t1F/3chSPCXEXIVGyB7HO5i/nA8awKyOSi7HSg+VRgp
X-Gm-Message-State: AOJu0Yy0w4HFydHfE3vw1qaQKFEomcs1BlF1Zqqd3lOVMCQ2bIg5EmBW kcrB5SjfKgouvnt2O9OZaDYtOYB1CNikbMxXjSm2Bw+SUTCXVW1b5uAygo+C1yK4Rlyu2qtd6Rv XLhir0zK7o5e1U2n141ngPEXfMPmjo9o=
X-Google-Smtp-Source: AGHT+IEDButoAOdUlKP07hBiLmJSSesUtSAZw8MGCwlzAuMrGoZtk4SxEEmV/L5lbwvHG83hbqNKRhRh9TFZaHhFe3M=
X-Received: by 2002:a2e:95c4:0:b0:2d2:6193:6d53 with SMTP id y4-20020a2e95c4000000b002d261936d53mr2895332ljh.13.1709357924227; Fri, 01 Mar 2024 21:38:44 -0800 (PST)
MIME-Version: 1.0
References: <170932507606.22050.4290924992004339091@ietfa.amsl.com> <8D77A161-CC65-43F1-B1F7-C076BD1EA9F2@gmail.com>
In-Reply-To: <8D77A161-CC65-43F1-B1F7-C076BD1EA9F2@gmail.com>
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Fri, 01 Mar 2024 21:38:32 -0800
Message-ID: <CABY-gONH-1xC92=b=pGQ7rVp9_JwG1enQCqMvgFV5NiQ5TNsJw@mail.gmail.com>
Subject: Re: New Version Notification for draft-acee-rtgwg-vrrp-rfc8347bis-03.txt
To: Acee Lindem <acee.ietf@gmail.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, NETMOD Group <netmod@ietf.org>, RTGWG <rtgwg@ietf.org>
Content-Type: multipart/related; boundary="000000000000de39c40612a6e7bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/rOb1Ytb6DPl-T2gkt-OkcUuDZlk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Mar 2024 05:38:48 -0000

Hi,

Speaking as an individual contributor, I'm leaning toward option 3. In case
someone implemented RFC 8347, they can choose whether to implement the new
model.

Thanks,
Yingzhen

On Fri, Mar 1, 2024 at 12:43 PM Acee Lindem <acee.ietf@gmail.com> wrote:

> This BIS document updates the YANG model with IETF inclusive language
> guidelines as was done with the VRRP protocol specification itself.
>
> [image: ietf-logo-card.png]
>
> Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6
> <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-vrrp-rfc5798bis/>
> datatracker.ietf.org
> <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-vrrp-rfc5798bis/>
> <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-vrrp-rfc5798bis/>
>
>
> It currently doesn’t conform to YANG backward guidelines. There are
> basically three options:
>
>     1. Treat the correction of non-inclusive language as necessary bug fix
> and allow non-backward compatible changes.
>     2. Keep all the old non-inclusive data leaves in the model with
> deprecated status. At some point in future, these could be removed in a new
> document.
>     3. Make this a completely new model - ietf-vrrp-2.yang.
>
> The current individual draft is based on option 1. I had a conversation
> with Lou and he suggested the 3 third option.
>
> What are people’s opinion on this? Option 2 is my least favorite since it
> doesn’t complete the job and given how long IETF document take (especially
> YANG models), I probably won’t be actively participating long enough for
> the draft which removes the deprecated options.
>
> Thanks,
> Acee
>
> On Mar 1, 2024, at 15:31, internet-drafts@ietf.org wrote:
>
> A new version of Internet-Draft draft-acee-rtgwg-vrrp-rfc8347bis-03.txt has
> been successfully submitted by Acee Lindem and posted to the
> IETF repository.
>
> Name:     draft-acee-rtgwg-vrrp-rfc8347bis
> Revision: 03
> Title:    A YANG Data Model for the Virtual Router Redundancy Protocol
> (VRRP)
> Date:     2024-03-01
> Group:    Individual Submission
> Pages:    44
> URL:
> https://www.ietf.org/archive/id/draft-acee-rtgwg-vrrp-rfc8347bis-03.txt
> Status:
> https://datatracker.ietf.org/doc/draft-acee-rtgwg-vrrp-rfc8347bis/
> HTML:
> https://www.ietf.org/archive/id/draft-acee-rtgwg-vrrp-rfc8347bis-03.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-acee-rtgwg-vrrp-rfc8347bis
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-acee-rtgwg-vrrp-rfc8347bis-03
>
> Abstract:
>
>   This document describes a data model for the Virtual Router
>   Redundancy Protocol (VRRP).  Both versions 2 and 3 of VRRP are
>   covered.
>
>   The VRRP terminology has been updated conform to inclusive language
>   guidelines for IETF technologies.  The IETF has designated National
>   Institute of Standards and Technology (NIST) "Guidance for NIST Staff
>   on Using Inclusive Language in Documentary Standards" for its
>   inclusive language guidelines.
>
>   This document obsoletes RFC 8347.
>
>
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>