
From nobody Sat May  1 13:29:48 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EAFA3A0DBA; Sat,  1 May 2021 13:29:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Radek_Krej=C4=8D=C3=AD_via_Datatracker?= <noreply@ietf.org>
To: <yang-doctors@ietf.org>
Cc: babel@ietf.org, draft-ietf-babel-yang-model.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161990098603.26817.6467081462726716234@ietfa.amsl.com>
Reply-To: =?utf-8?b?UmFkZWsgS3JlasSNw60=?= <radek.krejci@gmail.com>
Date: Sat, 01 May 2021 13:29:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/FZDJONCdnqmJwQMrGqG-isUC8So>
Subject: [babel] Yangdoctors last call review of draft-ietf-babel-yang-model-09
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 May 2021 20:29:46 -0000

Reviewer: Radek Krejčí
Review result: Ready with Nits

This is my YANG doctor review of draft-ietf-babel-yang-model containing
ietf-babel@2021-03-12.yang module. The draft and the module are well written
and I have just two minor comments:

- The copyright year in the YANG module should be probably 2021, not 2020.

- Some values of the specific statements (e.g. min-elements) are quoted despite
it is not necessary (the value must be a number or a single word). I propose to
use pyang/yanglint to generate the module since it also unifies all the
formatting and quoting.



From nobody Tue May  4 10:39:47 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 69EC33A15BE; Tue,  4 May 2021 10:39:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: babel@ietf.org, draft-ietf-babel-yang-model.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162014997938.23614.6494865677211981729@ietfa.amsl.com>
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
Date: Tue, 04 May 2021 10:39:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/mN4I4B55M8m0XQd-9heGfQ6lTRo>
Subject: [babel] Genart last call review of draft-ietf-babel-yang-model-09
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2021 17:39:40 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-babel-yang-model-09
Reviewer: Stewart Bryant
Review Date: 2021-05-04
IETF LC End Date: 2021-04-22
IESG Telechat date: Not scheduled for a telechat

Summary: A well written text that is ready for publication. Just one note and a
couple of minor nits.

Major issues: None

Minor issues:

5.  Acknowledgements
 Juliusz Chroboczek provided most of the example configurations for babel that
 are shown in the Appendix.

The Appendix seems seems quite substantive, I am surprised that Juliusz was not
listed as an author.

Nits/editorial comments:
2.1.  Information Model

" attributes are marked a read-only objects in the information module"
SB> s/marked a/marked as/

2.3.  YANG Module
"On other hand, for a"

SB> s/On other hand/On the other hand/



From nobody Thu May  6 15:08:13 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638933A0AE4; Thu,  6 May 2021 15:08:11 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 SgI2PqOSkcDg; Thu,  6 May 2021 15:08:05 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 48CE03A0AE7; Thu,  6 May 2021 15:08:02 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id s20so4113825plr.13; Thu, 06 May 2021 15:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=+pM2KCSMevZOJ1KVlad9/5h9yvE0E12zWcHCX2j64I8=; b=k30sUFNXJ72wdhka+Coi+vj9dr9O6DxoAN7jwMoBonPA3Prn7jF1y4eRQw391ZAcWw 5RYbRgrqzgL4nf/vVsDKdGd5mhWSrfZ2+zTlQzCCKzTKyZsIEb+188VMntJ+aNF9qbBS HRqC9M+1bWA4JLOywh1u/SkTxw42di0hqN1Gqx3NHHFm4kJnrT4IkayFuCzKS0aQez7n QJrFB98Q1cRMb2oJMJBJfBOc1McKWEUeqGYrpUYJRKswvsbdakeOPvqZJfQ4wpmlIimm Fojc2DmlEQk5c7p2/HyCAGmcZaik5I0i7Xwedw27UNN8tHPZl2ljn18sskr9ku1R6IJr cuJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=+pM2KCSMevZOJ1KVlad9/5h9yvE0E12zWcHCX2j64I8=; b=OT4lLgbTSco3qo3zKg046FFMgYMk30cvo6qmCT8KAoHM/BgDC5PzSbwGzQu3cqu2Ey CJOmkThrZ5jk7vqefRcqIEwx7h/CXO73qaHpebfy7F/y0tOa/nC6Uw3DczgvPOxPg0nb fKeKc5EQSw0YDLMXgXTyXthfcKQ8vrERCqn2CmVRfRdZDJbTj386vv8+urEjV61ftZAA U5HdyaHt1nj9ng5+8P9Wr/b8snRQH7GvrEJBzgl+13iqOxqEJ2hmGPutpXAC20U2L7Lm jteJ9xCWzIMJwuhDLqGDTandVcEvdlpWXHShVEovLrEZzqa+Au6ZM2AW68fHk0hlSbM+ 1FRg==
X-Gm-Message-State: AOAM531oAwkuGWNBgmmxYvS/se9INCBVoyNbbDtcDseTZOlt1m4TCj91 +0I2ghwItphSV7+aW0NZIfE=
X-Google-Smtp-Source: ABdhPJyAnxIK+fp/MaN3ui2KIB2AXPllRIK7XvlxQjRLDVuq4PxoDtzwyEk0a0u8PIlFQGOHFGTf8A==
X-Received: by 2002:a17:90a:cb0e:: with SMTP id z14mr20480056pjt.128.1620338881371;  Thu, 06 May 2021 15:08:01 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:5982:1aa9:1959:d934? ([2601:647:5600:5020:5982:1aa9:1959:d934]) by smtp.gmail.com with ESMTPSA id cm22sm2680766pjb.32.2021.05.06.15.08.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 May 2021 15:08:00 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <9784697B-E02F-4034-9515-3CB5F3A59426@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7BDE8DA2-EC5C-452A-AFBE-324A85C0CF30"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 6 May 2021 15:07:59 -0700
In-Reply-To: <161990098603.26817.6467081462726716234@ietfa.amsl.com>
Cc: yang-doctors@ietf.org, babel@ietf.org, draft-ietf-babel-yang-model.all@ietf.org, last-call@ietf.org
To: =?utf-8?B?UmFkZWsgS3JlasSNw60=?= <radek.krejci@gmail.com>
References: <161990098603.26817.6467081462726716234@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/oetDnwoe7icP9FuX3Yem1OlR4rc>
Subject: Re: [babel] Yangdoctors last call review of draft-ietf-babel-yang-model-09
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 22:08:12 -0000

--Apple-Mail=_7BDE8DA2-EC5C-452A-AFBE-324A85C0CF30
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Radek,

Thanks for reviewing the YANG model. See comments inline.

> On May 1, 2021, at 1:29 PM, Radek Krej=C4=8D=C3=AD via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Radek Krej=C4=8D=C3=AD
> Review result: Ready with Nits
>=20
> This is my YANG doctor review of draft-ietf-babel-yang-model =
containing
> ietf-babel@2021-03-12.yang module. The draft and the module are well =
written
> and I have just two minor comments:
>=20
> - The copyright year in the YANG module should be probably 2021, not =
2020.

Fixed.

>=20
> - Some values of the specific statements (e.g. min-elements) are =
quoted despite
> it is not necessary (the value must be a number or a single word). I =
propose to
> use pyang/yanglint to generate the module since it also unifies all =
the
> formatting and quoting.

Ok. I ran pyang on the module to addresses statements that should be =
quoted or not, and fixed all of them.=20

p.s. While I was at it, I also fixed the prefix issue as it relates to =
import of ietf-yang-types that Tom Petch brought up.

Cheers.

>=20
>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_7BDE8DA2-EC5C-452A-AFBE-324A85C0CF30
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Radek,<div class=3D""><br class=3D""></div><div class=3D"">Thanks for =
reviewing the YANG model. See comments inline.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On May =
1, 2021, at 1:29 PM, Radek Krej=C4=8D=C3=AD via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" class=3D"">noreply@ietf.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Reviewer: Radek Krej=C4=8D=C3=AD<br class=3D"">Review result: =
Ready with Nits<br class=3D""><br class=3D"">This is my YANG doctor =
review of draft-ietf-babel-yang-model containing<br class=3D""><a =
href=3D"mailto:ietf-babel@2021-03-12.yang" =
class=3D"">ietf-babel@2021-03-12.yang</a> module. The draft and the =
module are well written<br class=3D"">and I have just two minor =
comments:<br class=3D""><br class=3D"">- The copyright year in the YANG =
module should be probably 2021, not 2020.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div>Fixed.</div><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D""><br class=3D"">- Some values =
of the specific statements (e.g. min-elements) are quoted despite<br =
class=3D"">it is not necessary (the value must be a number or a single =
word). I propose to<br class=3D"">use pyang/yanglint to generate the =
module since it also unifies all the<br class=3D"">formatting and =
quoting.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Ok. I ran pyang on the module to addresses statements =
that should be quoted or not, and fixed all of them.&nbsp;</div><div><br =
class=3D""></div><div>p.s. While I was at it, I also fixed the prefix =
issue as it relates to import of ietf-yang-types that Tom Petch brought =
up.</div><div><br class=3D""></div><div>Cheers.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_7BDE8DA2-EC5C-452A-AFBE-324A85C0CF30--


From nobody Thu May  6 15:13:43 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2363A0B69; Thu,  6 May 2021 15:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 FOXXzwDv2ME8; Thu,  6 May 2021 15:13:36 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 E23813A0B6C; Thu,  6 May 2021 15:13:35 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id t21so4147222plo.2; Thu, 06 May 2021 15:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YfWffnF8ag9ZepBz4gDgJmdGPvXq09FlNVk/SoeHcUI=; b=kdjmyK0Rcl5c6w9eXYFuysde/8cmxg0kZirqgh1WZZ8lkEshMxabSZDgL1PND29oT6 gB1px1UTKoKYF/q3+1KbRjUU6FZAk0krisTmI4KJdSGj7cJm4a6BI6ELXiRs7dkUcgEi eJVe1VHn52Fs3MZxPd9fOYyTzld0tcVjKf4VY7mOVPF0Y7NmJD542CSDao4zj8kx5wxc Q/5zPFufP3OAofTff2awbg2nqJvyuxRioOVhYina+2izu9JcKQoLX1KNoTiWVnZHrg9r aJ3bv/KAvphPz/MTcyrJg2uD2urtKQJWzpW7BKv/fkY0yQgbIp6OMX/w+J1VvvAWEGhq WLcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YfWffnF8ag9ZepBz4gDgJmdGPvXq09FlNVk/SoeHcUI=; b=pcHsBAQ04O/ESWrClESzhWkdscrGyr3OqFz2S5vOgzIZ69OyRzJeDgmpEPoSOmxTid ACaQXDy1i+1JWD6Zmsnzac8IU3XAVKJJTyA2pb+F8JZRpdwpvSA4sRSgpIS3/zxhJdJY vBSDNEF+e7Ow0XlrMj/wkp6RZdGKevSGTnKkSP/Htn34LZh52Dm5hyoqSm6L/u9xn9WJ D7rpxen+ZbOkuB0NJQ2xKgLEdZgkmqBqvjlza/fXAH8JEDFDBs9BKrHRdztPU9QriENr z70rMC0WZTtvCmDYk0oEq8mfcy///y/ucs6mfA0FXJtQEgO5bX6P5L4gyyCfrkhhGB7E r2dQ==
X-Gm-Message-State: AOAM531wl2UKE0Jk0N6hJ+3R2ySZ3SRkTDcTXdSE+hLoW6gJ7FWcIxEW 7r+YlrgXOwBh6bF4lF2Udj4=
X-Google-Smtp-Source: ABdhPJybTRG2B/vI4TGoRPUJeBlvKknYiFDZrMawauswEE9qQx4yK1Pe+vZHA0bPd5gJsI2yldXB9Q==
X-Received: by 2002:a17:90a:df08:: with SMTP id gp8mr7125396pjb.199.1620339214068;  Thu, 06 May 2021 15:13:34 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:5982:1aa9:1959:d934? ([2601:647:5600:5020:5982:1aa9:1959:d934]) by smtp.gmail.com with ESMTPSA id q11sm2835744pjq.6.2021.05.06.15.13.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 May 2021 15:13:33 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <675244A6-E079-498E-8D65-8D420A060F07@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_316BA69A-D0F1-4E78-B8D8-E0A98F976F04"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 6 May 2021 15:13:32 -0700
In-Reply-To: <162014997938.23614.6494865677211981729@ietfa.amsl.com>
Cc: gen-art@ietf.org, babel@ietf.org, draft-ietf-babel-yang-model.all@ietf.org, last-call@ietf.org
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <162014997938.23614.6494865677211981729@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/6px_9znpST_We0Qq2yHP-uDr9jM>
Subject: Re: [babel] Genart last call review of draft-ietf-babel-yang-model-09
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 22:13:42 -0000

--Apple-Mail=_316BA69A-D0F1-4E78-B8D8-E0A98F976F04
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Stewart,

Thanks for reviewing the document. I have addressed your nits and will =
be available as part of -10 version of the draft.

Cheers.

> On May 4, 2021, at 10:39 AM, Stewart Bryant via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-babel-yang-model-09
> Reviewer: Stewart Bryant
> Review Date: 2021-05-04
> IETF LC End Date: 2021-04-22
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: A well written text that is ready for publication. Just one =
note and a
> couple of minor nits.
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> 5.  Acknowledgements
> Juliusz Chroboczek provided most of the example configurations for =
babel that
> are shown in the Appendix.
>=20
> The Appendix seems seems quite substantive, I am surprised that =
Juliusz was not
> listed as an author.
>=20
> Nits/editorial comments:
> 2.1.  Information Model
>=20
> " attributes are marked a read-only objects in the information module"
> SB> s/marked a/marked as/
>=20
> 2.3.  YANG Module
> "On other hand, for a"
>=20
> SB> s/On other hand/On the other hand/
>=20
>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_316BA69A-D0F1-4E78-B8D8-E0A98F976F04
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Stewart,<div class=3D""><br class=3D""></div><div class=3D"">Thanks for =
reviewing the document. I have addressed your nits and will be available =
as part of -10 version of the draft.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Cheers.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On May =
4, 2021, at 10:39 AM, Stewart Bryant via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" class=3D"">noreply@ietf.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Reviewer: Stewart Bryant<br class=3D"">Review result: Ready =
with Nits<br class=3D""><br class=3D"">I am the assigned Gen-ART =
reviewer for this draft. The General Area<br class=3D"">Review Team =
(Gen-ART) reviews all IETF documents being processed<br class=3D"">by =
the IESG for the IETF Chair. &nbsp;Please treat these comments just<br =
class=3D"">like any other last call comments.<br class=3D""><br =
class=3D"">For more information, please see the FAQ at<br class=3D""><br =
class=3D"">&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" =
class=3D"">https://trac.ietf.org/trac/gen/wiki/GenArtfaq</a>&gt;.<br =
class=3D""><br class=3D"">Document: draft-ietf-babel-yang-model-09<br =
class=3D"">Reviewer: Stewart Bryant<br class=3D"">Review Date: =
2021-05-04<br class=3D"">IETF LC End Date: 2021-04-22<br class=3D"">IESG =
Telechat date: Not scheduled for a telechat<br class=3D""><br =
class=3D"">Summary: A well written text that is ready for publication. =
Just one note and a<br class=3D"">couple of minor nits.<br class=3D""><br =
class=3D"">Major issues: None<br class=3D""><br class=3D"">Minor =
issues:<br class=3D""><br class=3D"">5. &nbsp;Acknowledgements<br =
class=3D""> Juliusz Chroboczek provided most of the example =
configurations for babel that<br class=3D""> are shown in the =
Appendix.<br class=3D""><br class=3D"">The Appendix seems seems quite =
substantive, I am surprised that Juliusz was not<br class=3D"">listed as =
an author.<br class=3D""><br class=3D"">Nits/editorial comments:<br =
class=3D"">2.1. &nbsp;Information Model<br class=3D""><br class=3D"">" =
attributes are marked a read-only objects in the information module"<br =
class=3D"">SB&gt; s/marked a/marked as/<br class=3D""><br class=3D"">2.3. =
&nbsp;YANG Module<br class=3D"">"On other hand, for a"<br class=3D""><br =
class=3D"">SB&gt; s/On other hand/On the other hand/<br class=3D""><br =
class=3D""><br class=3D""></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_316BA69A-D0F1-4E78-B8D8-E0A98F976F04--


From nobody Wed May 12 13:43:19 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A01A3A1504; Wed, 12 May 2021 13:43:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: babel@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: babel@ietf.org
Message-ID: <162085219255.27931.14681686973445739755@ietfa.amsl.com>
Date: Wed, 12 May 2021 13:43:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/KpcUKtuLXiHPYywitWCz9KRt07c>
Subject: [babel] I-D Action: draft-ietf-babel-yang-model-10.txt
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2021 20:43:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Babel routing protocol WG of the IETF.

        Title           : YANG Data Model for Babel
        Authors         : Mahesh Jethanandani
                          Barbara Stark
	Filename        : draft-ietf-babel-yang-model-10.txt
	Pages           : 40
	Date            : 2021-05-12

Abstract:
   This document defines a data model for the Babel routing protocol.
   The data model is defined using the YANG data modeling language.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-babel-yang-model-10
https://datatracker.ietf.org/doc/html/draft-ietf-babel-yang-model-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-babel-yang-model-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed May 12 13:47:13 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2820C3A1530; Wed, 12 May 2021 13:47:07 -0700 (PDT)
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 VHB25mDdsH-Q; Wed, 12 May 2021 13:47:03 -0700 (PDT)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 9CB703A152F; Wed, 12 May 2021 13:47:02 -0700 (PDT)
Received: by mail-pg1-x52d.google.com with SMTP id z4so1860492pgb.9; Wed, 12 May 2021 13:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ruQFBZBp80lXK+e2hfLSqnpRBSE832vjXZZvcjAoRWc=; b=FuGm30CbyYKZoHi76c1tBo0ZX3vGNuh7kFICtitzQx94Y+VQXc/5PSRzGTClyDTJ/C DWGw+XfHRF8u6J48BbBQdN36BdoJAlVHow9ebXckZkIMVzMRROp5TcNhBHSQRwP/ZkpV qEiXdBNu1FYyM1ZwZaFrBTjN/ColubySWbus9j6PCs9B98VkS00SpRc43I8EG6cvjO08 QogqIv3mVxxWy8JKTfElKGU3JmCkMPb1YOxXPlLHXO7ixPWFVY+ynelOEjoJE1n4mc+s VsTViUFW4Bki5CXMumbeAbg++gzaXXn/G0dReDPD2OiBbxFPZpIWGZGu0uCwLKWakCLb 1NiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ruQFBZBp80lXK+e2hfLSqnpRBSE832vjXZZvcjAoRWc=; b=fHogVmog+hMLF8qHbKYHmEv2cpL55UT1iEPi/nX6MlsfcD6q3dbiXvwHGklUkrtLCp zpCn/0n8fyFBNa9ayOSOtabmKbSgWAXKKY7mtATYxlQu12I4OJcuob1xuxH6i6+yUxi4 VsmhdHuSs+Tqn4ZFMNebuB4sCgN2pHc7oaN9uUzQmCmnFz8EHeyWl0NHhQBZVRrZhNRo 4kqPOHOnBrC7Z+ATBOnh8LCdJ01hng8r9TtgKNs9E3Hky/HtTb1Mg839YnmFYCvTQ7C8 p714nRJzGRsAR3zfK6tZEIyANz02e3q8scR87Lx3/XkjqxJdWGie5K/MznaV6Xsub3f2 B/tg==
X-Gm-Message-State: AOAM530BHu1TrsHW4bF1Kd83XTUCbbtdFs0Rvo36n/8ohQYyrkL2DCJQ uCdO1mMYr+SVrQyjiyLBubA=
X-Google-Smtp-Source: ABdhPJwwRwCEJN+d7K7yIXEgBUBwX9Cc/3Lani1UX4kheqeMzUQRy8cNIB3axdfmWdDMjUGpPi3oag==
X-Received: by 2002:a17:90a:4406:: with SMTP id s6mr40699939pjg.93.1620852420417;  Wed, 12 May 2021 13:47:00 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:81ba:e539:277c:7f6? ([2601:647:5600:5020:81ba:e539:277c:7f6]) by smtp.gmail.com with ESMTPSA id l20sm496955pjq.38.2021.05.12.13.46.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 May 2021 13:46:59 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_51E1E967-8AAF-4E75-8066-71860C9FDD7F"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 12 May 2021 13:46:58 -0700
In-Reply-To: <607406F2.70500@btconnect.com>
Cc: last-call@ietf.org, babel-chairs@ietf.org, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/sbKU1QBPLDzdsQx2DOKppsYwX6U>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2021 20:47:07 -0000

--Apple-Mail=_51E1E967-8AAF-4E75-8066-71860C9FDD7F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This has been addressed in -10 version of the draft. Cheers.

> On Apr 12, 2021, at 1:38 AM, tom petch <daedulus@btconnect.com> wrote:
>=20
> This I-D introduces a new and unnecessary YANG prefix in defiance of =
BCP216 s.4.2.
>=20
> It imports ietf-yang-types, perhaps the most widely imported module in =
the world, and RFC6991, where that module is specified, defines the =
proper prefix as 'yang'.  This I-D invents a different one. Technically, =
YANG can cope with this but that does not make it a sensible thing to =
do.
>=20
> Tom Petch
>=20
> On 08/04/2021 13:43, The IESG wrote:
>>=20
>> The IESG has received a request from the Babel routing protocol WG =
(babel) to
>> consider the following document: - 'YANG Data Model for Babel'
>>   <draft-ietf-babel-yang-model-09.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits =
final
>> comments on this action. Please send substantive comments to the
>> last-call@ietf.org mailing lists by 2021-04-22. Exceptionally, =
comments may
>> be sent to iesg@ietf.org instead. In either case, please retain the =
beginning
>> of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>    This document defines a data model for the Babel routing protocol.
>>    The data model is defined using the YANG data modeling language.
>>=20
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>>=20
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> .
>>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_51E1E967-8AAF-4E75-8066-71860C9FDD7F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">This =
has been addressed in -10 version of the draft. Cheers.<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 12, 2021, at 1:38 AM, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">This =
I-D introduces a new and unnecessary YANG prefix in defiance of BCP216 =
s.4.2.<br class=3D""><br class=3D"">It imports ietf-yang-types, perhaps =
the most widely imported module in the world, and RFC6991, where that =
module is specified, defines the proper prefix as 'yang'. &nbsp;This I-D =
invents a different one. Technically, YANG can cope with this but that =
does not make it a sensible thing to do.<br class=3D""><br class=3D"">Tom =
Petch<br class=3D""><br class=3D"">On 08/04/2021 13:43, The IESG =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">The IESG has received a request from the Babel routing =
protocol WG (babel) to<br class=3D"">consider the following document: - =
'YANG Data Model for Babel'<br class=3D""> =
&nbsp;&nbsp;&lt;draft-ietf-babel-yang-model-09.txt&gt; as Proposed =
Standard<br class=3D""><br class=3D"">The IESG plans to make a decision =
in the next few weeks, and solicits final<br class=3D"">comments on this =
action. Please send substantive comments to the<br class=3D""><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a> =
mailing lists by 2021-04-22. Exceptionally, comments may<br class=3D"">be =
sent to <a href=3D"mailto:iesg@ietf.org" class=3D"">iesg@ietf.org</a> =
instead. In either case, please retain the beginning<br class=3D"">of =
the Subject line to allow automated sorting.<br class=3D""><br =
class=3D"">Abstract<br class=3D""><br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;This document defines a data model for the Babel =
routing protocol.<br class=3D""> &nbsp;&nbsp;&nbsp;The data model is =
defined using the YANG data modeling language.<br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D"">The=
 file can be obtained via<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br class=3D"">No IPR =
declarations have been submitted directly on this I-D.<br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">IETF-Announce mailing list<br =
class=3D"">IETF-Announce@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/ietf-announce<br =
class=3D"">.<br class=3D""><br =
class=3D""></blockquote></div></div></blockquote></div><br class=3D""><div=
 class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_51E1E967-8AAF-4E75-8066-71860C9FDD7F--


From nobody Thu May 13 08:47:11 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B973A1356; Thu, 13 May 2021 08:47:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <162092082278.7424.7836678134954594030@ietfa.amsl.com>
Date: Thu, 13 May 2021 08:47:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/EHuqdHZyoGdQRE25oRCt3gd-DC8>
Subject: [babel] John Scudder's No Record on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2021 15:47:07 -0000

John Scudder has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Record

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

At the moment, the automated check is returning errors:

ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" not in canonical
order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:157: error: keyword
"if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" not in canonical
order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:176: error: keyword
"if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" not in canonical
order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:187: error: keyword
"if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:206: error: keyword "if-feature" not in canonical
order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:207: error: keyword
"if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:214: error: keyword "if-feature" not in canonical
order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:215: error: keyword
"if-feature" not in canonical order (see RFC 6020, Section 12)




From nobody Thu May 13 09:04:54 2021
Return-Path: <martin.vigoureux@nokia.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE7A3A1333; Thu, 13 May 2021 09:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 bcnlLMGH6pgP; Thu, 13 May 2021 09:04:40 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2105.outbound.protection.outlook.com [40.107.22.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F53B3A1311; Thu, 13 May 2021 09:04:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GVVQz7hgsQyYEiXb9wHddEbt94tv0lVVB4tGcLIU5zCusJkl8tVbhdTJ79wDWRs7p1rBhAVetxaAHB2noJcx5TIWw0AzTUhba1kx4SyMf12kLo2e/4LGI1RRoRGSW+kqyPfmLUasyJwMsKeCsvL/O/kZl3ce7zmU2QxtH9/Bicy58PTYmcbvNXyOJegN/EKUM4ppVMR92q16KT3mPho2e93pAo+V0qDvYMcMpeH1kyc4O+dLuVbJuZ/8iMrrTzkaG3gPz18InCSBk1cfXzi6JRKmVKiUtpTZe1YY34hmV7dMgo5cltmJWo41/KGheGm8PZo6NRbs+9PmUlEAT/xGYQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rKsBWif2NaPCw5I9gXJbqhNgdMsEpxRig9zyQ+KO1HQ=; b=fLFheVa2/RM8uVrmv2GtDqeiaddsfhnOCBBm+MHfqDCXkR1m95y3gZdo8vpqnEx4OZatTJyThugiUzx7CZbXlVZhNpag2FMbOUW90WLxReCnVDN8eeGyT56z/M3eyUl8IKyFk0eYZs/Agnfac4GaOJk4O5Qpzy8vp1Rn2FbKUHTNKXw8gnKUra2/rIIBpjx6KdSeGVhALWp0DXq3KMn+sNxk1Dqr89p9NgTzDdlkGMtU868vlykpORnnluMHPOQkZr1Q0D7WUFeSE2vo3dt4EzhAgOBfyD39xEHS2Vo0SjZvJYS7O+WULhMGmoVrDwA6vivdOqun86zAuvtgpG3DOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rKsBWif2NaPCw5I9gXJbqhNgdMsEpxRig9zyQ+KO1HQ=; b=i0PGjQuutfzqAjRfgzdyce9ZfXMIiQoPKwJDYYJeDTTIyZBwu5XmXleT3qjMnzE9ThA3GOt7hS3oeyasK/2rjeBdYJDYrgd7BkWZIWpPTtoA+qiePDwU91l5M2yIkB9f6aBsRkf4v2lfB/EIirzwSMTHp4U+oTbEeSprxbjD3MM=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nokia.com;
Received: from DB7PR07MB5562.eurprd07.prod.outlook.com (2603:10a6:10:79::18) by DBAPR07MB6775.eurprd07.prod.outlook.com (2603:10a6:10:17f::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.11; Thu, 13 May 2021 16:04:34 +0000
Received: from DB7PR07MB5562.eurprd07.prod.outlook.com ([fe80::2181:3615:73f9:1ce3]) by DB7PR07MB5562.eurprd07.prod.outlook.com ([fe80::2181:3615:73f9:1ce3%7]) with mapi id 15.20.4150.011; Thu, 13 May 2021 16:04:34 +0000
To: John Scudder <jgs@juniper.net>, The IESG <iesg@ietf.org>
Cc: babel-chairs@ietf.org, d3e3e3@gmail.com, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
References: <162092082278.7424.7836678134954594030@ietfa.amsl.com>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <e34c2415-a36b-c5c7-3da2-b331f2fe6a8c@nokia.com>
Date: Thu, 13 May 2021 18:04:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <162092082278.7424.7836678134954594030@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Originating-IP: [131.228.2.20]
X-ClientProxiedBy: CH0PR03CA0097.namprd03.prod.outlook.com (2603:10b6:610:cd::12) To DB7PR07MB5562.eurprd07.prod.outlook.com (2603:10a6:10:79::18)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [172.30.2.230] (131.228.2.20) by CH0PR03CA0097.namprd03.prod.outlook.com (2603:10b6:610:cd::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4108.25 via Frontend Transport; Thu, 13 May 2021 16:04:30 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4cfd71e3-a63f-47bd-73c9-08d91628ccaa
X-MS-TrafficTypeDiagnostic: DBAPR07MB6775:
X-Microsoft-Antispam-PRVS: <DBAPR07MB677574361B4F000D8C32EAB08C519@DBAPR07MB6775.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: FLk+1rMrNPa9oRQM1NKMliaYcy3vVn+bFxhAjEpk27rXRWrKXhefucUc8q4+yyY2I8xpFhqxGOQ3/oo1d6Kp21FgWLZqKLWa/4iqhJNUjAecRZwkmJ6UGHqxz4gOcwgkBot0axsKSd1pzSC2DaJkpDQShhX6rtubh9Fweqel++Y4EUBY5cnUFT1VI4Kjd9DUGCU3CBCY6NqOsKoENHe1GDiOub2iCzXDIj3acYz3iNoedpQ4dFXhpHRnWhu6e/b+Ehl2NqGM/pDrF5ItAshbuSBn+jyubrQcgZy9v7fMF8EHePDyuxgfEpAoSKGwlpVyRHsNNjyNzRpD6iDyfg4zK/XnrX1k5WUUPq7ePlShs5Eb0Ogjk4xUcbJmz9UkaUR38ck/FD2sX3oFYHgDaL0+w/CIii39gjv50b4OziyWlcU/dYET2crhBQ0kKzoLbjXBe6h0k/jY3brAs0H6Gnq/SF46qFONno889JAzS1Pzon8dx1w3PaslDY546SqFegcNmDdR281jpoI3scLVM0rYb2/f1NqF8FIiZzQLbTfKP9Vpliq5Zk0T0xlvHCHYfqyWlqZYEumzUrdJIId+rS8nH2+DskHataodghetY1k7pxrUDOoA34f3YCY+4ZldtrO19ON/73VmwFY3FsahSlr/5sC+gpuehLgvmb6uVUsVjlatfmwz3DLIwWg8eAwMJ16fOkwYcnSOiXJfxlBoocqJZNstj9NIAQDNq3viwby/DJdLYsGSPf40SmN1OdsFUTGXOMB4gHxBMsaMo6bOeG6/yNQvlVphNu2+qtvlDQw6UKDSEPnt6bxpfBtxXhNylb1qfJVStuxRNuF0m6SqGOu2gA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DB7PR07MB5562.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(396003)(346002)(366004)(376002)(136003)(5660300002)(2906002)(6486002)(6666004)(66574015)(186003)(316002)(110136005)(66556008)(2616005)(52116002)(38350700002)(38100700002)(26005)(31686004)(16526019)(44832011)(956004)(86362001)(478600001)(66476007)(36756003)(66946007)(8936002)(8676002)(966005)(16576012)(31696002)(4326008)(83380400001)(43740500002)(45980500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?c0dqaXFReGhHd3V3TkRDS3d2SS94Q0JwTE56UXNPQlNVaUY2d3NnbHozNzVT?= =?utf-8?B?R0t3a0JvV3N6bmVaa090SndXUklFWWtYYXl5d3V0YTBTOGo4QXBiWWxoTmdQ?= =?utf-8?B?S3phVnBPVUtaZytMMFMza1J3bmt4RFg3K3c4eGQrcWJlVTFJc2xkQUVzYjh3?= =?utf-8?B?M3NWUzJBbmdESVo1d29nUmFmWktrWHB1OTR2NjJJWnhIVWg2UjRnblI3eEZu?= =?utf-8?B?OTdmYVNVSDFHTW9JaStLVW9hcTdPSVhOeWowVkVDY0Mza2ZieWFERnZja3dL?= =?utf-8?B?WkVkSVhzZ1YvcUxXeFpIOGxJZVhqSnA4TVJPWURpaXVnY0hiY0FKd3grR2Rk?= =?utf-8?B?Z0VrUlhZMDcwMHl2S1FHVzhEMXJyRGFqOG5VU29oRTBrS1NzSkdjQzQ4UU1Y?= =?utf-8?B?ZUlyREVjcnlockpLcVR0QXV1dzJsZTNRNkRpemk1bGRNQUh1aVpsdWZuR1R6?= =?utf-8?B?S1c1NWswTExiSDdockZUemR4SXpNNDgzb2ZVSTVsQ2ZCTEJza2luSDhTTGcx?= =?utf-8?B?UGVxZVJYdyt6VnE4VG1VeXR2U3BYclpFRTVZNHNhdHRoV3B5RkwyN1VDTmU5?= =?utf-8?B?VXZzell4c0Izc2xaYVY3TkQ4NW9nMGh4VEEwcEM5STdwZ1RZaDl0QWt3WTlG?= =?utf-8?B?MUV1WjBwdmpHYllPUzRoc2NvcUdIZzlTY09GMWpSaXdHWDh1aXViTVVtZzJJ?= =?utf-8?B?akJBQ253K20veDdUZVpkMCtzZGxROGNZclR3dmphSlZKQm5QdXI5bjc1QzN6?= =?utf-8?B?YUIvVURoUVFqblUybWQyK0dtV0FybHJqQ3pKUEVETTl3U20rTmtReTArQ2c4?= =?utf-8?B?TlppczFhL1UyVVQ5SHJ6VDFwR2c5YVFnNkd0TFl0L3ZpYWNONlF4NWc3UW45?= =?utf-8?B?Z0t3VEJCRXFZUWFXZ2R3V3BtZTJLVlJxcENmZUFFa0dIN29yYytxVFkwSmdJ?= =?utf-8?B?QXZkUzFqdDAreGQ5a2tDV3BPMjFjdm5Zek0yM0Y0T05NQm9vRSs3MkFGS0Js?= =?utf-8?B?REFIYkhiNlFLZlhNcUU3a1RmTUdmQ0tCbVVoRXhtRkM4YldrRXM0Uit3bldL?= =?utf-8?B?SWRhWTFhQUFRek51Nkl6Y0dOQUNNSEJhRkJHVkJmaWEzaXhMTnlhRkJkOWlT?= =?utf-8?B?SkV6blVaWmJIQUdDRHFuSHdrbmJwRmEyQ2tIcGh4dzdGVmUza1hhek5SREZJ?= =?utf-8?B?VlBYODB4SUIwL3YycUx5TVJ2TE0vSkVuM0FuRjF2Q1RGZFdTNnE3UUh4aFBW?= =?utf-8?B?cEN1TlZrRWhWUWxYTldzM0FUem9aMytwWW9qblVLNGlGUklVRmdWcnZ5WUs1?= =?utf-8?B?blRzZUdscnplY2I4NW9INUg3MGVnbC8vRnQrWUliMHNpdFhsVmRleDdWZzVN?= =?utf-8?B?UEx6VzNNVE42YmVScmhQWGYzYXVwWDl0TGRVVW9QaG9XL1N3VVc1ajlYUVVG?= =?utf-8?B?NENaK1RSNFZRa2kzTnRTQVRwV0IwekQ3MXJHVkIxNVo2UkZjdkkyc0MwODlw?= =?utf-8?B?MUJBcFRtNDNLR0ZnSXVIbWJrUnhJdWdvdlpkZ3dpcTY3QWxSd2F1eGhiWkdy?= =?utf-8?B?WGFjOWtUSjhwL0tueHNmclhvMEVzdjJXL2oxOWNySHFSTWZGVzdyb25jSW9r?= =?utf-8?B?VGJrbTk4K3VtemRvRGxxT0ZrTXI1SDJIKzhjM1N3Rks0MzgvZ21zSEVQUFhw?= =?utf-8?B?U3JRaG1lUXdBdkhwVU0xY240czJIOU1rRGpiSWxyVmlEd1Y3cnJ6d3gyVGk5?= =?utf-8?Q?QZiaYudRnDYBBYdnZgsIvnzMjPxCsVVgjmyxLbx?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4cfd71e3-a63f-47bd-73c9-08d91628ccaa
X-MS-Exchange-CrossTenant-AuthSource: DB7PR07MB5562.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 May 2021 16:04:33.8871 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: EwmkhF4657ESBWyvivgZyIzpe1iMQOBHG44LvS7luxCBSOVWzmRPwXRRFncOqSJGsWDRUFn4QYvv/g4rwg9KLckeEW4Vg/NgWUFfVh44v8g=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBAPR07MB6775
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/FM3eDskXqvOxDr_dYeAUPAqycs4>
Subject: Re: [babel] John Scudder's No Record on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2021 16:04:53 -0000

Thank you John
that's strange.
I'm pretty sure everything was fine on 09 as I looked yesterday few 
hours before I submitted the ballot. I was waiting for v10.
But I have to admit that I didn't look again at the yang checks on v10 
before pressing the button.

Looking at the diff it seems fairly easy to address.

-m

Le 2021-05-13 à 17:47, John Scudder via Datatracker a écrit :
> John Scudder has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Record
> 
> 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/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> At the moment, the automated check is returning errors:
> 
> ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" not in canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:157: error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" not in canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:176: error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" not in canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:187: error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:206: error: keyword "if-feature" not in canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:207: error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:214: error: keyword "if-feature" not in canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:215: error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> 
> 
> 
> 


From nobody Thu May 13 10:12:37 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21DF03A15AD; Thu, 13 May 2021 10:12:35 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 AtqGg6N8C2eu; Thu, 13 May 2021 10:12:31 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 162D53A156E; Thu, 13 May 2021 10:12:13 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id v191so22357688pfc.8; Thu, 13 May 2021 10:12:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dlSp17AA/EXMgjEi+/RdqaL5MFkTGlnA+yfjFpVEP1c=; b=lGrQ7Op+ek+xnsrROV9abFTxhFQotz+1B1T58JGljKZEOam1KvKbV+FmzOGd2PK9Ci 2KlMyjncjL1AnNgOLCQ/4j42fS+SNlKNlwJo0b8ixi+HzFVrE9k2lmEudwjZqAul4LpB 92Ivlcu3Lp2vN/Fd7cKNdXpYLEWpJUj1HrTl5oO1jUFaf7JGBaecz4AyfdzkdvHFDec/ ztet0Zsxw+3UX66nyDn0quijXhRRg+ijsJ5jPsZu1omRCq3f11ZBF0MxnTXpmq7kaWdQ MjdNXiOWi/w2MfVqy4xaUEU9yynBGBlZ5OTQJB/ZXjj/Ne2ok+KoMymj0gzhjJwwkyK3 FPbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dlSp17AA/EXMgjEi+/RdqaL5MFkTGlnA+yfjFpVEP1c=; b=HQ7/g916u8dsJisEBodY05fPDrxVHTUpUf/mKHpCkFu6ythzbT5E5KykMTGn73brv3 h82Ir9FCI7DSvuvF6DlGisPbtymzZQYtzA5qTPJrsZME2tA/bLYjs4+jpo6oLJza6ccF 5WBeBAsw7BTrtnVOvzkOW5QmZHcPD8cvIzhyYL3BqcwD+JJ1IqAXw5e0dKn2+PEHSJT6 6vMDRW3xhPVnB5WeCV34QUP9E+JI5YRGCX21sVIhfeHrEKWDFk9uLZyC0Pq0tvS15X7d wdoO175RtuTdNKGGRkwFU2ClMSmWfEEnQR6zbVDBh6uKi7n+7JnE1OQT2va3Q+D7fzLm aNrQ==
X-Gm-Message-State: AOAM532n318eCc6ytcNyj0RWgF1fWoAmxtjV97dTza9xOToWDyx/sfnj 7NiXRfoocekqCGR4ZJXJDk0=
X-Google-Smtp-Source: ABdhPJwpK+sPQXiOGdmIOlzskskPoRKlP76+xpgVduUrtKvbYZk9K+/0WRP9yQZbQVUgffm/oQ1Kaw==
X-Received: by 2002:a17:90a:aa14:: with SMTP id k20mr6344800pjq.88.1620925931347;  Thu, 13 May 2021 10:12:11 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:e9d0:b7e0:1e2c:2ca5? ([2601:647:5600:5020:e9d0:b7e0:1e2c:2ca5]) by smtp.gmail.com with ESMTPSA id w81sm2345828pfc.106.2021.05.13.10.12.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 May 2021 10:12:10 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <8AEF8127-E8A5-442C-B775-24B65DF3F2E8@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2FD757D4-C3B5-46EF-B418-28ADE784ED17"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 13 May 2021 10:12:09 -0700
In-Reply-To: <162092082278.7424.7836678134954594030@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: John Scudder <jgs@juniper.net>
References: <162092082278.7424.7836678134954594030@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/1x5dtT_x-TvgeoeMEQ7iWFvIF24>
Subject: Re: [babel] John Scudder's No Record on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2021 17:12:35 -0000

--Apple-Mail=_2FD757D4-C3B5-46EF-B418-28ADE784ED17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi John,

Apparently, this check has been updated recently.

$ pyang --lint --strict --canonical -p ../../../iana/yang-parameters =
ietf-babel@2021-05-12.yang=20
$ pyang --version
pyang 2.0.2

Which after upgrade gave the following output:

$ pyang --version
pyang 2.4.0
$ pyang --lint --strict --canonical -p ../../../iana/yang-parameters =
ietf-babel@2021-05-12.yang=20
ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:157: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:176: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:187: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:207: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:208: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:215: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)
ietf-babel@2021-05-12.yang:216: error: keyword "if-feature" not in =
canonical order (see RFC 6020, Section 12)

I will address it.

Thanks.

> On May 13, 2021, at 8:47 AM, John Scudder via Datatracker =
<noreply@ietf.org> wrote:
>=20
> John Scudder has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Record
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> At the moment, the automated check is returning errors:
>=20
> ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" not in =
canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:157: =
error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" not in =
canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:176: =
error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" not in =
canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:187: =
error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:206: error: keyword "if-feature" not in =
canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:207: =
error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
> ietf-babel@2021-05-12.yang:214: error: keyword "if-feature" not in =
canonical
> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:215: =
error: keyword
> "if-feature" not in canonical order (see RFC 6020, Section 12)
>=20
>=20
>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_2FD757D4-C3B5-46EF-B418-28ADE784ED17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
John,<div class=3D""><br class=3D""></div><div class=3D"">Apparently, =
this check has been updated recently.</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">$ pyang --lint --strict =
--canonical -p ../../../iana/yang-parameters <a =
href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>&nbsp;</div><div class=3D"">$ =
pyang --version</div><div class=3D"">pyang 2.0.2</div><div class=3D""><br =
class=3D""></div><div class=3D"">Which after upgrade gave the following =
output:</div><div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D"">$ pyang --version</div><div class=3D"">pyang 2.4.0</div><div =
class=3D"">$ pyang --lint --strict --canonical -p =
../../../iana/yang-parameters <a =
href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>&nbsp;</div><div class=3D""><a =
href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:148: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:157: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:175: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:176: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:186: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:187: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:207: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:208: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:215: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section 12)</div><div =
class=3D""><a href=3D"mailto:ietf-babel@2021-05-12.yang" =
class=3D"">ietf-babel@2021-05-12.yang</a>:216: error: keyword =
"if-feature" not in canonical order (see RFC 6020, Section =
12)</div></div><div class=3D""><br class=3D""></div><div class=3D"">I =
will address it.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 13, 2021, at 8:47 AM, John Scudder via =
Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
class=3D"">noreply@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">John =
Scudder has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Record<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">At the moment, the automated check =
is returning errors:<br class=3D""><br =
class=3D"">ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" =
not in canonical<br class=3D"">order (see RFC 6020, Section 12) =
ietf-babel@2021-05-12.yang:157: error: keyword<br class=3D"">"if-feature" =
not in canonical order (see RFC 6020, Section 12)<br =
class=3D"">ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" =
not in canonical<br class=3D"">order (see RFC 6020, Section 12) =
ietf-babel@2021-05-12.yang:176: error: keyword<br class=3D"">"if-feature" =
not in canonical order (see RFC 6020, Section 12)<br =
class=3D"">ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" =
not in canonical<br class=3D"">order (see RFC 6020, Section 12) =
ietf-babel@2021-05-12.yang:187: error: keyword<br class=3D"">"if-feature" =
not in canonical order (see RFC 6020, Section 12)<br =
class=3D"">ietf-babel@2021-05-12.yang:206: error: keyword "if-feature" =
not in canonical<br class=3D"">order (see RFC 6020, Section 12) =
ietf-babel@2021-05-12.yang:207: error: keyword<br class=3D"">"if-feature" =
not in canonical order (see RFC 6020, Section 12)<br =
class=3D"">ietf-babel@2021-05-12.yang:214: error: keyword "if-feature" =
not in canonical<br class=3D"">order (see RFC 6020, Section 12) =
ietf-babel@2021-05-12.yang:215: error: keyword<br class=3D"">"if-feature" =
not in canonical order (see RFC 6020, Section 12)<br class=3D""><br =
class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_2FD757D4-C3B5-46EF-B418-28ADE784ED17--


From nobody Thu May 13 12:44:35 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5FE3A0DC1; Thu, 13 May 2021 12:44:34 -0700 (PDT)
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 qj5IlgM2MHwJ; Thu, 13 May 2021 12:44:29 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 0487B3A0DB8; Thu, 13 May 2021 12:44:28 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id c21so22407909pgg.3; Thu, 13 May 2021 12:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=H6+99Rjr0tDdmyduAVU+Ev6Oaoi3TeRvIJq6CeiFbjQ=; b=Yi9y/tvyCZsOS9St8OjXtIEKvbcz6tjyTnQMjHAVkjlVPu8JdyIVEbrXuyw+Z3zNCV es10QyHDR5ECm2e7JMoaMtWF2pxWRWdA76DUAZcnvSMr/QWPpX1OimptuNXhbAtQxby4 5/vAqhLVvvg2XaPbxHhncAhRV0Vk8meZU+5hCZQgCSWZXDt0+/esxNA4noYtI/mmoF2Q URX53pN44rVZGgLd5Zn4ohmhBxKaqwEZYySeiX4pG9JHvg45mhcc9fD0zxurETnqwr5k fga52c/qEC1EcVeIDjFMHmCaB0JHAlCwsFA8ATC2cBS8/lmxPkuIMTuPSgBs7ZOVTPis kjgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=H6+99Rjr0tDdmyduAVU+Ev6Oaoi3TeRvIJq6CeiFbjQ=; b=H6jO54XmCObkU5v14npcUF6YvSr4oKaJ4bxpyGpVX9J01N+r0W8JrhZbuGh/SeHyBa GZTL4oVXs/mDcBwJpCW8sx9/N9Y45kuz5VJODxkg2WPF7fe24EUjwjtPzx8taXEQPipc FB5irbMz9v7or3is7cGtOZ1tZXsIAiY7U9f7787jvV6kXXWaLgW3DC4RTojBJ9dFcsao fH1zwjyAt7jSmYxq3vw5Ptc81TTMkIQwMFazgzjyz2GtnNBRugNQTAnZWEuoCPaT9+Bt qp26V92g6lPWWOAfzF0P4msmQSbzzZLnWcuGdyRgaiB3qb1dnN5qUtc9N/Z/DsKQ25gQ WFmQ==
X-Gm-Message-State: AOAM532Xm5SwduPCIng9vs4M8bZc30fQmEn0CjGGS3iEiDRSHk1WBSZO pRA58wgfW+5ACSZfzRtvMFQ=
X-Google-Smtp-Source: ABdhPJxtm+azF9TILbs3uzn29YFtDmL/U/quNefvyMXIkm+q9tQn+XSLHrJGdy2kX1bnNg897A62vg==
X-Received: by 2002:a63:a552:: with SMTP id r18mr12646190pgu.439.1620935067675;  Thu, 13 May 2021 12:44:27 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:e9d0:b7e0:1e2c:2ca5? ([2601:647:5600:5020:e9d0:b7e0:1e2c:2ca5]) by smtp.gmail.com with ESMTPSA id v130sm2593305pfc.25.2021.05.13.12.44.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 May 2021 12:44:27 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <474E50C2-7835-4406-9FE6-1C59293A28BD@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0AEA18B2-E644-4343-8D3E-761ED4D70597"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 13 May 2021 12:44:25 -0700
In-Reply-To: <e34c2415-a36b-c5c7-3da2-b331f2fe6a8c@nokia.com>
Cc: John Scudder <jgs@juniper.net>, The IESG <iesg@ietf.org>, babel-chairs <babel-chairs@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
To: Martin Vigoureux <martin.vigoureux@nokia.com>
References: <162092082278.7424.7836678134954594030@ietfa.amsl.com> <e34c2415-a36b-c5c7-3da2-b331f2fe6a8c@nokia.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/v3w0v8RyMY-OypF4_ksmjdzcH50>
Subject: Re: [babel] John Scudder's No Record on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2021 19:44:34 -0000

--Apple-Mail=_0AEA18B2-E644-4343-8D3E-761ED4D70597
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi John/Martin,

I have fixed this here.=20

=
https://github.com/mjethanandani/babel-data-model/pull/30/commits/6e92cfa9=
932f43964e6d7db6f6103b13636c90f2 =
<https://github.com/mjethanandani/babel-data-model/pull/30/commits/6e92cfa=
9932f43964e6d7db6f6103b13636c90f2>

I am expecting more comments, so I am holding on publishing v11 at this =
time. If you disagree, let me know and I can publish v11.

> On May 13, 2021, at 9:04 AM, Martin Vigoureux =
<martin.vigoureux@nokia.com> wrote:
>=20
> Thank you John
> that's strange.
> I'm pretty sure everything was fine on 09 as I looked yesterday few =
hours before I submitted the ballot. I was waiting for v10.
> But I have to admit that I didn't look again at the yang checks on v10 =
before pressing the button.
>=20
> Looking at the diff it seems fairly easy to address.
>=20
> -m
>=20
> Le 2021-05-13 =C3=A0 17:47, John Scudder via Datatracker a =C3=A9crit =
:
>> John Scudder has entered the following ballot position for
>> draft-ietf-babel-yang-model-10: No Record
>> 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/iesg/statement/discuss-criteria.html
>> for more information about DISCUSS and COMMENT positions.
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>> At the moment, the automated check is returning errors:
>> ietf-babel@2021-05-12.yang:148: error: keyword "if-feature" not in =
canonical
>> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:157: =
error: keyword
>> "if-feature" not in canonical order (see RFC 6020, Section 12)
>> ietf-babel@2021-05-12.yang:175: error: keyword "if-feature" not in =
canonical
>> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:176: =
error: keyword
>> "if-feature" not in canonical order (see RFC 6020, Section 12)
>> ietf-babel@2021-05-12.yang:186: error: keyword "if-feature" not in =
canonical
>> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:187: =
error: keyword
>> "if-feature" not in canonical order (see RFC 6020, Section 12)
>> ietf-babel@2021-05-12.yang:206: error: keyword "if-feature" not in =
canonical
>> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:207: =
error: keyword
>> "if-feature" not in canonical order (see RFC 6020, Section 12)
>> ietf-babel@2021-05-12.yang:214: error: keyword "if-feature" not in =
canonical
>> order (see RFC 6020, Section 12) ietf-babel@2021-05-12.yang:215: =
error: keyword
>> "if-feature" not in canonical order (see RFC 6020, Section 12)

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_0AEA18B2-E644-4343-8D3E-761ED4D70597
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
John/Martin,<div class=3D""><br class=3D""></div><div class=3D"">I have =
fixed this here.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D""><a =
href=3D"https://github.com/mjethanandani/babel-data-model/pull/30/commits/=
6e92cfa9932f43964e6d7db6f6103b13636c90f2" =
class=3D"">https://github.com/mjethanandani/babel-data-model/pull/30/commi=
ts/6e92cfa9932f43964e6d7db6f6103b13636c90f2</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">I am expecting more comments, so I am =
holding on publishing v11 at this time. If you disagree, let me know and =
I can publish v11.<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On May 13, 2021, at 9:04 AM, =
Martin Vigoureux &lt;<a href=3D"mailto:martin.vigoureux@nokia.com" =
class=3D"">martin.vigoureux@nokia.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Thank =
you John<br class=3D"">that's strange.<br class=3D"">I'm pretty sure =
everything was fine on 09 as I looked yesterday few hours before I =
submitted the ballot. I was waiting for v10.<br class=3D"">But I have to =
admit that I didn't look again at the yang checks on v10 before pressing =
the button.<br class=3D""><br class=3D"">Looking at the diff it seems =
fairly easy to address.<br class=3D""><br class=3D"">-m<br class=3D""><br =
class=3D"">Le 2021-05-13 =C3=A0 17:47, John Scudder via Datatracker a =
=C3=A9crit&nbsp;:<br class=3D""><blockquote type=3D"cite" class=3D"">John =
Scudder has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Record<br class=3D"">When =
responding, please keep the subject line intact and reply to all<br =
class=3D"">email addresses included in the To and CC lines. (Feel free =
to cut this<br class=3D"">introductory paragraph, however.)<br =
class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D"">The document, along with other ballot =
positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">At the moment, the automated check is returning =
errors:<br class=3D"">ietf-babel@2021-05-12.yang:148: error: keyword =
"if-feature" not in canonical<br class=3D"">order (see RFC 6020, Section =
12) ietf-babel@2021-05-12.yang:157: error: keyword<br =
class=3D"">"if-feature" not in canonical order (see RFC 6020, Section =
12)<br class=3D"">ietf-babel@2021-05-12.yang:175: error: keyword =
"if-feature" not in canonical<br class=3D"">order (see RFC 6020, Section =
12) ietf-babel@2021-05-12.yang:176: error: keyword<br =
class=3D"">"if-feature" not in canonical order (see RFC 6020, Section =
12)<br class=3D"">ietf-babel@2021-05-12.yang:186: error: keyword =
"if-feature" not in canonical<br class=3D"">order (see RFC 6020, Section =
12) ietf-babel@2021-05-12.yang:187: error: keyword<br =
class=3D"">"if-feature" not in canonical order (see RFC 6020, Section =
12)<br class=3D"">ietf-babel@2021-05-12.yang:206: error: keyword =
"if-feature" not in canonical<br class=3D"">order (see RFC 6020, Section =
12) ietf-babel@2021-05-12.yang:207: error: keyword<br =
class=3D"">"if-feature" not in canonical order (see RFC 6020, Section =
12)<br class=3D"">ietf-babel@2021-05-12.yang:214: error: keyword =
"if-feature" not in canonical<br class=3D"">order (see RFC 6020, Section =
12) ietf-babel@2021-05-12.yang:215: error: keyword<br =
class=3D"">"if-feature" not in canonical order (see RFC 6020, Section =
12)<br class=3D""></blockquote></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_0AEA18B2-E644-4343-8D3E-761ED4D70597--


From nobody Fri May 14 03:20:21 2021
Return-Path: <daedulus@btconnect.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8F703A2D7D; Fri, 14 May 2021 03:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 apCHAE2qbogB; Fri, 14 May 2021 03:20:10 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130137.outbound.protection.outlook.com [40.107.13.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 465933A2D7A; Fri, 14 May 2021 03:20:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Ts2Wqn7cOReA8jWuwH+MC+/8TnBzCv8mKkxLLZozWv4ikB5Cb4cwU4lLVyAeV1p6HWy+dgnqXSzjsKy63e4QgmiVE7hOhRaaIVgx361jTfSOKvDhKNT9m/dyZ0omuTAxnaaPMHGFa3lwy7NaRVcjZY5ududgBRl51PR32wfBGDzvn96e8bF6HXIWJMlM8tmlmHiP7BWNAKthiDB+UPH76mkjYT+UXomfMZ2kD1JQ0dWeAxnKpal5qylJpsNeSJzmDfMTu+4CsK5MNpjiIBxy87EkEoTGClJggchDw0hce3b2sOYcYK3MZC/4Ap8qkICVPQRdu+mm6tVGNN6ze7koxg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MmGxjyEza4VPBIkltQsVlT1xrBdRloHkVRt36e1Tmg0=; b=MnT977gR6KJm5Cz0Y2FrGQ4AEMP9p51xr2RUnKV4EtlQvNtkcL0eAG6C+A9OMOaxCdhPbVBrQjoXzNTcue5Qh+v/TAjvTLx+VHZLSO+BuZwcecvMdeewwkxU4Ta08quyuhJ2ifBfJ2oR3vmswCaFXCPchRT/6DbvkS5rfq+IJOITjEzJD7OgcRJwUfsJ6Q6dXNA2WCMqZP3JTiaGFI0KIEMnFFrRA2+TQIXwwhZvkjG5mtY8krzycPuPz5kxzQlgPhMdGzaFwPWBilOmIse7l0ncikcS2sfoHQVImo9ujd+JxALsd7CZvCE3BwRgr7iqYK4WUUxllM8iQyNc4l0EOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MmGxjyEza4VPBIkltQsVlT1xrBdRloHkVRt36e1Tmg0=; b=YdJgoqedYuLnQzuwuv2CczYufCN7A2VaJGfTHiq+2dtMwmccRQ/RiM3kbW3nOoqvZlQGDdbKEg992ptuT5EysTdW2w1nf2fSzuqTeWl4vC6k3z+ocRWO0PNH7joWkW00bWIRTAK9mzl9/d3EadjxVJBTqkMZtNowg06+AMItiqg=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB3517.eurprd07.prod.outlook.com (2603:10a6:802:22::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4129.23; Fri, 14 May 2021 10:20:07 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4150.011; Fri, 14 May 2021 10:20:07 +0000
To: Mahesh Jethanandani <mjethanandani@gmail.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com>
Cc: last-call@ietf.org, babel-chairs@ietf.org, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <609E4ED3.5010101@btconnect.com>
Date: Fri, 14 May 2021 11:20:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.143.250.49]
X-ClientProxiedBy: LO2P123CA0012.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:a6::24) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.143.250.49) by LO2P123CA0012.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:a6::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4108.25 via Frontend Transport; Fri, 14 May 2021 10:20:06 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 9c0b6a55-d1e8-4312-5f8a-08d916c1d8ae
X-MS-TrafficTypeDiagnostic: VI1PR07MB3517:
X-Microsoft-Antispam-PRVS: <VI1PR07MB3517D10FBE94649E1A06A01FC6509@VI1PR07MB3517.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: Ea0gUe5hXy1EcHb2SOnryzXleDv/t1xqyYsF6tSKRokaFmNf0smzsvheorA9jNuyycpVptFfBfvPw5AwtvDoTtsNCG+za2GAOE5tkgxC+MMkELpXRnSzM1w6ENeA5TphVDKzWI0cZPDkdUSHAMC2fZnCUysvP9aFAkqZPlYhqHpQZ7any6KTKjKD5xFNs+uhkxS0nIWAy7ytA4CM4cCWXH5MATbwUnPGn/M4x2oI0n3slb4pqo9rg2LARF2FtiiDv6fZZM0hPNkkQv1q1mawXMlGphnLtGWSJRnxvk/y+I+JRTecb3rLnKhAGTMgkTLg/5SsYSLKusVkAiJG4zS84Tyjurzdhbc3rmez04izzVs7ooo0FsdhEVKJN8NNfD+Fv8deXiF0iYd1PtAbWviU4erkqRkxDKZM4n3jbWMOtlGE0IPx9ArCDWdgjpQ5In5yI214sggTgY87qUhtAgAjX31Qmvhsf1AYVvdG0UHRsT1dSCH9xjBdN1UuTTpy8MLFgUUSRp8L4VruHpDj69r4ju7ydd79ezQLe5ENypLRTkyD/SyWHEaWodY0h/Fmqd0MXzGfw7z83N67wA+PTN8UqOn1sLBz/dpsmjYSB4Jo/0N1+abtdDOirH2lVooNiIz3z7uPvKFN9Uf87/2t2d+gpQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(376002)(366004)(136003)(346002)(396003)(86362001)(52116002)(478600001)(5660300002)(186003)(8676002)(16576012)(87266011)(83380400001)(66946007)(66556008)(6916009)(36756003)(8936002)(2906002)(26005)(33656002)(6666004)(4326008)(66476007)(956004)(6486002)(38100700002)(2616005)(16526019)(38350700002)(53546011)(316002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?Windows-1252?Q?TJm8gziIkLRvsVDS0PMlBGwi1Bfgs1O7TkPRw57wNDTRFSTPU0zhC4Qd?= =?Windows-1252?Q?rESFNZrUUsxU/8s6Miei+XmEzi9GtGMSm25mfxdjynke/F3+IRGm8u4C?= =?Windows-1252?Q?kydZwmhMsTvNNHEt++hQ8WZIkbc9KpRymkZEmWEbwZRg1qNtd16boOt+?= =?Windows-1252?Q?F92tUdVif7z7cmv8QyQ8hirrPLrjn+hz5W48OZ+goe2ANkQHFE22wH8F?= =?Windows-1252?Q?PEyqmwDGTwocpQhZtYGd94TRQIQ73UGv4HckFIXs76aEfRqqsSb68osj?= =?Windows-1252?Q?xmVt1daZ5Re9235Gr6GQW49lisb5V1OGKLKuOZL9PqOb8C3q+4Kv2P26?= =?Windows-1252?Q?xyk+FCAkZ+ILr/8B2zMFfcgiaBhavcA2kXmJHxY6Pwqwk9fWaaWyQo0L?= =?Windows-1252?Q?NWD4TC3eCgJr9QRCU+TYQ+c0pEVFIs8c4NU2TrKxhK5CcsvsN0f0VBkc?= =?Windows-1252?Q?HQYELOXmFoFyUc5oEN9H7T1RnuDz2D6Vydl6KIex9EevF5BdNIUqjUD/?= =?Windows-1252?Q?bJjxOXLUWk5Fhw2+PuN3cJ2wdUQConSH5+5gJ9Okixmzjhumh9sa6Iil?= =?Windows-1252?Q?RM60x4AVxSQJ1SeayG7kJ2F7RR65D5kOZ1UyMrosWsMIjTaxBa00GFiP?= =?Windows-1252?Q?mxS5RReZd/6TD46ts95fenDDO9tFIhLTtu02efLzE0OM8/wp0jLKvU4x?= =?Windows-1252?Q?OrjBRLSf7DONJ9ydaAE7KG/DXteiP1ypvwXynV4guEl/rirPpiqGR8lc?= =?Windows-1252?Q?qd53Z+zyLKxUNdFNkYKPqhWEFJL7VdklCmvyRjuTwPA1VNYUvn9h/127?= =?Windows-1252?Q?NtCHkl7cYRoaNnof2r2A44UGVDI0qXJyiAuaJI7IJzq5/PRB0mFnKKg5?= =?Windows-1252?Q?kdYd2gNbCcRlyviL7cYEm82VzI3C0SEaLbANAqDe1CPydbx2ohbqr2He?= =?Windows-1252?Q?jvRkRQ6gWjyEahNDy7mvYL7G6U1LavnR2Fzi9Re+hb5l/nIcKEqxgU/G?= =?Windows-1252?Q?5F2EHGRdX7nKSE6unKj8J5FA4/JIKGpQLaDghMocCGp/vclilnlx7Xeo?= =?Windows-1252?Q?oHxF8DNY8Z1x48CaSNOVqcXPB6NCB8aO4vrfKa2N2yV8zGjy0ePIMPtS?= =?Windows-1252?Q?menYkPyk00/dAlETIbqos0x4QW6g9WqglBl/qclwbhLQu5GArFH0r+Kt?= =?Windows-1252?Q?2SGUsZKG5ZnUY2I9c7X1qGEcLA6+cBBAfdM6cB8jEaGPdewWg6lw4njc?= =?Windows-1252?Q?83iCiVg178mwBi9SBkrSd0fRtGq9396bpS7KCYSR5yMFPhu6vz2MGTNz?= =?Windows-1252?Q?lB5LRNptEadCe8206uC+jysCiTsj4V5e1IlRlMFPY1A476pfz773rtTf?= =?Windows-1252?Q?2+ZLkSxiiEMXLp7IE4SlqCgA20BbxvIiomXq143kQMF2MMW/TK5BIao5?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9c0b6a55-d1e8-4312-5f8a-08d916c1d8ae
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 May 2021 10:20:07.3842 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: P6vASJ45L30oQMRX/F9I9jmripEbZaxgg5ifuJQ/Ezh/IvHI64NwS1UmsJdHgDXq3jxrns706yssq6i4zPn70Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3517
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/9jbmpw7muM11tQ9WNdmxnnIwJ5k>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 10:20:16 -0000

On 12/05/2021 21:46, Mahesh Jethanandani wrote:
> This has been addressed in -10 version of the draft. Cheers.

Indeed it has.

I note that some YANG clauses have [references] in them which are likely 
not plain text; doubtless that will be fixed at some point in the process.

Tom Petch
>
>> On Apr 12, 2021, at 1:38 AM, tom petch <daedulus@btconnect.com> wrote:
>>
>> This I-D introduces a new and unnecessary YANG prefix in defiance of BCP216 s.4.2.
>>
>> It imports ietf-yang-types, perhaps the most widely imported module in the world, and RFC6991, where that module is specified, defines the proper prefix as 'yang'.  This I-D invents a different one. Technically, YANG can cope with this but that does not make it a sensible thing to do.
>>
>> Tom Petch
>>
>> On 08/04/2021 13:43, The IESG wrote:
>>>
>>> The IESG has received a request from the Babel routing protocol WG (babel) to
>>> consider the following document: - 'YANG Data Model for Babel'
>>>    <draft-ietf-babel-yang-model-09.txt> as Proposed Standard
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits final
>>> comments on this action. Please send substantive comments to the
>>> last-call@ietf.org mailing lists by 2021-04-22. Exceptionally, comments may
>>> be sent to iesg@ietf.org instead. In either case, please retain the beginning
>>> of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>     This document defines a data model for the Babel routing protocol.
>>>     The data model is defined using the YANG data modeling language.
>>>
>>>
>>>


From nobody Fri May 14 09:17:10 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A64943A37D4; Fri, 14 May 2021 09:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 dvvI2ormcquK; Fri, 14 May 2021 09:17:04 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 3845B3A37CD; Fri, 14 May 2021 09:17:04 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id n3so4247269plf.7; Fri, 14 May 2021 09:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=adVP4VhUaFIxbXTCLnvS4nNMV6Rt/d7C0scY7Kvtfro=; b=tHu8P3tpIt2uCSuT71ENaS+7jxAG6J99NzTMq5CAmLpv7EjriDjruuuM6B0r+EDtPa cy/bnztDVUuj12OCWFa673YPwo33KYcGGA/UTecvDmNR3ia4YgKsBaHf+TZTGAobdPQ1 rE8FjIR3fdNa2Vyu1vWxHZCO0t/OhNv7hLlJYJ2SnwgWDxkywmVIsQ9Z2ryo4oYDTZ4b SOTckOdZxshzp6oWY1zkRnDCNaCd/k+bwwHA11jZz2sUOczBEYWOR8PqJKpKb7/KVYrB vpd1RvIHqprivU9IWszxVrDsKWXqaRfcYatkv9v0pw7AXikor5QmsIVSLP/0ZeZqlNiW 7kbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=adVP4VhUaFIxbXTCLnvS4nNMV6Rt/d7C0scY7Kvtfro=; b=Qyn2x+GBni4k7lcsLxpRs3PIhVF3CQ7ZiUY9wViQ9qtOClUfBc2A0WlhQSV8x3izeR RlUwQgRD5wlsDZRd/MKRs4eYBEtoNKDyS1WoK+1TWsRXhXPlnT6BOyyFFtc0vHR987ra TNSwX770WnAS3l6qcQvH4lo9Zj0DIdI/euzxAKXMwYiLJmbPbDASjRMKINbvLOlEUQ2o YZlyX19lgR+Jlzs6PWUkg19Gw66/FCUxeuOFxTNNeyEGTZhQJE1ZKZyyj6cBZfNnBCKp O4fzicQroQ18knoPw7ZrgqjGZG3HR2giLI63XqFi5qsKezYbxi84W1qTi9E8TkYwOdD8 2wUw==
X-Gm-Message-State: AOAM533KdJUyd9dd9Vs+9Z9LA5qKapb+2Sb9RS8xpG2XkrOdxNahKOZe smjBnV+H2gjRQJOOb5fVhqc=
X-Google-Smtp-Source: ABdhPJy3gxnn8ZjC+PIRayIpXnebtKfGVI4aorVyFA2Ni5f6yeYjF6vcxpkJNiDHZ1j+pIbyeAZWsA==
X-Received: by 2002:a17:902:f784:b029:ef:8e2f:430e with SMTP id q4-20020a170902f784b02900ef8e2f430emr12325470pln.28.1621009022362;  Fri, 14 May 2021 09:17:02 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:25f2:6a5c:8d81:dca9? ([2601:647:5600:5020:25f2:6a5c:8d81:dca9]) by smtp.gmail.com with ESMTPSA id w26sm927665pgl.50.2021.05.14.09.17.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 May 2021 09:17:01 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4D72277F-C1E5-440F-A54B-3F4422E17AED"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Fri, 14 May 2021 09:17:00 -0700
In-Reply-To: <609E4ED3.5010101@btconnect.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/lGA380PhI7o77BV6aDXArvFz9ls>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 16:17:09 -0000

--Apple-Mail=_4D72277F-C1E5-440F-A54B-3F4422E17AED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tom,

Can you point to something specific? Thanks.

> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com> wrote:
>=20
> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>> This has been addressed in -10 version of the draft. Cheers.
>=20
> Indeed it has.
>=20
> I note that some YANG clauses have [references] in them which are =
likely not plain text; doubtless that will be fixed at some point in the =
process.
>=20
> Tom Petch
>>=20
>>> On Apr 12, 2021, at 1:38 AM, tom petch <daedulus@btconnect.com> =
wrote:
>>>=20
>>> This I-D introduces a new and unnecessary YANG prefix in defiance of =
BCP216 s.4.2.
>>>=20
>>> It imports ietf-yang-types, perhaps the most widely imported module =
in the world, and RFC6991, where that module is specified, defines the =
proper prefix as 'yang'.  This I-D invents a different one. Technically, =
YANG can cope with this but that does not make it a sensible thing to =
do.
>>>=20
>>> Tom Petch
>>>=20
>>> On 08/04/2021 13:43, The IESG wrote:
>>>>=20
>>>> The IESG has received a request from the Babel routing protocol WG =
(babel) to
>>>> consider the following document: - 'YANG Data Model for Babel'
>>>>   <draft-ietf-babel-yang-model-09.txt> as Proposed Standard
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and =
solicits final
>>>> comments on this action. Please send substantive comments to the
>>>> last-call@ietf.org mailing lists by 2021-04-22. Exceptionally, =
comments may
>>>> be sent to iesg@ietf.org instead. In either case, please retain the =
beginning
>>>> of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>=20
>>>>    This document defines a data model for the Babel routing =
protocol.
>>>>    The data model is defined using the YANG data modeling language.
>>>>=20
>>>>=20
>>>>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_4D72277F-C1E5-440F-A54B-3F4422E17AED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Tom,<div class=3D""><br class=3D""></div><div class=3D"">Can you point =
to something specific? Thanks.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On May =
14, 2021, at 3:20 AM, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
12/05/2021 21:46, Mahesh Jethanandani wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">This has been addressed in -10 version of the =
draft. Cheers.<br class=3D""></blockquote><br class=3D"">Indeed it =
has.<br class=3D""><br class=3D"">I note that some YANG clauses have =
[references] in them which are likely not plain text; doubtless that =
will be fixed at some point in the process.<br class=3D""><br =
class=3D"">Tom Petch<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Apr =
12, 2021, at 1:38 AM, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">This I-D introduces a new and unnecessary YANG prefix in =
defiance of BCP216 s.4.2.<br class=3D""><br class=3D"">It imports =
ietf-yang-types, perhaps the most widely imported module in the world, =
and RFC6991, where that module is specified, defines the proper prefix =
as 'yang'. &nbsp;This I-D invents a different one. Technically, YANG can =
cope with this but that does not make it a sensible thing to do.<br =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D"">On =
08/04/2021 13:43, The IESG wrote:<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">The IESG has received a request from the Babel =
routing protocol WG (babel) to<br class=3D"">consider the following =
document: - 'YANG Data Model for Babel'<br class=3D""> =
&nbsp;&nbsp;&lt;draft-ietf-babel-yang-model-09.txt&gt; as Proposed =
Standard<br class=3D""><br class=3D"">The IESG plans to make a decision =
in the next few weeks, and solicits final<br class=3D"">comments on this =
action. Please send substantive comments to the<br class=3D""><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a> =
mailing lists by 2021-04-22. Exceptionally, comments may<br class=3D"">be =
sent to <a href=3D"mailto:iesg@ietf.org" class=3D"">iesg@ietf.org</a> =
instead. In either case, please retain the beginning<br class=3D"">of =
the Subject line to allow automated sorting.<br class=3D""><br =
class=3D"">Abstract<br class=3D""><br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;This document defines a data model for the Babel =
routing protocol.<br class=3D""> &nbsp;&nbsp;&nbsp;The data model is =
defined using the YANG data modeling language.<br class=3D""><br =
class=3D""><br class=3D""><br =
class=3D""></blockquote></blockquote></blockquote></div></div></blockquote=
></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_4D72277F-C1E5-440F-A54B-3F4422E17AED--


From nobody Fri May 14 09:34:59 2021
Return-Path: <daedulus@btconnect.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCB13A3858; Fri, 14 May 2021 09:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 VaTOohzoJvgR; Fri, 14 May 2021 09:34:49 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2133.outbound.protection.outlook.com [40.107.22.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811373A3855; Fri, 14 May 2021 09:34:49 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OXDX29gzsrD5sJBcuCmSCxyQXCRJS8hAV8dywx00BWLZUsZLO9gZcWSBMzBejlMAh+7tno/AnIPBmgIAUkPHGdTBi28YiL3SScP8PVCeRUflZdEtl6Cmi9XfmpX9lcGqLRkzjyamwehYSrXAXt+u1WTJwwGxGHXonRS9+hZXETM/i0Szz48FNEejI5xx4ZrnEXCb49+k/xnsGY3qAdBVG6Z3kTwJwxTK4pn11ZToI+yukcBhLMHzdAfYSytI6jQu4hxWWfHs2Ns12qeyvaE4kf7XeC79M1jzv3nC1B2Hvu0azAUvwWGh1G03sW4M6EeY4eukPJK2oS9xnz+K86aQ1w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pMTf441kbdpAmiEWPWIOS2YvrwFi9Odonr1qw6aFoUs=; b=mq4qNS4nytY84OBEIPOFPny92AIqVmFwleK1Cy29rbwH8l2W7+Xn8zuIqG+wVtR+4a3jQT0GgGcSU9EcZWTnIH+eztigx2rkaJLm4UYd5M3ex65hUFwIwGGgFRVPE8X3rMTgUqOKXbCJqrWFnr0COOj3YhQyMFPPD0V4VU4Wvgn/UvS2SkAGhYpuGiuysXT3AEK4CF3ahNax7b66IhWSIpf6ZA1WkZdaZ7YCG7VR1Sp5oSFHY2azPEVILAQ1xG/7ce9gDRL7TJ1XFPY8YNzItm/pXx8B9LhCqZ++0BgjtMP4xWdlKongrZtE0Mdl6hPqje4kfc0KeTHrktsMHFOK9Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pMTf441kbdpAmiEWPWIOS2YvrwFi9Odonr1qw6aFoUs=; b=hZxiEC5QQ9/MII63KlmAs9NAU9uPm2lidr6HTRAVU8pXa6BI8KmhkI/Kh2TfMxwj7Yfk+lCc2zGRYe0esjIpgJBsDJt9pk8SKkqoMHm0LWW0scGfumZhs+gVGR3xjJzGr2eF8bHcFqsCLWHLyxbwCCf5L8LGXrMjjx/GI/+Kjt8=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB6448.eurprd07.prod.outlook.com (2603:10a6:800:138::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.12; Fri, 14 May 2021 16:34:47 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4150.011; Fri, 14 May 2021 16:34:47 +0000
To: Mahesh Jethanandani <mjethanandani@gmail.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com> <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <609EA6A3.1040303@btconnect.com>
Date: Fri, 14 May 2021 17:34:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.143.250.49]
X-ClientProxiedBy: LO4P123CA0354.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:18d::17) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.143.250.49) by LO4P123CA0354.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:18d::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4108.25 via Frontend Transport; Fri, 14 May 2021 16:34:46 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: bf724a60-98dd-4b8e-8d1c-08d916f62fca
X-MS-TrafficTypeDiagnostic: VI1PR07MB6448:
X-Microsoft-Antispam-PRVS: <VI1PR07MB644834527FA6129D6CC6FB8CC6509@VI1PR07MB6448.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: /leSExcjPNyYpCHioJuauUqKSEIbq3qmc2yXIM0mSGTPmYM+k1EuIyBMxNXnOS639Z91FwKamFP7NpTQuaCJ7XSw7YWjqLWDvLFQk0kI0+sTiYzJ3s1Kf8V8JofjcMFU+sRLf2kPuQ4023apY/NQte4FBK/oNPa/7236EPRgnl5q1PaLaaiHoZ1xE/WDrGxTg18o1Ikiv59OHoIE7pqQWoOXX/j6BNkhdkBsbzNkuo/FmZUPn99BFlOPhr+HO8Bw0SAxWfbSDJeweTOb/uReayxiwRAL33H/mNlAd5YW7FCI7d+yxmNVxGUCl9mEIXuzrSFUbH6ukv75tShw9uWsBCD2wmBF9IP6GIxDPBHD6uvwfCl9yIKi3WEpiQCQNRYuntkHsp/NxQihS2b8YF/pbHJCQb1HwOPOJyweo+Pj7zUzI0JmYt/P7tYj1sHdZiONYG96ePd6yVSH2iIeJawxx/02BJrHqPMjRegjv4EnMZ7iTcGAEarDg46AaBSlTmiKU6LHLnxu+A/nHo0R+FuMMjTi7b0CWPJ7i0+w/1VELUWKadPNvr/B9cd8fkgPx+mT9GoBTsHIGOknUIm3NYPxaQL2yoRJTmbeTEDN2vswWnBC9X6qQe8XOmuFvYefVcCbE1TQehU1STPDg3i++SlZNA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(376002)(346002)(136003)(366004)(39860400002)(2906002)(26005)(2616005)(956004)(8936002)(478600001)(36756003)(6916009)(66476007)(52116002)(87266011)(66556008)(53546011)(33656002)(6486002)(83380400001)(5660300002)(66946007)(38350700002)(316002)(16576012)(38100700002)(6666004)(186003)(8676002)(86362001)(16526019)(4326008); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?Windows-1252?Q?HD0ofts2/22hs/ZwbfNLv4hrN5QHZ6Ft33Dhs7G0XnFoBptXIVuVkqDu?= =?Windows-1252?Q?e/aucyrFt0hqZCNxrBtR0rv9DeNZ+NBy17DGSBRvlF4l6Y3rMDpxBOYT?= =?Windows-1252?Q?Is42To+0rWWY52vEwc1rOxbdH/OA3Zmp9ko0GOASbVAYw0uMXnZWdigX?= =?Windows-1252?Q?j0eyHvgxH2pBPGPU98/o/CQ3Ode4VA2VRXVi5a7ewIx+P/BWAd9v7q5f?= =?Windows-1252?Q?LczIDfAY2lYObuQ1qNvlIIpq+B5wf9kxhFU94/s+yLHrbUirJB2/b9Ug?= =?Windows-1252?Q?OOknd2oRGLoWpVG55CoWvQIh7tAD7GqzNm+ES+umV5Y1repjqhW6dScH?= =?Windows-1252?Q?fkOi3Y6gLtEyqbMjKm26Wdn7IeS07X/L57eRbO1r8UxkftH346bJpFxT?= =?Windows-1252?Q?RTxgUTHSXP8f9np8KzeFL9h0lJnvLDOPBZhPcImvPBQuwM9daKyBTVA3?= =?Windows-1252?Q?ckeJesC1+UZbZz98Tk+FU1Kfw5XY9sP4sEzmAJAXgEQ0cK9s6ZGLOZbp?= =?Windows-1252?Q?8Y3k5SWIifjm14i8q7JO/xo1F2D9T10MAxg9eo4bmTlbi5QvxXyOmkjf?= =?Windows-1252?Q?oD9XdAvxVqAw17eQDLYILXpDXMZqOJU8WbRfq5PgZ2QE9rpvv9zkT8L3?= =?Windows-1252?Q?byjSHDUQDm8lpOAKvVaOOdMdlrcd7Gz/oxJWHN2OD/rqNh0HqgI+i7+G?= =?Windows-1252?Q?Iock5TZ96UM5Ru0YfHdPh+DbUJdyP+OAi7hgt0aPqRmpYUft3FNP1rxA?= =?Windows-1252?Q?i87AZLEMGatVgL8p59Qj5nDBrwEO4vGc1+o089UKOHRBYcEsfSIIYii0?= =?Windows-1252?Q?ks6ReQK6/8fhNsC3aXii+7LXQ9T9kdr5fQ3ZR3UbO7VEsm4KAD7G0hKF?= =?Windows-1252?Q?GQzgW58z59ZJKqe7ggQ1c3I1tnGFQTg58m5GoVMBN1cDa1nPbIRSASvJ?= =?Windows-1252?Q?oQ/t3XJH8F1r6i8Euf3LYbzBE5JsrjiBY7QSXTQzUxOzc4hoo7sIzuqk?= =?Windows-1252?Q?NklDq59pYJYhJSHqovBERAiOuionlhVjyQEZYIHT5mfF3yt+0eQ84yjA?= =?Windows-1252?Q?DdzFqu7xakDsZN6dOy35Hc9FZhyaiMQ/6uo9qL+YhQJxHlbVAyEWF0x8?= =?Windows-1252?Q?PywNOoAmODO8LS3yTdRyBK9pMQYR6uo1WhTNt5oJ9t2IP6Hdg0ZG4fgF?= =?Windows-1252?Q?ODgRNNbGp7Cv0x+KyahxABub01S6/itvndqjQI/LmaYNDSe1qWgHPmEH?= =?Windows-1252?Q?98sXUpFSNQddFSLPt8e3NUbZF9LokP9gPVm3K5F1ew02Fc5wkqBBqetd?= =?Windows-1252?Q?W5olkVVCLjxQU00K36w3Lf7xaRpClfkbxrrK11MLfH/0NPGmWH8XA36P?= =?Windows-1252?Q?M6V0+gu5TMqkQs5EqkSsB+s12hcc88kdAtiv+USJu1e5F4OELk19Qvp2?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bf724a60-98dd-4b8e-8d1c-08d916f62fca
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 May 2021 16:34:47.0987 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: GHZ1gqbSOVKh7xd2EJuAt6suKl+0j/7Mn0uxZVJwmNeX3UO5beXBlYewwpR9gCoDUW5P6ArZjkCaixu/gPAgyw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB6448
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/K_z2l4h083uh-ol7LLTkNHSCpQ0>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 16:34:55 -0000

On 14/05/2021 17:17, Mahesh Jethanandani wrote:
> Hi Tom,
>
> Can you point to something specific? Thanks.


action reset
...[RFC ZZZZ]
...
leaf value
[RFC2104]...[RFC4868]... [RFC8697]...  [RFC7693]
...
leaf value
[RFC7468]

Tom Petch



>
>> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com>
>> wrote:
>>
>> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>>> This has been addressed in -10 version of the draft. Cheers.
>>
>> Indeed it has.
>>
>> I note that some YANG clauses have [references] in them which are
>> likely not plain text; doubtless that will be fixed at some point
>> in the process.
>>
>> Tom Petch
>>>
>>>> On Apr 12, 2021, at 1:38 AM, tom petch
>>>> <daedulus@btconnect.com> wrote:
>>>>
>>>> This I-D introduces a new and unnecessary YANG prefix in
>>>> defiance of BCP216 s.4.2.
>>>>
>>>> It imports ietf-yang-types, perhaps the most widely imported
>>>> module in the world, and RFC6991, where that module is
>>>> specified, defines the proper prefix as 'yang'.  This I-D
>>>> invents a different one. Technically, YANG can cope with this
>>>> but that does not make it a sensible thing to do.
>>>>
>>>> Tom Petch
>>>>
>>>> On 08/04/2021 13:43, The IESG wrote:
>>>>>
>>>>> The IESG has received a request from the Babel routing
>>>>> protocol WG (babel) to consider the following document: -
>>>>> 'YANG Data Model for Babel'
>>>>> <draft-ietf-babel-yang-model-09.txt> as Proposed Standard
>>>>>
>>>>> The IESG plans to make a decision in the next few weeks, and
>>>>> solicits final comments on this action. Please send
>>>>> substantive comments to the last-call@ietf.org mailing lists
>>>>> by 2021-04-22. Exceptionally, comments may be sent to
>>>>> iesg@ietf.org instead. In either case, please retain the
>>>>> beginning of the Subject line to allow automated sorting.
>>>>>
>>>>> Abstract
>>>>>
>>>>>
>>>>> This document defines a data model for the Babel routing
>>>>> protocol. The data model is defined using the YANG data
>>>>> modeling language.
>>>>>
>>>>>
>>>>>
>
> Mahesh Jethanandani mjethanandani@gmail.com
>
>
>
>
>
>


From nobody Fri May 14 09:59:21 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632AA3A3904; Fri, 14 May 2021 09:59:19 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 QUbnXj7d9dO2; Fri, 14 May 2021 09:59:14 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 6315B3A3902; Fri, 14 May 2021 09:59:14 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id k15so11753340pgb.10; Fri, 14 May 2021 09:59:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3AU+//ukumQNIURdkuFGEGXbWbC6PNl6N342++9Bink=; b=cX7rfWGHV/YQYnUE+CFseE7uCfhlRQgw0XJhgb/e95IRfJWhot6vVI9N4ygciGbXPd nm3MuKOGu9RH0zvpCqrHpF5u8LtHrJLTndmGWBu+gbZyS9dpw1ypL418suUgL1IMPtRS HE0cfLezpjmLzk31jHPCymkgScqAfqHIR3nUpAxAPmKWYvvrkjJ+b2JRuy2cQUOg9fl5 pIJP0Q06yhltPHRhS92wuOZ5tzfLRigov0ltLxcCfPms42AT05lEZMXm75txEAFzFPj1 m/4ZfYlGj1WvyJ0B/2SQPyeIzVASF0eN+PtTXkE0nySTxsAFugmjZC/Lu2Kaop9BfByh 6jhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3AU+//ukumQNIURdkuFGEGXbWbC6PNl6N342++9Bink=; b=qcjIWffmFJMMkwze+kFLwmL9fiHH45rDMFkdQ0pCnnOAxQzeXuoqBvpwQ5/q14AI7v pJ3yIXwvXPoDrFk/zDdsYFkYzeD+ZJ0tG0bXUJ2V22f/w941JndrdNt9raApDZZyEH0W CTiSdCiePgCPWWXw+y5RfK3L381qemLp10oWB4fgH4vHNDGKJk96iXicXpAcZSEs8lbZ LwEbc3wYOIzt30JId9ByYDNy3FRSOjZll/kKMuDRvS6a7a3eJtM9EY+8ul+BCQ4sn5lx gbZyTqE+3QwIXiP6+Md4iLaSMmVK0YMB4Svae3bgUX/E2i65YE3AvxfSPCOb6M70pBW9 lqEA==
X-Gm-Message-State: AOAM531zb1CV2pfxNd4h7TQbkH00hLo9BHHo138c+IibQV7dOcqW2u4C ZJged7J/SDakQryCCeXuj3E=
X-Google-Smtp-Source: ABdhPJxtbEQUn0GxD4VBSoI3kAvr0YAzdAUDO6R3N8YFj81A8wbA7qyTTXoc7MgrUbSrV38OU1v7sA==
X-Received: by 2002:a62:31c4:0:b029:28d:1ad0:340c with SMTP id x187-20020a6231c40000b029028d1ad0340cmr45794172pfx.35.1621011553502;  Fri, 14 May 2021 09:59:13 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:25f2:6a5c:8d81:dca9? ([2601:647:5600:5020:25f2:6a5c:8d81:dca9]) by smtp.gmail.com with ESMTPSA id h3sm2126908pfh.114.2021.05.14.09.59.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 May 2021 09:59:12 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <185C6A7C-D5D8-4FAB-BCBB-62525CBCBDDC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_82B09E43-39EC-450A-86EE-E636B99D248E"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Fri, 14 May 2021 09:59:11 -0700
In-Reply-To: <609EA6A3.1040303@btconnect.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com> <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com> <609EA6A3.1040303@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/_JyoyYDPSIDKcqvgzi8gXiAhRS8>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 16:59:20 -0000

--Apple-Mail=_82B09E43-39EC-450A-86EE-E636B99D248E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tom,

Are you suggesting that there should be no references to RFC numbers in =
the description statement? Note, the reference statement that follows =
the description statement has the complete reference to the RFC which is =
being cited in the description statement.

Cheers.

> On May 14, 2021, at 9:34 AM, tom petch <daedulus@btconnect.com> wrote:
>=20
> On 14/05/2021 17:17, Mahesh Jethanandani wrote:
>> Hi Tom,
>>=20
>> Can you point to something specific? Thanks.
>=20
>=20
> action reset
> ...[RFC ZZZZ]
> ...
> leaf value
> [RFC2104]...[RFC4868]... [RFC8697]...  [RFC7693]
> ...
> leaf value
> [RFC7468]
>=20
> Tom Petch
>=20
>=20
>=20
>>=20
>>> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com>
>>> wrote:
>>>=20
>>> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>>>> This has been addressed in -10 version of the draft. Cheers.
>>>=20
>>> Indeed it has.
>>>=20
>>> I note that some YANG clauses have [references] in them which are
>>> likely not plain text; doubtless that will be fixed at some point
>>> in the process.
>>>=20
>>> Tom Petch
>>>>=20
>>>>> On Apr 12, 2021, at 1:38 AM, tom petch
>>>>> <daedulus@btconnect.com> wrote:
>>>>>=20
>>>>> This I-D introduces a new and unnecessary YANG prefix in
>>>>> defiance of BCP216 s.4.2.
>>>>>=20
>>>>> It imports ietf-yang-types, perhaps the most widely imported
>>>>> module in the world, and RFC6991, where that module is
>>>>> specified, defines the proper prefix as 'yang'.  This I-D
>>>>> invents a different one. Technically, YANG can cope with this
>>>>> but that does not make it a sensible thing to do.
>>>>>=20
>>>>> Tom Petch
>>>>>=20
>>>>> On 08/04/2021 13:43, The IESG wrote:
>>>>>>=20
>>>>>> The IESG has received a request from the Babel routing
>>>>>> protocol WG (babel) to consider the following document: -
>>>>>> 'YANG Data Model for Babel'
>>>>>> <draft-ietf-babel-yang-model-09.txt> as Proposed Standard
>>>>>>=20
>>>>>> The IESG plans to make a decision in the next few weeks, and
>>>>>> solicits final comments on this action. Please send
>>>>>> substantive comments to the last-call@ietf.org mailing lists
>>>>>> by 2021-04-22. Exceptionally, comments may be sent to
>>>>>> iesg@ietf.org instead. In either case, please retain the
>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>=20
>>>>>> Abstract
>>>>>>=20
>>>>>>=20
>>>>>> This document defines a data model for the Babel routing
>>>>>> protocol. The data model is defined using the YANG data
>>>>>> modeling language.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>=20
>> Mahesh Jethanandani mjethanandani@gmail.com
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_82B09E43-39EC-450A-86EE-E636B99D248E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Tom,<div class=3D""><br class=3D""></div><div class=3D"">Are you =
suggesting that there should be no references to RFC numbers in the =
description statement? Note, the reference statement that follows the =
description statement has the complete reference to the RFC which is =
being cited in the description statement.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Cheers.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On May =
14, 2021, at 9:34 AM, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
14/05/2021 17:17, Mahesh Jethanandani wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">Hi Tom,<br class=3D""><br class=3D"">Can you =
point to something specific? Thanks.<br class=3D""></blockquote><br =
class=3D""><br class=3D"">action reset<br class=3D"">...[RFC ZZZZ]<br =
class=3D"">...<br class=3D"">leaf value<br =
class=3D"">[RFC2104]...[RFC4868]... [RFC8697]... &nbsp;[RFC7693]<br =
class=3D"">...<br class=3D"">leaf value<br class=3D"">[RFC7468]<br =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On May 14, 2021, at 3:20 =
AM, tom petch &lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt;<br class=3D"">wrote:<br =
class=3D""><br class=3D"">On 12/05/2021 21:46, Mahesh Jethanandani =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">This has been =
addressed in -10 version of the draft. Cheers.<br =
class=3D""></blockquote><br class=3D"">Indeed it has.<br class=3D""><br =
class=3D"">I note that some YANG clauses have [references] in them which =
are<br class=3D"">likely not plain text; doubtless that will be fixed at =
some point<br class=3D"">in the process.<br class=3D""><br class=3D"">Tom =
Petch<br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On Apr 12, 2021, at 1:38 =
AM, tom petch<br class=3D"">&lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">This I-D introduces a new and unnecessary YANG prefix in<br =
class=3D"">defiance of BCP216 s.4.2.<br class=3D""><br class=3D"">It =
imports ietf-yang-types, perhaps the most widely imported<br =
class=3D"">module in the world, and RFC6991, where that module is<br =
class=3D"">specified, defines the proper prefix as 'yang'. &nbsp;This =
I-D<br class=3D"">invents a different one. Technically, YANG can cope =
with this<br class=3D"">but that does not make it a sensible thing to =
do.<br class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D"">On=
 08/04/2021 13:43, The IESG wrote:<br class=3D""><blockquote type=3D"cite"=
 class=3D""><br class=3D"">The IESG has received a request from the =
Babel routing<br class=3D"">protocol WG (babel) to consider the =
following document: -<br class=3D"">'YANG Data Model for Babel'<br =
class=3D"">&lt;draft-ietf-babel-yang-model-09.txt&gt; as Proposed =
Standard<br class=3D""><br class=3D"">The IESG plans to make a decision =
in the next few weeks, and<br class=3D"">solicits final comments on this =
action. Please send<br class=3D"">substantive comments to the <a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a> =
mailing lists<br class=3D"">by 2021-04-22. Exceptionally, comments may =
be sent to<br class=3D""><a href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a> instead. In either case, please retain =
the<br class=3D"">beginning of the Subject line to allow automated =
sorting.<br class=3D""><br class=3D"">Abstract<br class=3D""><br =
class=3D""><br class=3D"">This document defines a data model for the =
Babel routing<br class=3D"">protocol. The data model is defined using =
the YANG data<br class=3D"">modeling language.<br class=3D""><br =
class=3D""><br class=3D""><br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br =
class=3D"">Mahesh Jethanandani <a href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D""></blockquote></div></div></blockquote></div><br class=3D""><div=
 class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_82B09E43-39EC-450A-86EE-E636B99D248E--


From nobody Sat May 15 04:06:46 2021
Return-Path: <daedulus@btconnect.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8F23A22F1; Sat, 15 May 2021 04:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 Z3m0rJjuvCrD; Sat, 15 May 2021 04:06:39 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2133.outbound.protection.outlook.com [40.107.20.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A9F43A22EF; Sat, 15 May 2021 04:06:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BI49fhqvC3skVARsVCcOIdDUDIla3dD5YYrl8q8q1Kdq7csceLi60xGH9dxBOwIjDoQpzJyi6o3mbfl0jkfedZgeyjdjhH9PXf/kR6gKUGfrlZOPyosg3Wlj6aFyRx4Rtti0E5N3o3OHkAEAqXuR2ntY7XRvbbpfTPF/6Pqds6vjSd64YCkKCjmYHO+4mCXgHLmvlPJvcwqu/ctqMxCBuOTLZtzgNnkqBjDbVsGRHiqp5PxTxfzHlVvam1W40HPJc/lv8kq1FCx0SP/5iu5Ohp143p8FY3LLtB7Y2Hq5VSle3Hb/0yR55JUn5xaQAq6j/UA5Y/eU5Q8oZnRnR9coPQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=z8qozeLiRXRkGrFsCD4gO1FZD8L/JzzpqvrQWM2d1+8=; b=AjGyAGqvJt7W37hA/EFMumeEc74BvCALaThNpYDHZjjmN+ujP0d56vZ/3doWfrEc8tS4/+VFulY0hlVlwiy/ci7e2TsyV4F3yvGNz78l7cjCuboIVELzhkbrTJQouuaMNpptX4mm1n79azdNMy/CnhXTti3wVUOwe7Zt2YFd8BBa9p0O5yXkEU3XczJ+ACW8jxcNrKdA4bOC5YEO+5t8JWM9Jg40JFKcdxvTr3Sl0IGR7yGQ9PeN6i8PJ7Rhg44vB7B24JU4Nke+B6E7DZEGwVauVx0cOY5Hznf6CStaug1hMVSqbApOZydPJ5gd30k4JUQJgkVd0ByG7pRsAu/eOQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=z8qozeLiRXRkGrFsCD4gO1FZD8L/JzzpqvrQWM2d1+8=; b=mW7N2hMIApntaW9A42CdgvBAOfl/HeIEiATDaKk9dAAqR0SUc1NVvtR+78yCBz/2kfAEqSgmRRUEbzm28UoE2BzI426Z7zMgQDVm0MFPCOxLtLmkkT+R/nRQ+EeP9LKGovoE7753Xn4+vqM59c0BlahsYRo0b1QAgIXMzid8yfI=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB2221.eurprd07.prod.outlook.com (2603:10a6:800:22::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.11; Sat, 15 May 2021 11:06:31 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4150.011; Sat, 15 May 2021 11:06:31 +0000
To: Mahesh Jethanandani <mjethanandani@gmail.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com> <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com> <609EA6A3.1040303@btconnect.com> <185C6A7C-D5D8-4FAB-BCBB-62525CBCBDDC@gmail.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <609FAB33.4000201@btconnect.com>
Date: Sat, 15 May 2021 12:06:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <185C6A7C-D5D8-4FAB-BCBB-62525CBCBDDC@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.143.250.49]
X-ClientProxiedBy: LO4P123CA0477.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:1a8::14) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.143.250.49) by LO4P123CA0477.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:1a8::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4108.25 via Frontend Transport; Sat, 15 May 2021 11:06:30 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 13f192bf-947a-40af-a588-08d917917e61
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2221:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB22212AC2E7920E71B4C2D8B3C62F9@VI1PR0701MB2221.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: JYNIDyf/3l7LSeSgFiteCGEWVLLp62gjYTf24Ja3B74S7Q0YbGcmeET9kVO6lTaDjgBNeLSGMlsEMMs9s0+QE1XDz/H2RbcbT6f3iUrjRCNo1ObyeNa6rFlpO873dhHVzUeQqqGOlhib2reQklGHYBgvg2SKRkwl95Mx5izbAIJUYlAbSqL6JICkChIR4pX3Sbdw40f2Uhjsim5fcyUStK8VuoGdBnqARdxQqe86WwDR3HCc1hhNKnGdvrWMgKBOjqIkvhEcYml2U/c7kC/9AeoSxapDmlv9r0Ub2G7mOZHqqEQqKGtawkOrFZksil7Mc5a/TcNHKw/bGZFxGi1DD5PlxC5DErGhg0LsTLYslr9jddMce2l1i3/QdcvB4sqAf9WhVHEdOmAJdMxM5hZb1NelPS+9Uw4Z4Aprc+0vD/dZitVJMJyaShqguYi76R4Q+8hn3j0wB1/Uxbj5dRVwyytrBqXrj/JX0l4ZbjCgtCX6X6Iy9cQF74VvCyUepUtKLCvrtFLc2vk4948Xq4VED9OIQ3cAeR+5klYI0nY4K4s/8sbJM6PCwQpxK+bRNmXBEpIP9+JEMe+9guYV+jTWFOZg/GN2aaGQymc3Ua72ngkeP857zElSzUtOwW8+gLPWycrv78MKDDwwCVD5jFVn2w==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(366004)(376002)(39860400002)(346002)(136003)(26005)(2616005)(52116002)(8676002)(87266011)(2906002)(38100700002)(66946007)(53546011)(956004)(66476007)(6666004)(36756003)(16526019)(16576012)(6486002)(478600001)(186003)(5660300002)(33656002)(6916009)(86362001)(316002)(8936002)(38350700002)(66556008)(4326008); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?Windows-1252?Q?UiIvX5hb+BEEc1u9MiPqFIULg3fN6AmCViAFaJASb3TfkVWLhTxH0sCH?= =?Windows-1252?Q?zsdbuQ2SS/UvdLF452WYe1igEW2WIs4n1UISNfBg2A3FSN/ndvvf2/Bm?= =?Windows-1252?Q?MNVlVyGJN+pad6DSmIZxh8G6s/Tw2kVu7FQmqCxRlHJFliEHIJZQ837u?= =?Windows-1252?Q?MT71iUrAH/CdauhprxSWkrfQLPHZ+w+FobxhbFsoCmEla51uRz8K/aCF?= =?Windows-1252?Q?6nkn+OD7jGlwR10xFqwU4gvJ76zJ5lStG+gE5MhJLvx/dfWDwQ3vlOSn?= =?Windows-1252?Q?1I+p5rXh8mFj6cOw2RqYy7fz9g+kQjMWLZKkGvxmQmKQcBsaQYB0Re8y?= =?Windows-1252?Q?3kUCVby87cHFHB6ENtOu7vlxFToYXOr23ZIVMHAa2uXyD6osmFuGYiv8?= =?Windows-1252?Q?qPZwuWTAidjxkkpEvJgkHUnOJ9VDlEF74icWkdlLoa+bkIi5R4U9Yrer?= =?Windows-1252?Q?+VXIonb6Z0vbhflzEv9a3Gp4sRtMGnmi32mL7XbgWD5nSVaD8k0Fb9nC?= =?Windows-1252?Q?LOWjWUm4G3YAcLz7JEshqFvbyCnOBoIeIPLvDfXrYB78mA6EZ3F98kB6?= =?Windows-1252?Q?g2+a5+kvYVLA2cRZwmAb+8OcPpYKoFmjpVHXKX54BuOVrs1ySa3Q9v0/?= =?Windows-1252?Q?QOP2cPWnwCJUdo9mCtRbwJ4IKyenYW9lpA5JhFY96nP69pSjKqgIv12R?= =?Windows-1252?Q?EHsUJ+W5XLK/h+364o3mkJTeCzXo4U0DVGVh9f+FMbmiTjiPMMRdsDfE?= =?Windows-1252?Q?YXBEJcqC7Z3IEp5GevTwO1GBLATB6g6Jjz3W0zCN66tvPlORWp7oXTQ4?= =?Windows-1252?Q?wMuS57KBQUH52/NRN1Sw6bloBfIg3G/meD7YCQgxI0a1R0U2JTCg98lH?= =?Windows-1252?Q?yNjDkmPg+Fq2FI8kGIXHy9x0rR48CCAvkDz6PqIAbSsLI1IKkCwZs+BC?= =?Windows-1252?Q?tJLlG+Q/fOSbjTnTmLWwlYzkzq4j6MzbzhX6aCeb9JRzpOdgE0EcqlZv?= =?Windows-1252?Q?7OYQ5sNLIf3mkqI/wERc/vOS9RuXTJm9wLrxkO5hngL+TYlA0NDPHOZ+?= =?Windows-1252?Q?Ah0MFqjhNU6X5FSJWG6qi25xjSu7PQ11UaYvAb+rxe66ZWYZdXPzWlwa?= =?Windows-1252?Q?cYNf1NByFNB5OKU6gLTD5PymDELPPdveB/fHBOZbExBdILpvDUWmoUfL?= =?Windows-1252?Q?T7jE8V+xNfs8flCtuIh480fe9+NakFuz6yfskCOPwejDYbFP1+tdCgCP?= =?Windows-1252?Q?p8NOZRukNPIluFnUTc04U6Hc3mCMaf+A7pIl4WweIBC48NsI7MFSHIWw?= =?Windows-1252?Q?n1A2oPmbAX0IRkiBeEPw68fXcYmsqxBiKB78oYbmhXEZ9ZnVu1zqgMBo?= =?Windows-1252?Q?ltzRHP6HgnjhQsu6cMiYdqVQFNzHSBWmensPJUO4D4WzUVlJlheOtEQt?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 13f192bf-947a-40af-a588-08d917917e61
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 15 May 2021 11:06:30.9542 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: oBVTsf5uu5k4XDM65qpYrApDg+VTzurSOpx4JfdywfMxv+0LG+Lt0NfLcaiQpNt7JiyG9y6K/jBkgMnjL3QLmg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2221
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/mm37icZIe54VP392NXx4f6ZGnYE>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 May 2021 11:06:44 -0000

On 14/05/2021 17:59, Mahesh Jethanandani wrote:
> Hi Tom,
>
> Are you suggesting that there should be no references to RFC numbers in the description statement? Note, the reference statement that follows the description statement has the complete reference to the RFC which is being cited in the description statement.

I am saying that [RFC ZZZZ] and such like are usually xML and not plain 
text and that a YANG module is required to be plain text as when it is 
extracted from the RFC and floats off on is own independent of the rest 
of the RFC.  The 'canonical form' of a YANG module is plain text!

Tom Petch

> Cheers.
>
>> On May 14, 2021, at 9:34 AM, tom petch <daedulus@btconnect.com> wrote:
>>
>> On 14/05/2021 17:17, Mahesh Jethanandani wrote:
>>> Hi Tom,
>>>
>>> Can you point to something specific? Thanks.
>>
>>
>> action reset
>> ...[RFC ZZZZ]
>> ...
>> leaf value
>> [RFC2104]...[RFC4868]... [RFC8697]...  [RFC7693]
>> ...
>> leaf value
>> [RFC7468]
>>
>> Tom Petch
>>
>>
>>
>>>
>>>> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com>
>>>> wrote:
>>>>
>>>> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>>>>> This has been addressed in -10 version of the draft. Cheers.
>>>>
>>>> Indeed it has.
>>>>
>>>> I note that some YANG clauses have [references] in them which are
>>>> likely not plain text; doubtless that will be fixed at some point
>>>> in the process.
>>>>
>>>> Tom Petch
>>>>>
>>>>>> On Apr 12, 2021, at 1:38 AM, tom petch
>>>>>> <daedulus@btconnect.com> wrote:
>>>>>>
>>>>>> This I-D introduces a new and unnecessary YANG prefix in
>>>>>> defiance of BCP216 s.4.2.
>>>>>>
>>>>>> It imports ietf-yang-types, perhaps the most widely imported
>>>>>> module in the world, and RFC6991, where that module is
>>>>>> specified, defines the proper prefix as 'yang'.  This I-D
>>>>>> invents a different one. Technically, YANG can cope with this
>>>>>> but that does not make it a sensible thing to do.
>>>>>>
>>>>>> Tom Petch
>>>>>>
>>>>>> On 08/04/2021 13:43, The IESG wrote:

>>>
>>> Mahesh Jethanandani mjethanandani@gmail.com
>>>
>>>
>>>
>>>
>>>
>>>
>
> Mahesh Jethanandani
> mjethanandani@gmail.com
>
>
>
>
>
>


From nobody Sun May 16 15:53:14 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CBEED3A1C37; Sun, 16 May 2021 15:53:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <162120558736.2547.14241878542030403927@ietfa.amsl.com>
Date: Sun, 16 May 2021 15:53:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/LjExZbLhpREHyANoX7dLifnvzNo>
Subject: [babel] Erik Kline's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 May 2021 22:53:08 -0000

Erik Kline has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Objection

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

[[ nits ]]

[ appendix A ]

* "An Appendix" is cute.  :-)

  Consider perhaps "Example Configurations" or just "Examples",
  if you haven't already.




From nobody Sun May 16 21:06:26 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC4173A257F; Sun, 16 May 2021 21:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 luFiAUJ1Tz11; Sun, 16 May 2021 21:06:15 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 28E0C3A257E; Sun, 16 May 2021 21:06:15 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id f22so2799400pgb.9; Sun, 16 May 2021 21:06:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ehVmmCv2oRaM9cRZnknyjRGs7DrvI7bcHlI5pqUkQAM=; b=qju0Yr0aL9OT5arkv144jIna/8ajdxpFHjAaqYGobjEGHrAyEyDKDFuNWihEYFDCLO 1S25y4MHi5beeGaxiJA9J2j+XcZrFInPH7fLEk1he0dEgDsFFR59H+kHYUpWQirRa86Y pZ3e2mB5+G9E41aOSFwm6lHEm27MUtX3TEc2SUmSn1xFEYjVX/OM33KiYGEgwsUOG+Ib AxqEnTXCJraaQIuAQfIsUALgaT0R3pSbmAl1Ofb7LcQQoDPsFuHUtHLYOHPCNZOjD08Z 7RBbsFQGoCFmFYK6vi/aQ2QTHTPFaok8lZtoGTuwpFO2eljHAuUQVicq7WBz1tYMQeq+ GNqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ehVmmCv2oRaM9cRZnknyjRGs7DrvI7bcHlI5pqUkQAM=; b=Y69ylUmGteDXgJAi5MPf/8fxEZASADIuHezzIBUmY+mdzShdBejsZ2FKWqDQyNetgp 8VHUoXxOadExH6+kiOashsacqNHpWYWzBHZkZ8+NVs1399PvehSOm8fFb4aPIWOyWWAB 081mfAWsHopbo7gBofK52BpJ4vpzN1F9t1S5d8g/+nZFFtdjMwzRgxLVFJRe05JBr17P bqtPU5iCaqqOurkO6VKlQx7M97sTuuobSmyz822vLcHwltA9pPG12o27I5hw4V/6E1RB 5oIeT8BTbEqzHgMQoPk8VWU3FNmbBQVm4VBtRZr7USDVoIHuUIYeyrBo9YQ84Pa6a/pJ KNOA==
X-Gm-Message-State: AOAM5303FOuH9l6k8CzlX2zFiO1EeLYlF0pTRvix13BPMtqoOTG33xyb epacG6yqhDtU2Zb0eLOkVvm4BUX1iMaMAg==
X-Google-Smtp-Source: ABdhPJz/kbT2cyZZ4KReyMo0/roPTW50k1nK50/Sgd4JtOVU/iHzVvKRJ/3yhpJgUTOSfp7Giog0hg==
X-Received: by 2002:a63:f717:: with SMTP id x23mr49554947pgh.141.1621224373679;  Sun, 16 May 2021 21:06:13 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:50a:2eca:7550:efd0? ([2601:647:5600:5020:50a:2eca:7550:efd0]) by smtp.gmail.com with ESMTPSA id k9sm9540343pgq.27.2021.05.16.21.06.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 May 2021 21:06:13 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <92805A4A-BADD-4C77-AA43-1623C61AF011@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A1243B0-049A-41CF-AD1C-21C5B3CEF4F7"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sun, 16 May 2021 21:06:10 -0700
In-Reply-To: <162120558736.2547.14241878542030403927@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: Erik Kline <ek.ietf@gmail.com>
References: <162120558736.2547.14241878542030403927@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/iU7vOkaJhGKlRHAJF6rYnSLN-Yc>
Subject: Re: [babel] Erik Kline's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 04:06:20 -0000

--Apple-Mail=_5A1243B0-049A-41CF-AD1C-21C5B3CEF4F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Erik,

Thanks for reviewing the document.

> On May 16, 2021, at 3:53 PM, Erik Kline via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Erik Kline has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> [[ nits ]]
>=20
> [ appendix A ]
>=20
> * "An Appendix" is cute.  :-)
>=20
>  Consider perhaps "Example Configurations" or just "Examples",
>  if you haven't already.
>=20
>=20

Changed it to =E2=80=9CExample Configurations=E2=80=9D.

Cheers.

>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_5A1243B0-049A-41CF-AD1C-21C5B3CEF4F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Erik,<div class=3D""><br class=3D""></div><div class=3D"">Thanks for =
reviewing the document.<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On May 16, 2021, at 3:53 PM, =
Erik Kline via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
class=3D"">noreply@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Erik =
Kline has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Objection<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">[[ nits ]]<br class=3D""><br =
class=3D"">[ appendix A ]<br class=3D""><br class=3D"">* "An Appendix" =
is cute. &nbsp;:-)<br class=3D""><br class=3D""> &nbsp;Consider perhaps =
"Example Configurations" or just "Examples",<br class=3D""> &nbsp;if you =
haven't already.<br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Changed it =
to =E2=80=9CExample Configurations=E2=80=9D.</div><div><br =
class=3D""></div><div>Cheers.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_5A1243B0-049A-41CF-AD1C-21C5B3CEF4F7--


From nobody Sun May 16 21:27:49 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015173A260B; Sun, 16 May 2021 21:27:48 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 vTvBGyK_DKpM; Sun, 16 May 2021 21:27:43 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 120BB3A260E; Sun, 16 May 2021 21:27:42 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id g18so2426975pfr.2; Sun, 16 May 2021 21:27:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ryPm4c/8D3JyjE9wIREXA8MySPKqDZ/5GgABio+TlyQ=; b=GVoY6Nfid0bUZRiO0HTphxK5XCibu9ZLKnnw34e29vdbKL9VJhEZgSYhvyMjPcVOe7 BuXxmFnEiohTY3eqnHVonZJj/P5P1ZwxsF63f2SMQaLCwPEEfJPhoIooxXaFmNMsqcBx j1iiEXDtNpOXNa4EoiUPOP14c8CPEb68Bds/XIeRgAtTHct1dJMlMt/d8yn/LP75fKVm +4a4UaU3LjLC7WQsO/i2VeO8DUSPHotptl01L6kwYOdcMwre5XqQVlKwiiV1ItVvOHZe Zwyiw4wERJ+JbHXW+ioE9TlAnMAYWv1UGmdU5SUpXdktsOcRWQvu+04W30SP1Fb6elwH dhcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ryPm4c/8D3JyjE9wIREXA8MySPKqDZ/5GgABio+TlyQ=; b=WMdVTgsGEX6l68/mbYNfJ1HS5kaAP5pJFmfhZqtFIk3FAk2WzMDOokf983HRAB56vF tTtIkeRUQQgu4OuazgWetz5LCqPGSTyVaeP3037wbDive5NnXj3fJg8PHtcW5oLfTA4w tyxNWkPZxNFqogI4qesbE64ACKIpQyPtjXeBGyrO3ptSkZ1rj2gKPYub5Y3FS0L0BsXv +4wHdvAIeVtYU6jiHhl5cQNEv90auEFZDiGggiKlYHzeloVxDckvj3+0CRMu6KI1z8XJ xhHwGScxsPSKBWCdWwIgdk74NQ+MuPhmKq+b7xFKqRvLdF1nNzpYthj7q2ZMhuVrxy8e Hl4Q==
X-Gm-Message-State: AOAM532JRRKSobH5kYuXNO6xJinHjugusZuyqiTTg5b6wqg1AjZ2Dlrc 5DOCE39G0SdvxYeROxVu330=
X-Google-Smtp-Source: ABdhPJxL7LJrv3fMls4/u64db8IVNnDeMB5af++u7PseuTvKQg7FPl4eohYVoXt16Npbz8dIrZ2NTQ==
X-Received: by 2002:a05:6a00:1a42:b029:2c5:3039:b62f with SMTP id h2-20020a056a001a42b02902c53039b62fmr1750203pfv.27.1621225661862;  Sun, 16 May 2021 21:27:41 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:50a:2eca:7550:efd0? ([2601:647:5600:5020:50a:2eca:7550:efd0]) by smtp.gmail.com with ESMTPSA id g8sm8775840pfo.85.2021.05.16.21.27.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 May 2021 21:27:41 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <411086E6-9BE0-4523-AD75-49C2E7F2D3D0@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_53F9345A-E3E6-4474-9218-89BA3DC24981"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sun, 16 May 2021 21:27:40 -0700
In-Reply-To: <609FAB33.4000201@btconnect.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com> <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com> <609EA6A3.1040303@btconnect.com> <185C6A7C-D5D8-4FAB-BCBB-62525CBCBDDC@gmail.com> <609FAB33.4000201@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/IXpkyeeSj_ViIHepjmVlVWs5uo4>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 04:27:48 -0000

--Apple-Mail=_53F9345A-E3E6-4474-9218-89BA3DC24981
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tom,

> On May 15, 2021, at 4:06 AM, tom petch <daedulus@btconnect.com> wrote:
>=20
> On 14/05/2021 17:59, Mahesh Jethanandani wrote:
>> Hi Tom,
>>=20
>> Are you suggesting that there should be no references to RFC numbers =
in the description statement? Note, the reference statement that follows =
the description statement has the complete reference to the RFC which is =
being cited in the description statement.
>=20
> I am saying that [RFC ZZZZ] and such like are usually xML and not =
plain text and that a YANG module is required to be plain text as when =
it is extracted from the RFC and floats off on is own independent of the =
rest of the RFC.  The 'canonical form' of a YANG module is plain text!

Where in RFC 7950 or RFC 8407 does it say that?

>=20
> Tom Petch
>=20
>> Cheers.
>>=20
>>> On May 14, 2021, at 9:34 AM, tom petch <daedulus@btconnect.com> =
wrote:
>>>=20
>>> On 14/05/2021 17:17, Mahesh Jethanandani wrote:
>>>> Hi Tom,
>>>>=20
>>>> Can you point to something specific? Thanks.
>>>=20
>>>=20
>>> action reset
>>> ...[RFC ZZZZ]
>>> ...
>>> leaf value
>>> [RFC2104]...[RFC4868]... [RFC8697]...  [RFC7693]
>>> ...
>>> leaf value
>>> [RFC7468]
>>>=20
>>> Tom Petch
>>>=20
>>>=20
>>>=20
>>>>=20
>>>>> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com>
>>>>> wrote:
>>>>>=20
>>>>> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>>>>>> This has been addressed in -10 version of the draft. Cheers.
>>>>>=20
>>>>> Indeed it has.
>>>>>=20
>>>>> I note that some YANG clauses have [references] in them which are
>>>>> likely not plain text; doubtless that will be fixed at some point
>>>>> in the process.
>>>>>=20
>>>>> Tom Petch
>>>>>>=20
>>>>>>> On Apr 12, 2021, at 1:38 AM, tom petch
>>>>>>> <daedulus@btconnect.com> wrote:
>>>>>>>=20
>>>>>>> This I-D introduces a new and unnecessary YANG prefix in
>>>>>>> defiance of BCP216 s.4.2.
>>>>>>>=20
>>>>>>> It imports ietf-yang-types, perhaps the most widely imported
>>>>>>> module in the world, and RFC6991, where that module is
>>>>>>> specified, defines the proper prefix as 'yang'.  This I-D
>>>>>>> invents a different one. Technically, YANG can cope with this
>>>>>>> but that does not make it a sensible thing to do.
>>>>>>>=20
>>>>>>> Tom Petch
>>>>>>>=20
>>>>>>> On 08/04/2021 13:43, The IESG wrote:
>=20
>>>>=20
>>>> Mahesh Jethanandani mjethanandani@gmail.com
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>> Mahesh Jethanandani
>> mjethanandani@gmail.com
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_53F9345A-E3E6-4474-9218-89BA3DC24981
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Tom,<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 15, 2021, at 4:06 AM, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
14/05/2021 17:59, Mahesh Jethanandani wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">Hi Tom,<br class=3D""><br class=3D"">Are you =
suggesting that there should be no references to RFC numbers in the =
description statement? Note, the reference statement that follows the =
description statement has the complete reference to the RFC which is =
being cited in the description statement.<br class=3D""></blockquote><br =
class=3D"">I am saying that [RFC ZZZZ] and such like are usually xML and =
not plain text and that a YANG module is required to be plain text as =
when it is extracted from the RFC and floats off on is own independent =
of the rest of the RFC. &nbsp;The 'canonical form' of a YANG module is =
plain text!<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Where in RFC 7950 or RFC 8407 does it say =
that?</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Tom Petch<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Cheers.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On May 14, 2021, at 9:34 =
AM, tom petch &lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">On 14/05/2021 17:17, Mahesh Jethanandani wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">Hi Tom,<br class=3D""><br =
class=3D"">Can you point to something specific? Thanks.<br =
class=3D""></blockquote><br class=3D""><br class=3D"">action reset<br =
class=3D"">...[RFC ZZZZ]<br class=3D"">...<br class=3D"">leaf value<br =
class=3D"">[RFC2104]...[RFC4868]... [RFC8697]... &nbsp;[RFC7693]<br =
class=3D"">...<br class=3D"">leaf value<br class=3D"">[RFC7468]<br =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On May 14, 2021, at 3:20 =
AM, tom petch &lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt;<br class=3D"">wrote:<br =
class=3D""><br class=3D"">On 12/05/2021 21:46, Mahesh Jethanandani =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">This has been =
addressed in -10 version of the draft. Cheers.<br =
class=3D""></blockquote><br class=3D"">Indeed it has.<br class=3D""><br =
class=3D"">I note that some YANG clauses have [references] in them which =
are<br class=3D"">likely not plain text; doubtless that will be fixed at =
some point<br class=3D"">in the process.<br class=3D""><br class=3D"">Tom =
Petch<br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On Apr 12, 2021, at 1:38 =
AM, tom petch<br class=3D"">&lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">This I-D introduces a new and unnecessary YANG prefix in<br =
class=3D"">defiance of BCP216 s.4.2.<br class=3D""><br class=3D"">It =
imports ietf-yang-types, perhaps the most widely imported<br =
class=3D"">module in the world, and RFC6991, where that module is<br =
class=3D"">specified, defines the proper prefix as 'yang'. &nbsp;This =
I-D<br class=3D"">invents a different one. Technically, YANG can cope =
with this<br class=3D"">but that does not make it a sensible thing to =
do.<br class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D"">On=
 08/04/2021 13:43, The IESG wrote:<br =
class=3D""></blockquote></blockquote></blockquote></blockquote></blockquot=
e></blockquote><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Mahesh Jethanandani <a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D""></blockquote></blockquote><br class=3D"">Mahesh =
Jethanandani<br class=3D""><a href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D""></blockquote></div></div></blockquote></div><br class=3D""><div=
 class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_53F9345A-E3E6-4474-9218-89BA3DC24981--


From nobody Mon May 17 01:49:35 2021
Return-Path: <lars@eggert.org>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 133013A2F35; Mon, 17 May 2021 01:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=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 (1024-bit key) header.d=eggert.org
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 pWfDpUD2E-8j; Mon, 17 May 2021 01:49:14 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 E89A33A2F13; Mon, 17 May 2021 01:49:13 -0700 (PDT)
Received: from smtpclient.apple (unknown [212.68.24.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 49016600C7B; Mon, 17 May 2021 11:49:07 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1621241347; bh=fsi9U3GMGcaFxuMRaOJi4RlaX6LAoVTydz2HzwIlHvE=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=hZzHlmw2dIE18ex0Z4iRBm+YjllsAAxsynSnWj3WftlImngLYkmzGRhSIDqt66ykD 73cky37XGdgRh/tZdBnUNJ5nRIvV2fLV5qxLTBhkMk8QDl2Tjon9z3jDglUIG2Z4or BA1C0N18540/OdKaZ9/mXJ2UXRZFgRxepdwIRHhs=
From: Lars Eggert <lars@eggert.org>
Message-Id: <41E67DF8-41CF-44A3-AEA5-789F5D9BB432@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F0EDCB68-939B-4890-A2E3-F1A2987F0347"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Mon, 17 May 2021 11:49:06 +0300
In-Reply-To: <162014997938.23614.6494865677211981729@ietfa.amsl.com>
Cc: General Area Review Team <gen-art@ietf.org>, last-call@ietf.org, draft-ietf-babel-yang-model.all@ietf.org, babel@ietf.org
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <162014997938.23614.6494865677211981729@ietfa.amsl.com>
X-MailScanner-ID: 49016600C7B.AFC02
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/lvzrXcRiZtOuk9eLITp4U7X46ag>
Subject: Re: [babel] [Last-Call] Genart last call review of draft-ietf-babel-yang-model-09
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 08:49:27 -0000

--Apple-Mail=_F0EDCB68-939B-4890-A2E3-F1A2987F0347
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Stewart, thank you for your review. I have entered a No Objection ballot =
for this document.

Lars


> On 2021-5-4, at 20:39, Stewart Bryant via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-babel-yang-model-09
> Reviewer: Stewart Bryant
> Review Date: 2021-05-04
> IETF LC End Date: 2021-04-22
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: A well written text that is ready for publication. Just one =
note and a
> couple of minor nits.
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> 5.  Acknowledgements
> Juliusz Chroboczek provided most of the example configurations for =
babel that
> are shown in the Appendix.
>=20
> The Appendix seems seems quite substantive, I am surprised that =
Juliusz was not
> listed as an author.
>=20
> Nits/editorial comments:
> 2.1.  Information Model
>=20
> " attributes are marked a read-only objects in the information module"
> SB> s/marked a/marked as/
>=20
> 2.3.  YANG Module
> "On other hand, for a"
>=20
> SB> s/On other hand/On the other hand/
>=20
>=20
> --
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call


--Apple-Mail=_F0EDCB68-939B-4890-A2E3-F1A2987F0347
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAmCiLgIACgkQVLXDCb9w
wVfS2w/+OOI5heExouHz/GQ+hDopCTS68ylWW03Fd20lpGv2z7o1x0wbpyYFEu0b
6OJnjrIbuGrJPap2sYdKXWLWWimAlqixmmHlwyFIIkwVxP2cSdjJnSqf2iemCENS
jpUuM2Gvk0b+3SgFhkmgeA24kqQyDwjxyDB2wRiLoJbwoh6LFW/+TdlVGxqi9T8t
s+5UFLERYL1P7XSybAVrVXe02R0Rxbb4Huw4pQ1kiGUUGcv8Hh3rNmLh3iPjhBzI
PGRyxsXgC2vja0KkS04eb1deb+GoqA4ajT2ThHC83ZjGyDFDb/MYR9YkOQfTnH2X
Q+c1G2jYES8Wgrt4CoKmVtIlTeS5FGUNKcAamCPeXaULyGNVHoLAzcjDgypJm8DT
vIIPT4e19ehYcXOHIzULjCc3mGEBvEqiJvFKigR4MUhwQzzX7tG43nwYerhjlQwS
obbaqX7xG2l7oQcIRi3jpT9b1zdFE58x2QmnWR3iogLgEfQe5stIZT3cVZggI4Ac
L5No3ZErr7ftvz8z8kP1rjtE/kFPfP/ykZgb95sdNaqL9c+aGyiaxcNBGNT5TF8N
IC2xq5gZL0c5nUbami1rCz4hu3YZfGl3t0RFHY1Ii8v5/oIq1YHtDO2zaKpdKAUm
G3f3R6KJPJR2yC2sSdEiqJ5VEZyvnLyTFFji8MvpL+dsx3+T1M8=
=jNDF
-----END PGP SIGNATURE-----

--Apple-Mail=_F0EDCB68-939B-4890-A2E3-F1A2987F0347--


From nobody Mon May 17 02:46:01 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E48D23A30C2; Mon, 17 May 2021 02:45:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <162124475990.8618.15255310968103028424@ietfa.amsl.com>
Date: Mon, 17 May 2021 02:45:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/5Pxd-FNUDr3y5nnMpmmzkF-mgIE>
Subject: [babel] =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-bab?= =?utf-8?q?el-yang-model-10=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 09:46:00 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-babel-yang-model-10: 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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thank you for the work put into this document. I really like the fact that the
information model is built before the data model. Congratulations !

Please find below one blocking (but trivial to fix) DISCUSS point, some
non-blocking COMMENT points (but replies would be appreciated), and one nit.

Thank you to Donald Eastlake for his shepherd's write-up (including the WG
consensus).

I hope that this helps to improve the document,

Regards,

-éric

== DISCUSS ==

The YANG module does not compile correctly with PYANG, it should be easy to fix
though :-) See: https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html
Or is it a PYANG error ?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

== COMMENTS ==

The related links on should be updated. E.g., the YANG catalog entry should be:
https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-babel@2021-05-12

-- Section 2.2 --
I usually use the expanded tree view rather the YANG module itself to get a
global view. Is there any reason why the full tree view is not included?

-- Section 5 --
Is there any reason why the doc shepherd is not acknowledged ?

== NITS ==

-- Section 2.3 --
s/MAC based security/MAC-based security/ ?




From nobody Mon May 17 14:10:38 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D69B3A4510; Mon, 17 May 2021 14:10:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <162128583297.9778.8228421381328520899@ietfa.amsl.com>
Date: Mon, 17 May 2021 14:10:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/gYFfSD5GPCz1GF84xqwfcTcFLFg>
Subject: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 21:10:34 -0000

Martin Duke has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Objection

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(2.3)

leaf received-metric {
           type uint16;
           description
             "The metric with which this route was advertised by the
              neighbor, or maximum value (infinity) to indicate the
              route was recently retracted and is temporarily
              unreachable. This metric will be 0 (zero) if the route
              was not received from a neighbor but was generated
              through other means. At least one of
              calculated-metric or received-metric MUST be non-NULL.";
           reference
             "RFC ZZZZ: Babel Information Model, Section 3.6,
              RFC 8966: The Babel Routing Protocol, Section 2.1.";
         }

         leaf calculated-metric {
           type uint16;
           description
             "A calculated metric for this route. How the metric is
              calculated is implementation-specific. Maximum value
              (infinity) indicates the route was recently retracted
              and is temporarily unreachable. At least one of
              calculated-metric or received-metric MUST be non-NULL.";
           reference
             "RFC ZZZZ: Babel Information Model, Section 3.6,
              RFC 8966: The Babel Routing Protocol, Section 2.1.";
         }

I don't understand the relationship between these two. If the metric was
calculated rather than received, why would the value be zero instead of NULL?
Isn't a zero metric dangerous in a routing algorithm?

(4) "config true perspective"?




From nobody Mon May 17 14:18:15 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8853A454B; Mon, 17 May 2021 14:18:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alvaro Retana via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alvaro Retana <aretana.ietf@gmail.com>
Message-ID: <162128629308.24381.17399414850999671848@ietfa.amsl.com>
Date: Mon, 17 May 2021 14:18:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/4KRCjPX67EZAgDbHR1ubJB6Fb5E>
Subject: [babel] Alvaro Retana's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2021 21:18:14 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Objection

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

§1: "It is based on the Babel Information Model
[I-D.ietf-babel-information-model]."  The reference should be Normative.




From nobody Mon May 17 18:02:08 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D0F3A168A; Mon, 17 May 2021 18:02:06 -0700 (PDT)
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 YMhYNdRE0lY4; Mon, 17 May 2021 18:02:02 -0700 (PDT)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 3B5E73A1685; Mon, 17 May 2021 18:02:02 -0700 (PDT)
Received: by mail-pj1-x102c.google.com with SMTP id ot16so2674941pjb.3; Mon, 17 May 2021 18:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=1eWyFLPejEcMkpYYuPZSL2/FUukXMj/Kew9Je/Qp0Io=; b=dHDk9zyk3suYl6onlCNt97FJz5PCTNC3hDY0oGfoNd24glEfx25cLgZB414yp93cgc AxLmCO8UxbeafgRKbsqdgKEsOZ37CVEVc7A2Jb7+wQKxaVZHJFutv0prSt3kPbw+NFtm Ls+UQqG6PT12Jq6z/1txKUqVa7qgHw0mkMZofwtjVatAJEd5l5vB12vC6AggjRzgURjz 3gIa+mQGk0+v3YuraXFlEYDqGzTPdRrHBFvsUprnBi0cPOIsE2CLdbU4CQf2BhtNWNXG C3wHF+zs2XgYE3lXnjM6TZXSTe5bO4sb3RgstyPC2T73xgzNiK7tBNG6U1qRb1wt45E3 XO3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=1eWyFLPejEcMkpYYuPZSL2/FUukXMj/Kew9Je/Qp0Io=; b=Yt9DS7baHX6boyyiDFwXVqLaTnDpXZvzwqscs+nJAG8pDV7Q+IznlRJSMrNz5JgZud WRynD9JcubYT8YufLaxM9MNtBxUOR9PPD4bITS7jORX1FZg2KyBPvZ5zVKiTFy1FL77L T1fUIprIp4lpGcMiy82FOpPveFbSuaFrm+RuhHMZSNupptJmsmA0BIerapFrMXS026i5 cKVAUnIV+XXXPaxb3vS4YsVMp0A8ETD4H8O7ChGEWK/LHQgWT8EMjsOJiA9orfLsd6he BJZCdT1az6yrGarbvTP0+lmvNq7YAfxfEUdUmmO2CKOQqGjbZ0sTQ/L5TqNXDL4nHNs4 mZlg==
X-Gm-Message-State: AOAM531gvg3NU5Mz4fLOFFrhNLZ5NZtqdfZrmifGwlbmNTTHEt1eJdgi JwaJlfEyG5vB3CAcIgMyz/o=
X-Google-Smtp-Source: ABdhPJwV2WtlrqJiB2btr/OkO4NP5gJrJamtKha3LNcF6UZ7ieWbxZL5o7jPnpTCM883WgnjTuvlwQ==
X-Received: by 2002:a17:903:52:b029:f0:c3b2:15ac with SMTP id l18-20020a1709030052b02900f0c3b215acmr1518152pla.82.1621299720705;  Mon, 17 May 2021 18:02:00 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:5155:42ce:7ff2:f301? ([2601:647:5600:5020:5155:42ce:7ff2:f301]) by smtp.gmail.com with ESMTPSA id k38sm11190530pgi.73.2021.05.17.18.01.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 May 2021 18:02:00 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <C8A8CAA5-0F11-4B35-98B3-C544B5562E47@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4908D732-9884-4E77-837A-14E2EEF5E5C9"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 17 May 2021 18:01:58 -0700
In-Reply-To: <162128629308.24381.17399414850999671848@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
References: <162128629308.24381.17399414850999671848@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/TPC8sWPOQUb6StQ6Ycmdp6X9jNE>
Subject: Re: [babel] Alvaro Retana's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 01:02:07 -0000

--Apple-Mail=_4908D732-9884-4E77-837A-14E2EEF5E5C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Alvaro,

> On May 17, 2021, at 2:18 PM, Alvaro Retana via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Alvaro Retana has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> =C2=A71: "It is based on the Babel Information Model
> [I-D.ietf-babel-information-model]."  The reference should be =
Normative.

This gets into a whole lot of discussion around whether the information =
model is informational or not, something that has already happened in =
the WG and when that document came up in front of IESG (I think). I =
believe the decision was to keep the information model as informative.

I have therefore kept the reference as Informative. If I try to move it =
into the Normative part of the reference section, I get a downref error.

Cheers.

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_4908D732-9884-4E77-837A-14E2EEF5E5C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Alvaro,<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 17, 2021, at 2:18 PM, Alvaro Retana =
via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
class=3D"">noreply@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Alvaro=
 Retana has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Objection<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">=C2=A71: "It is based on the Babel =
Information Model<br class=3D"">[I-D.ietf-babel-information-model]." =
&nbsp;The reference should be Normative.<br =
class=3D""></div></div></blockquote><br class=3D""></div><div>This gets =
into a whole lot of discussion around whether the information model is =
informational or not, something that has already happened in the WG and =
when that document came up in front of IESG (I think). I believe the =
decision was to keep the information model as informative.</div><div><br =
class=3D""></div><div>I have therefore kept the reference as =
Informative. If I try to move it into the Normative part of the =
reference section, I get a downref error.</div><div><br =
class=3D""></div><div>Cheers.</div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_4908D732-9884-4E77-837A-14E2EEF5E5C9--


From nobody Tue May 18 11:01:09 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132DF3A1B29; Tue, 18 May 2021 11:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 fzqnz0BA1pHF; Tue, 18 May 2021 11:01:02 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 1F49D3A1B16; Tue, 18 May 2021 11:01:01 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id g18so6333229pfr.2; Tue, 18 May 2021 11:01:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=31GeimpxqKdfPDRaKMxxisX2jSjfIFm/Jf1fn4sQUO0=; b=tTWdaJR162BHGkpaAHupHLJ2mxjOAVCeLxzyJkfSrCa6ZLJdyCD0Z9GD2jvW82I3ES 6e1/zQZLhXShxNA8WYIykH5AkkH1UGibo4mThScYt1beJoJyBYp7Wb/jQ1hMvzmTX71l K2fEWUI2MIKbReoY/yrU81T8sp8hmsWLiYg5QrxJiDDxOXLbB3qqhrtDDHLSb6ZtZ9yX fc+AUj/F6t47uFCqN8bpjNCxXzead5kGPLrMD1lYesFmSY0Dtk8F6F9wvydbjUe3Xldg yqYuBov1QvMxfHLtPnTQOq5xHOThAo5THzr9+L2FEKeR4/cP03c8Dcs0Hb0lVA5rQvo2 IFvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=31GeimpxqKdfPDRaKMxxisX2jSjfIFm/Jf1fn4sQUO0=; b=XhyrABTOfedEbnGkPfUuPlxu/JurOj1P4tlcoJhQm3TN9uOFxYeFKC2KVVbINTU3/5 3O6eUE+FksjvkHeVUGV6Tx4wTSYBdHMIg6tMhXjC/gQNL2iAFBXyRxuu7pZ5D1oGuUTw DCjG5Mz5CNne2v/P+r9+rYdmU01zqvCj0UbVBXnY3ZX1ekWwXY2VfMPf+GUBO7iDmZhv C4YCf67FSz9FRE90Xv1ITIPoYGCE3Lx/0/+U+hFHwsuK2IAPF3xiuUOQPPIwKkAx88kB wC3NpuPQ1RqYN3z4vCtO2jFsmHXvpodklBF8FDFx8jinEAzZJVQZuaTIXB04LBmGoVuu 1cwQ==
X-Gm-Message-State: AOAM532/oQQzCNpz3j3X2ExkQsDCssKPnHvzGgI2+tj9lCG1tiBhv2wm 4+vTjTPEHepkChqfE0m0ge8=
X-Google-Smtp-Source: ABdhPJybTJHrI64nnkJA3sQvZHJXgUeyqlbmj6LEn7HhpdxUjzKLeqZVnZSFMaw+5BloD2+1f3kbGg==
X-Received: by 2002:a05:6a00:162b:b029:27f:f30e:f0db with SMTP id e11-20020a056a00162bb029027ff30ef0dbmr6238285pfc.73.1621360859886;  Tue, 18 May 2021 11:00:59 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:c54e:5d38:16e0:5235? ([2601:647:5600:5020:c54e:5d38:16e0:5235]) by smtp.gmail.com with ESMTPSA id f6sm12342634pfe.74.2021.05.18.11.00.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 May 2021 11:00:59 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_65AD0BD4-3257-4E18-AA7E-5FFCF158DBFE"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 18 May 2021 11:00:55 -0700
In-Reply-To: <162128583297.9778.8228421381328520899@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/cOJmnQB-EeXncKu19S95skKYuyE>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 18:01:07 -0000

--Apple-Mail=_65AD0BD4-3257-4E18-AA7E-5FFCF158DBFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Martin,

You bring up a point that I have been struggling with.

> On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Martin Duke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (2.3)
>=20
> leaf received-metric {
>           type uint16;
>           description
>             "The metric with which this route was advertised by the
>              neighbor, or maximum value (infinity) to indicate the
>              route was recently retracted and is temporarily
>              unreachable. This metric will be 0 (zero) if the route
>              was not received from a neighbor but was generated
>              through other means. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>=20
>         leaf calculated-metric {
>           type uint16;
>           description
>             "A calculated metric for this route. How the metric is
>              calculated is implementation-specific. Maximum value
>              (infinity) indicates the route was recently retracted
>              and is temporarily unreachable. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>=20
> I don't understand the relationship between these two. If the metric =
was
> calculated rather than received, why would the value be zero instead =
of NULL?
> Isn't a zero metric dangerous in a routing algorithm?

How do you represent NULL? By definition, NULL means there is no value, =
that we are looking at an empty leaf. A =E2=80=98received-metric=E2=80=99 =
per my reading, cannot be empty. It is either received from a neighbor, =
or is a generated value, and therefore cannot be empty. Same is the case =
for =E2=80=98calculated-metric=E2=80=99. Combine this with the fact that =
the info model defines the leaf of type unsigned int 16, and thus the =
value of 0. Would it help to add something to this effect?

"A value of 0 implies a NULL value, and SHOULD NOT be used in metric =
calculation".

Alternatively, one could change the type to signed int 16, something the =
TR-181 model does. In that case the value has two meanings. If the value =
is less than 0, it means the value is NULL, but if the value is greater =
than 0, then it carries the actual metric value??

In either case, an implementor cannot take the value of the metric as is =
and use it, without checking if it is 0 or -1.

>=20
> (4) "config true perspective"

Dropped the phrase from the sentence.

Thanks

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_65AD0BD4-3257-4E18-AA7E-5FFCF158DBFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Martin,<div class=3D""><br class=3D""></div><div class=3D"">You bring up =
a point that I have been struggling with.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On May =
17, 2021, at 2:10 PM, Martin Duke via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" class=3D"">noreply@ietf.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Martin Duke has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Objection<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">(2.3)<br class=3D""><br =
class=3D"">leaf received-metric {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type =
uint16;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br=
 class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"T=
he metric with which this route was advertised by the<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;neighbor, or maximum value (infinity) to indicate the<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;route was recently retracted and is temporarily<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;unreachable. This metric will be 0 (zero) if the route<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;was not received from a neighbor but was generated<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;through other means. At least one of<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;calculated-metric or received-metric MUST be non-NULL.";<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;reference<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"R=
FC ZZZZ: Babel Information Model, Section 3.6,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;RFC 8966: The Babel Routing Protocol, Section 2.1.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf =
calculated-metric {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type =
uint16;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br=
 class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"A=
 calculated metric for this route. How the metric is<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;calculated is implementation-specific. Maximum value<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;(infinity) indicates the route was recently retracted<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;and is temporarily unreachable. At least one of<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;calculated-metric or received-metric MUST be non-NULL.";<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;reference<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"R=
FC ZZZZ: Babel Information Model, Section 3.6,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;RFC 8966: The Babel Routing Protocol, Section 2.1.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D"">I don't understand the relationship between these two. If the =
metric was<br class=3D"">calculated rather than received, why would the =
value be zero instead of NULL?<br class=3D"">Isn't a zero metric =
dangerous in a routing algorithm?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>How do you =
represent NULL? By definition, NULL means there is no value, that we are =
looking at an empty leaf. A =E2=80=98received-metric=E2=80=99 per my =
reading, cannot be empty. It is either received from a neighbor, or is a =
generated value, and therefore cannot be empty. Same is the case for =
=E2=80=98calculated-metric=E2=80=99. Combine this with the fact that the =
info model defines the leaf of type unsigned int 16, and thus the value =
of 0. Would it help to add something to this effect?</div><div><br =
class=3D""></div><div>"A value of 0 implies a NULL value, and SHOULD NOT =
be used in metric calculation".</div><div><br =
class=3D""></div><div>Alternatively, one could change the type to signed =
int 16, something the TR-181 model does. In that case the value has two =
meanings. If the value is less than 0, it means the value is NULL, but =
if the value is greater than 0, then it carries the actual metric =
value??</div><div><br class=3D""></div><div>In either case, an =
implementor cannot take the value of the metric as is and use it, =
without checking if it is 0 or -1.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">(4) "config true perspective"<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Dropped =
the phrase from the sentence.</div><div><br =
class=3D""></div><div>Thanks</div><div><br class=3D""></div><div =
class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_65AD0BD4-3257-4E18-AA7E-5FFCF158DBFE--


From nobody Tue May 18 11:01:56 2021
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E383A1AF9; Tue, 18 May 2021 11:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 3yXROptls63n; Tue, 18 May 2021 11:01:50 -0700 (PDT)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 3321C3A1AF4; Tue, 18 May 2021 11:01:50 -0700 (PDT)
Received: by mail-ej1-x634.google.com with SMTP id z12so14530512ejw.0; Tue, 18 May 2021 11:01:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=mudLZPe2wONdRsg9yM5j3L7Tm5sz05L/uB3O+GoPRxs=; b=Nc6rRjE276S0PENNJo88DzkUVgk5kx4TiZulB26B1bCtcdMVqd2O3tJGmfnKVC9dbY Ahttex0t2c5m1BfCQT4rnUxrt5wHdpCPiQFX6L/21rJWwuqQxna6qlGgtkP0Yp52lti5 w8nAVRUC6D1uEsheDTCRbD09+EI8g0Lo6jelBYRo4V3WQIuwonGzKfSrmsDTLrBtpRaV w73DrT7w7O7vNqpZCaNWrtwo7qi5duOPNgT14mSEECrrqjj8exzvkh4Ki/3aRygTvlGC agqDrp+4kgFG0/R7koEdoENPCkGOJ/3X3dTfAnHLlou2B/PgqoqV3qbdrBPsPHFLzr4I 0LFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=mudLZPe2wONdRsg9yM5j3L7Tm5sz05L/uB3O+GoPRxs=; b=me+OvFaJ56y68cJc7SHDyXHMMhsapjUF96xRNFUW2QkhK3VIiUfzTtQHDBndAXyNWO awI5THm5ARP+o50R2KGUAd/FRkk6l/LxxfsAmDMG9sWWpautiQK1KEYGzIql5sfUhU0r szv0PfoVh1tLCagObNFB5DFRPAUlgrWHw8BRwkTO3asIiYNUoEYUbqJNRmevbPxEZVVc CoLwoK+tGjmP0ubAHkkclW19q4HQN7sZ8B1Zj2TZ3Y+KAvTO1Yml0+Vrpq58rUci/SV8 a85wjlW+/4QdpgjHHcMiark+ICI5ABETThhgiaKspS/FhT6LD94zr36D5og/eFOzrZOn KSng==
X-Gm-Message-State: AOAM533O4SuyrXyt+AfFYMZQezTw71VvJqQjF11fP+txdCL4EFr4mUme aDR4RMBCucjd1eDEbLxKNLg4HPM1RY6mZxrQzxE=
X-Google-Smtp-Source: ABdhPJwqPePL2E0Zk667oR114G7I/koHLMMxduW2GMxqyCCFAGFAPZPUVKSirxPf/xzzeOCyYjgzWtSZMKXdyZnkJyA=
X-Received: by 2002:a17:906:ad9a:: with SMTP id la26mr7404867ejb.122.1621360906913;  Tue, 18 May 2021 11:01:46 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 18 May 2021 11:01:46 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <C8A8CAA5-0F11-4B35-98B3-C544B5562E47@gmail.com>
References: <162128629308.24381.17399414850999671848@ietfa.amsl.com> <C8A8CAA5-0F11-4B35-98B3-C544B5562E47@gmail.com>
MIME-Version: 1.0
Date: Tue, 18 May 2021 11:01:46 -0700
Message-ID: <CAMMESszRLQVQrbbp-KrA6uKUoNcs8zc0ppzW=NqhzGRkfArX8w@mail.gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, The IESG <iesg@ietf.org>,  babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/68b7ri97kSk1YGWzBZMFeQF525M>
Subject: Re: [babel] Alvaro Retana's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 18:01:55 -0000

On May 17, 2021 at 9:02:01 PM, Mahesh Jethanandani wrote:


Mahesh:

Hi!


> > =C2=A71: "It is based on the Babel Information Model
> > [I-D.ietf-babel-information-model]." The reference should be Normative.
>
> This gets into a whole lot of discussion around whether the information m=
odel
> is informational or not, something that has already happened in the WG an=
d
> when that document came up in front of IESG (I think). I believe the deci=
sion
> was to keep the information model as informative.

The status of the document has nothing to do with the need (or not) to
reference it in a normative way. =C2=A0In general, "normative references
specify documents that must be read to understand or implement the
technology" [1]. =C2=A0In this case, the YANG model is based on the
Information model: the reference should be Normative regardless of the
status of the documents.


> I have therefore kept the reference as Informative. If I try to move it i=
nto
> the Normative part of the reference section, I get a downref error.

Having a Downref is not a showstopper -- it simply needs to be called
out on the IETF LC. =C2=A0There are many documents that have been used as
Downrefs [2].


Thanks!

Alvaro.



[1] https://www.ietf.org/about/groups/iesg/statements/normative-informative=
-references/

[2] https://datatracker.ietf.org/doc/downref/


From nobody Tue May 18 11:10:04 2021
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6BB83A1BC7; Tue, 18 May 2021 11:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 ZeaJwfT0ca0I; Tue, 18 May 2021 11:09:53 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 2A17A3A1BC5; Tue, 18 May 2021 11:09:53 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id t11so10318729iol.9; Tue, 18 May 2021 11:09:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ndWL9SvlOAluq4AzPZrVhFCT/cXzSipBN3DNx1XEmPU=; b=mPzXgPl3vLBuEAM1yVx5ppNNiNSBFH1Dza+9fx/nPHDr3cpt1j4TVoMTlHgVAvd9ZP wmLcuYGOmu1Wrv1OL3Rn1P6dB7LJOL/NsL7oWDxzB22MTUH6if1JwxqqUxzm4TBE8vH9 S9oWC6OgDEfgbwDbNHnGaF1p6gCftTruuHVhKkPULIKQfhFLTtrXgUCCVvhcuWY1YLPC GorfADlF4TtUh8qqnRlbx5u03LjS4RLKu3liTgcqktyV5vmCq+8vTK633Q03bGL4Et31 Y4g4sffcRcPTH73pGnOjpl84tyq36kvnKBTkqbfQJOfLEXhRAFuykk6dLpALvvuJ2edM XgGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ndWL9SvlOAluq4AzPZrVhFCT/cXzSipBN3DNx1XEmPU=; b=Mx0sqUuweC8m0PRKRyRNaFZMRZPgtpK4Q7xqn4nAjNA/Yb7bIulnRb5T1k5+MOtmFS gjtUewuKo0EpcSZISUaA7ZQhctjBT/aHp2SfNFco1xFT4Nf5KOfY/4QyRZC2ST+L/TeJ Qn4VuXU1tLOSRhvHuqXHTwrr6wJB+NFRXxGK5YLtw/Z4sjPgeZItuKp5LmyLBZvBkFgQ N8CSTu+5Pe5adwwVChDrdTuxuR/dn4SwuuG798KdL9NzCxIbKMWj4B0QsElt7D5FNPKV +ctrYf/HOwmyYw12U7Lokqc0e1EzHsrXnMeq62p3/z821eD7vxEXsnSF7NtfgCzmXVQ7 4NPw==
X-Gm-Message-State: AOAM532DgIafaN48EoUzZd4gdUQcEi7q1G/I5kD6WTa8HYV2zca23pTB WJiSJNX7mycOE4iN+LcMdPY/k/zU6ItAC1CYXBE=
X-Google-Smtp-Source: ABdhPJyAvM5E5gzL8jbdS2YduKBWwB4MpFGeEiqRUogEVXkp8xOQnox7/UbCuOsCrhgJWXerjweGOUrE3z7luLWEQfo=
X-Received: by 2002:a05:6602:446:: with SMTP id e6mr5468154iov.20.1621361390630;  Tue, 18 May 2021 11:09:50 -0700 (PDT)
MIME-Version: 1.0
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com> <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com>
In-Reply-To: <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 18 May 2021 11:09:46 -0700
Message-ID: <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org,  babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>,  Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bdbed005c29e9dcd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/dQ8f6_T6F9T5_5c4pnxb-ZNUnEw>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 18:09:58 -0000

--000000000000bdbed005c29e9dcd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

That's fine. In the original text, you refer to zero and NULL as if they're
separate quantities. As these are uints, I think s/NULL/zero would solve
the problem.

It would be helpful to clarify what happens when both values are nonzero.

On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani <
mjethanandani@gmail.com> wrote:

> Hi Martin,
>
> You bring up a point that I have been struggling with.
>
> On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker <noreply@ietf.or=
g>
> wrote:
>
> Martin Duke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>
> 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/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> (2.3)
>
> leaf received-metric {
>           type uint16;
>           description
>             "The metric with which this route was advertised by the
>              neighbor, or maximum value (infinity) to indicate the
>              route was recently retracted and is temporarily
>              unreachable. This metric will be 0 (zero) if the route
>              was not received from a neighbor but was generated
>              through other means. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>
>         leaf calculated-metric {
>           type uint16;
>           description
>             "A calculated metric for this route. How the metric is
>              calculated is implementation-specific. Maximum value
>              (infinity) indicates the route was recently retracted
>              and is temporarily unreachable. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>
> I don't understand the relationship between these two. If the metric was
> calculated rather than received, why would the value be zero instead of
> NULL?
> Isn't a zero metric dangerous in a routing algorithm?
>
>
> How do you represent NULL? By definition, NULL means there is no value,
> that we are looking at an empty leaf. A =E2=80=98received-metric=E2=80=99=
 per my reading,
> cannot be empty. It is either received from a neighbor, or is a generated
> value, and therefore cannot be empty. Same is the case for
> =E2=80=98calculated-metric=E2=80=99. Combine this with the fact that the =
info model defines
> the leaf of type unsigned int 16, and thus the value of 0. Would it help =
to
> add something to this effect?
>
> "A value of 0 implies a NULL value, and SHOULD NOT be used in metric
> calculation".
>
> Alternatively, one could change the type to signed int 16, something the
> TR-181 model does. In that case the value has two meanings. If the value =
is
> less than 0, it means the value is NULL, but if the value is greater than
> 0, then it carries the actual metric value??
>
> In either case, an implementor cannot take the value of the metric as is
> and use it, without checking if it is 0 or -1.
>
>
> (4) "config true perspective"
>
>
> Dropped the phrase from the sentence.
>
> Thanks
>
> Mahesh Jethanandani
> mjethanandani@gmail.com
>
>
>
>
>
>

--000000000000bdbed005c29e9dcd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>That&#39;s fine. In the original text, you refer to z=
ero and NULL as if they&#39;re separate quantities. As these are uints, I t=
hink s/NULL/zero would solve the problem.</div><div><br></div><div>It would=
 be helpful to clarify what happens when both values are nonzero.<br></div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani &lt;<a href=3D"mailto:=
mjethanandani@gmail.com">mjethanandani@gmail.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap=
: break-word;">Hi Martin,<div><br></div><div>You bring up a point that I ha=
ve been struggling with.<br><div><br><blockquote type=3D"cite"><div>On May =
17, 2021, at 2:10 PM, Martin Duke via Datatracker &lt;<a href=3D"mailto:nor=
eply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&gt; wrote:</div><br><=
div><div>Martin Duke has entered the following ballot position for<br>draft=
-ietf-babel-yang-model-10: No Objection<br><br>When responding, please keep=
 the subject line intact and reply to all<br>email addresses included in th=
e To and CC lines. (Feel free to cut this<br>introductory paragraph, howeve=
r.)<br><br><br>Please refer to <a href=3D"https://www.ietf.org/iesg/stateme=
nt/discuss-criteria.html" target=3D"_blank">https://www.ietf.org/iesg/state=
ment/discuss-criteria.html</a><br>for more information about DISCUSS and CO=
MMENT positions.<br><br><br>The document, along with other ballot positions=
, can be found here:<br><a href=3D"https://datatracker.ietf.org/doc/draft-i=
etf-babel-yang-model/" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-babel-yang-model/</a><br><br><br><br>----------------------------=
------------------------------------------<br>COMMENT:<br>-----------------=
-----------------------------------------------------<br><br>(2.3)<br><br>l=
eaf received-metric {<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0type uint16;<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0description<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;The metric with which this route was ad=
vertised by the<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0neighbor, or maximum value (infinity) to indicate t=
he<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0route was recently retracted and is temporarily<br> =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0unreac=
hable. This metric will be 0 (zero) if the route<br> =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0was not received f=
rom a neighbor but was generated<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0through other means. At least one=
 of<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0calculated-metric or received-metric MUST be non-NULL.&quot;;<b=
r> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reference<br=
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&=
quot;RFC ZZZZ: Babel Information Model, Section 3.6,<br> =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0RFC 8966: The B=
abel Routing Protocol, Section 2.1.&quot;;<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0}<br><br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0leaf calculated-metric {<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0type uint16;<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0description<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;A calculated metric for this r=
oute. How the metric is<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0calculated is implementation-specific. Max=
imum value<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0(infinity) indicates the route was recently retracted<br>=
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0and is temporarily unreachable. At least one of<br> =C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0calculated-m=
etric or received-metric MUST be non-NULL.&quot;;<br> =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reference<br> =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;RFC ZZZZ: Babel In=
formation Model, Section 3.6,<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0RFC 8966: The Babel Routing Protocol=
, Section 2.1.&quot;;<br> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0}=
<br><br>I don&#39;t understand the relationship between these two. If the m=
etric was<br>calculated rather than received, why would the value be zero i=
nstead of NULL?<br>Isn&#39;t a zero metric dangerous in a routing algorithm=
?<br></div></div></blockquote><div><br></div>How do you represent NULL? By =
definition, NULL means there is no value, that we are looking at an empty l=
eaf. A =E2=80=98received-metric=E2=80=99 per my reading, cannot be empty. I=
t is either received from a neighbor, or is a generated value, and therefor=
e cannot be empty. Same is the case for =E2=80=98calculated-metric=E2=80=99=
. Combine this with the fact that the info model defines the leaf of type u=
nsigned int 16, and thus the value of 0. Would it help to add something to =
this effect?</div><div><br></div><div>&quot;A value of 0 implies a NULL val=
ue, and SHOULD NOT be used in metric calculation&quot;.</div><div><br></div=
><div>Alternatively, one could change the type to signed int 16, something =
the TR-181 model does. In that case the value has two meanings. If the valu=
e is less than 0, it means the value is NULL, but if the value is greater t=
han 0, then it carries the actual metric value??</div><div><br></div><div>I=
n either case, an implementor cannot take the value of the metric as is and=
 use it, without checking if it is 0 or -1.</div><div><br><blockquote type=
=3D"cite"><div><div><br>(4) &quot;config true perspective&quot;<br></div></=
div></blockquote><div><br></div>Dropped the phrase from the sentence.</div>=
<div><br></div><div>Thanks</div><div><br></div><div>
<div dir=3D"auto" style=3D"color:rgb(0,0,0);letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;text-decoration:none"><div style=3D"color:rgb(0,0,0);letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px"><div>Mahesh Jethanandani</div><div><a href=3D"mailto:mj=
ethanandani@gmail.com" target=3D"_blank">mjethanandani@gmail.com</a></div><=
div><br></div></div><br></div><br><br>
</div>
<br></div></div></blockquote></div>

--000000000000bdbed005c29e9dcd--


From nobody Tue May 18 11:48:14 2021
Return-Path: <bs7652@att.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 056823A1D10; Tue, 18 May 2021 11:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level: 
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=att.onmicrosoft.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 fKkI3ALJUQfy; Tue, 18 May 2021 11:48:03 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C893A1CF2; Tue, 18 May 2021 11:48:02 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.43/8.16.0.43) with SMTP id 14IIObhX044649; Tue, 18 May 2021 14:48:01 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0083689.ppops.net-00191d01. with ESMTP id 38m0nytqk9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 18 May 2021 14:48:00 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 14IIlxas020098; Tue, 18 May 2021 14:47:59 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [135.47.91.189]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 14IIluNQ020019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 18 May 2021 14:47:56 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [127.0.0.1]) by zlp30483.vci.att.com (Service) with ESMTP id E6A5E40145A6; Tue, 18 May 2021 18:47:55 +0000 (GMT)
Received: from GAALPA1MSGED2BC.ITServices.sbc.com (unknown [135.50.89.128]) by zlp30483.vci.att.com (Service) with ESMTP id 8C6CA40145A4; Tue, 18 May 2021 18:47:55 +0000 (GMT)
Received: from GAALPA1MSGEX1AA.ITServices.sbc.com (135.50.89.96) by GAALPA1MSGED2BC.ITServices.sbc.com (135.50.89.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.4; Tue, 18 May 2021 14:47:48 -0400
Received: from GAALPA1MSGETA01.tmg.ad.att.com (144.160.249.126) by GAALPA1MSGEX1AA.ITServices.sbc.com (135.50.89.96) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.4 via Frontend Transport; Tue, 18 May 2021 14:47:48 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.57.47) by edgeal1.exch.att.com (144.160.249.126) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2242.4; Tue, 18 May 2021 14:47:45 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hPeoYRAvQSHROD8N1KDEbukrmjwaj091ohYS7+ORVKMSBO2bsXdWzH/QnN2At9p2dfu+DZuIaido4VPGy4Z4TE6WPB2sR5Nyk/jHGesg9F5cyybCpJoAhUZLjWEOYlwtwubAOzcNNxNsVyGrRRtE+Tl81uptq3vsWp8W7cLIPul5a/UgZSiiSodAYPMsEaCaxKgjgYjSaucdwWKwWAaMWSWudxoDPExHRHBS2TM3kCtL8xQb58VB9Cfo9eOKE/7pu8WCj5b4ZkcN5qGE4slkYkRg6dHzqHQFG75SBIOnFKWv/fgVAnlmOrbOP54o6yb/xQj8rCm3FyMC3gcku5u0DQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/yCs8wl/dFdYMy22eQGqzHftFO4SePyP0D/3goujNG0=; b=XAntSa8NIlOKQYcUs+4cYy/nC3ojFcRyv5AYCtfmTkV96suCSS6E9QXKdJstZzvoiszspLtb0zFTM4Jz/6j17ln2/aDdKiu8JXF6G+Pc2fo7zpuHH+16ssz6yRP6G3HLZAcW3+aRxf54y/dHVJoeAW2jtYNT90G2QAjesHwL6UA1GyykpXoy30hJvq3VXnHpCk1o/znghfCrTr+CIYrLfX8cyax78+iC3M81ynDS30JWT5bBizYfA9RDERbOecgELHXiKiKfc/pRijY01pR1DXx962OKNhSEmGwkVgtIiMV0PteSKGji/rgS/VbHJ5KBeOa4XxwzuZI2VqrGqKkMBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=att.com; dmarc=pass action=none header.from=att.com; dkim=pass header.d=att.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.onmicrosoft.com; s=selector2-att-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/yCs8wl/dFdYMy22eQGqzHftFO4SePyP0D/3goujNG0=; b=GM3WL5Wwh6BKfCit0Wc5hy2DMWt4W9eBxhE7famdw+iclx14jlQrIrNzXvqXCrMTXftsK6duhOzcOGmdDwZtwf6KkhZkYmDWvPE7KBDroa8bFWl1D2FkQeKv2kZmx5iSAUBUJnrdfHsdtJNigiJ+kfwFzsmtywBwS9RQE4zC9HI=
Received: from DM6PR02MB6924.namprd02.prod.outlook.com (2603:10b6:5:25f::7) by DM5PR02MB3209.namprd02.prod.outlook.com (2603:10b6:4:64::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4129.26; Tue, 18 May 2021 18:47:43 +0000
Received: from DM6PR02MB6924.namprd02.prod.outlook.com ([fe80::d09:83cc:18fe:ab1d]) by DM6PR02MB6924.namprd02.prod.outlook.com ([fe80::d09:83cc:18fe:ab1d%9]) with mapi id 15.20.4129.032; Tue, 18 May 2021 18:47:43 +0000
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Martin Duke'" <martin.h.duke@gmail.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>
CC: "'The IESG'" <iesg@ietf.org>, "'draft-ietf-babel-yang-model@ietf.org'" <draft-ietf-babel-yang-model@ietf.org>, "'babel-chairs'" <babel-chairs@ietf.org>, "'Babel at IETF'" <babel@ietf.org>, "'Donald Eastlake'" <d3e3e3@gmail.com>
Thread-Topic: Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
Thread-Index: AQHXTA/YfEAK5FlCCkWqGthi9aIBe6rpidgAgAABkuA=
Date: Tue, 18 May 2021 18:47:43 +0000
Message-ID: <DM6PR02MB692424BDA3D24B163D1E37F4C32C9@DM6PR02MB6924.namprd02.prod.outlook.com>
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com> <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com> <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com>
In-Reply-To: <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=att.com;
x-originating-ip: [45.18.123.63]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a3d2e3a9-caec-4c04-9c38-08d91a2d6c1c
x-ms-traffictypediagnostic: DM5PR02MB3209:
x-microsoft-antispam-prvs: <DM5PR02MB3209185E9C888FE74767113BC32C9@DM5PR02MB3209.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6aAd0oO8G8ltLRFyaaouFFEYUGKcDY6GYUsGgD5JpUfyIjIWGpn7SEwcDilany274jhHAeWIv6/KTQqAZ3RMFrlcEscaZeH6sp2oybfHJy81EIAQbFIrblENTOMJotgzCKQujavfHymTooxrY/JpFSW1UyZ5G6xvJKwWiBIaHHQ4Hj7Mm4S1l1w8dFJ5tpJUeVz9DtsVR1livxelP+VOH2N4k49eg595zbHd6RyZPFbdic1EAUvk0C/J91fGKiqzRJNDOvZLCsfY54OplWz7MmqgEUN4uoFkJ9+YKrp/a3QqlpF98RLHFdbmhOn/+y8ILVXz/tW8V2q/cFpoMfllb05RnWxax6YlhDDz635oQtlE6qdavnT5ObOPOUMCUQ2lpPgpwCbibBzZO6nhOtAYI8OCWHlDzd8l2uKPQyDtYBV/tT59bbeGWKvYwXHze8/gNJ9PkpEMXXIQZTSGkZd4au1aq6d2Kz0ndWbsb5z5T94vxlFoNHFp/ri/8+011nlED80Rwz9Qd5TqefWOYBgsdoazfrU6tmOxawzXpDUR3kDhYjBIovUa4VltvT04IpwekvXSQGjlWBKNt5ZUuck5RKl8mCUl8LORkbLZ//sIIShJ2uvjsY95RR89PD7duw3eBOcO0mE+8M5RsAPxA1fnMWKGFKQgjWvYiCU3LWdyCKUWw2LFFYaEeJm9oTOjigBxheY8Mj46CGtGDheS5XeK0g==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR02MB6924.namprd02.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(39860400002)(376002)(366004)(136003)(82202003)(55016002)(71200400001)(38100700002)(6506007)(53546011)(33656002)(122000001)(7696005)(26005)(186003)(8676002)(54906003)(64756008)(2906002)(66946007)(86362001)(66556008)(76116006)(66476007)(966005)(66446008)(110136005)(8936002)(478600001)(316002)(166002)(5660300002)(9686003)(66574015)(83380400001)(4326008)(52536014)(579004)(559001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?fx6om1tuSF8rI6dyWhHxWe+SbMqoKwvvqROcCuunypVnFBedQjy8umdUInaJ?= =?us-ascii?Q?2bxw538it+0DpL180aZiBzzEFt8L3hO9ltNIPcHj0v0ZqGxmSOaGVK19ytds?= =?us-ascii?Q?zphPf1q79BmhqMsI9VfoYluSkIJHniMK6JsC5mk/Cayhi7RLIFMtbv7yY8xD?= =?us-ascii?Q?nGrvg77VGTis2dwZ2/Q1XYsOQ9biBwM11DUvHygPJ+Csus7P8EhXvh9VYBPk?= =?us-ascii?Q?PxNjx1uovivaKF3Z0gT6aAuNgmBrni3pqUtChC3A7hEVqfNKhEtSCo6RcNiI?= =?us-ascii?Q?CGqr4rwrtw3deAWjdVCRJmWV1q88IsAHGJ30+j8iLTuS2ai4qF7X7WRhpobE?= =?us-ascii?Q?iFKZZPv308ogmB+PPWFmgEQFVJUdeeLPZlBhKLYpANgjzi/C3+xGN2IA4RQd?= =?us-ascii?Q?IA8/kgERbKltwuRZRrgLakrS0D7l2hWbjRuITQoyp+CAxKwDkBSOelkHU8jj?= =?us-ascii?Q?HF2lnAvqbSBf6L0RyplKd5jQXk1bEDuvJq/zebLTjQnhbd0pbiwhxA2VbD+O?= =?us-ascii?Q?MnlhNXPSvrr+rRJIoVdvU3IF994i5QIrclh+rHnw3cP5+v1100hg9HrNDshD?= =?us-ascii?Q?hKS4yPRhBnxpLqA5KuAiMAH9NN4qg3Vt9iFrinOtk0U4ZQdWuY0iSGPrw27D?= =?us-ascii?Q?0i5cVcKWFWxYmFCj4+Ct+OrJA0ZW85BnoTCKqePuWtDU0/fnUUDTCPvRR5nO?= =?us-ascii?Q?Cyc05QR60+cQpbqwKZEFRD2D/yu9hBkgUCb6rK7pVs0b8kq9aU5iSj3/Occ4?= =?us-ascii?Q?UeY/Rsh1/2O1DexEgupRuqNlrFzLmvlXS4D4KqXngx4drAIT7IFKcxvVk5bg?= =?us-ascii?Q?Hi7KK/p9G5hh928Pf98JQceQh/VWCKJxlZqayJNzJZ8f5CcvNMASxtdlXIhL?= =?us-ascii?Q?zUA2f2Ey1V/L78F3TYZR3IYeSCH40txf7ZCl+hI/moOt66dlTXPSIdpPRntK?= =?us-ascii?Q?GSjyZW+dwfJ6/NO/BMu/uRXs5RVGxSv5MPKoe8i0MhX3eMgIhVXOGKjX3z0n?= =?us-ascii?Q?oSZ1dgUl8hguZCybNAPL1/x7OvBi/Z7kASruIFgNmz27/yt40Jvy8MPQVxhu?= =?us-ascii?Q?EVZNmmUF4r7rNq0CSvFJbpqRuh5Mr7zcPfNo+/lPIjDTnaGGMA/WnAMpBmWj?= =?us-ascii?Q?4aRJl/O0HAsCxWvLvdFHksF8FH2ChpUqsnnrWSJ/wcUjStNEtqa/IXMa2ch3?= =?us-ascii?Q?QYAYcYLkw7165v2kFoJuv3n+OXeskjCosVtHEV5oeoIzKxa8vIRmljjOUyeO?= =?us-ascii?Q?dulk4iRvKMXEQnp1BI1QZIJzpOEiutgiy7UyDdEzN27z6zUsDQahHp28i56C?= =?us-ascii?Q?Qp0=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR02MB692424BDA3D24B163D1E37F4C32C9DM6PR02MB6924namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR02MB6924.namprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a3d2e3a9-caec-4c04-9c38-08d91a2d6c1c
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2021 18:47:43.8683 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e741d71c-c6b6-47b0-803c-0f3b32b07556
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: giQGWrXpR1SGlrNfDz35OiQMvc+Q/uia2J8v7Dw9YpO5MgcYyjIduoLnPbKnId31
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR02MB3209
X-OriginatorOrg: att.com
X-TM-SNTS-SMTP: F16B9A97950147A08E39FC3CF2D132D74799A67E8E86DA74D36255883C8C45AD2
X-Proofpoint-ORIG-GUID: 3fjY0D6JhyqreEtxRLMrcrqPm9lpu46e
X-Proofpoint-GUID: 3fjY0D6JhyqreEtxRLMrcrqPm9lpu46e
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-18_09:2021-05-18, 2021-05-18 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 mlxlogscore=999 phishscore=0 adultscore=0 clxscore=1011 impostorscore=0 spamscore=0 suspectscore=0 lowpriorityscore=0 mlxscore=0 bulkscore=0 priorityscore=1501 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2105180128
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/E36ikpE3wUWwyUwyh_DBMkSMC3c>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 18:48:08 -0000

--_000_DM6PR02MB692424BDA3D24B163D1E37F4C32C9DM6PR02MB6924namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The received-metric and calculated-metric are read-only parameters. They co=
me from the babel implementation and are never provided from the data model=
 to the implementation. Their calculation and use (by the implementation) i=
s governed fully by RFC 8966. For the Babel routing protocol implementers, =
NULL (a variable of zero-length) and zero (a value of zero) are separate an=
d distinct values. Various computer languages allow for this distinction - =
even when passing around integers. Data models (and relational databases li=
ke sql and such) often struggle with this distinction because they don't al=
low zero-length integer fields.

If the route is originated by this router, advertised by this router, and n=
ever advertised by another router in the network, then the received-metric =
(per the implementation) will be NULL. If the router is going to advertise =
a route that it originates, it will have to generate a calculated-metric. I=
t may calculate the calculated-metric for itself to be zero - thus ensuring=
, if it subsequently receives an advertisement from another router for the =
same route, the received-metric supplied by the other router will never be =
less than the calculated-metric it has.

Anyway, this is why "This metric will be NULL if the route was not received=
 from a neighbor but was generated through other means." Note that this sen=
tence is about the *route* being received from a neighbor (or the *route* b=
eing generated through other means). The received-metric is never "generate=
d". It is populated by the neighbor-supplied metric for an advertised route=
. And when an entry in the route table is locally originated and there is n=
o received value, then it needs to be properly noted that there is no value=
. An absence of received value is NULL, and not a value of zero.

What happens when both values are non-zero, is a matter of local implementa=
tion policy, as described in RFC 8966 3.5.2 and some of RFC 8966's Appendic=
es that provide examples for how metrics and costs can be computed and used=
. The data model has absolutely no say over what values are passed to it. B=
ut it is an error if it has no metric at all (received or calculated) for a=
 route that is in the route table.
Barbara

From: Martin Duke <martin.h.duke@gmail.com>
Sent: Tuesday, May 18, 2021 1:10 PM
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: The IESG <iesg@ietf.org>; draft-ietf-babel-yang-model@ietf.org; babel-c=
hairs <babel-chairs@ietf.org>; Babel at IETF <babel@ietf.org>; Donald Eastl=
ake <d3e3e3@gmail.com>
Subject: Re: Martin Duke's No Objection on draft-ietf-babel-yang-model-10: =
(with COMMENT)

That's fine. In the original text, you refer to zero and NULL as if they're=
 separate quantities. As these are uints, I think s/NULL/zero would solve t=
he problem.

It would be helpful to clarify what happens when both values are nonzero.

On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani <mjethanandani@gmail.c=
om<mailto:mjethanandani@gmail.com>> wrote:
Hi Martin,

You bring up a point that I have been struggling with.


On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker <noreply@ietf.org<=
mailto:noreply@ietf.org>> wrote:

Martin Duke has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Objection

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/iesg/statement/discuss-criteria.html<h=
ttps://urldefense.com/v3/__https:/www.ietf.org/iesg/statement/discuss-crite=
ria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa496wEI=
Oefq9NP$>
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/<https://urlde=
fense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-babel-yang-model/=
__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa496wEIOvbIEVE$=
>



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(2.3)

leaf received-metric {
          type uint16;
          description
            "The metric with which this route was advertised by the
             neighbor, or maximum value (infinity) to indicate the
             route was recently retracted and is temporarily
             unreachable. This metric will be 0 (zero) if the route
             was not received from a neighbor but was generated
             through other means. At least one of
             calculated-metric or received-metric MUST be non-NULL.";
          reference
            "RFC ZZZZ: Babel Information Model, Section 3.6,
             RFC 8966: The Babel Routing Protocol, Section 2.1.";
        }

        leaf calculated-metric {
          type uint16;
          description
            "A calculated metric for this route. How the metric is
             calculated is implementation-specific. Maximum value
             (infinity) indicates the route was recently retracted
             and is temporarily unreachable. At least one of
             calculated-metric or received-metric MUST be non-NULL.";
          reference
            "RFC ZZZZ: Babel Information Model, Section 3.6,
             RFC 8966: The Babel Routing Protocol, Section 2.1.";
        }

I don't understand the relationship between these two. If the metric was
calculated rather than received, why would the value be zero instead of NUL=
L?
Isn't a zero metric dangerous in a routing algorithm?

How do you represent NULL? By definition, NULL means there is no value, tha=
t we are looking at an empty leaf. A 'received-metric' per my reading, cann=
ot be empty. It is either received from a neighbor, or is a generated value=
, and therefore cannot be empty. Same is the case for 'calculated-metric'. =
Combine this with the fact that the info model defines the leaf of type uns=
igned int 16, and thus the value of 0. Would it help to add something to th=
is effect?

"A value of 0 implies a NULL value, and SHOULD NOT be used in metric calcul=
ation".

Alternatively, one could change the type to signed int 16, something the TR=
-181 model does. In that case the value has two meanings. If the value is l=
ess than 0, it means the value is NULL, but if the value is greater than 0,=
 then it carries the actual metric value??

In either case, an implementor cannot take the value of the metric as is an=
d use it, without checking if it is 0 or -1.



(4) "config true perspective"

Dropped the phrase from the sentence.

Thanks

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





--_000_DM6PR02MB692424BDA3D24B163D1E37F4C32C9DM6PR02MB6924namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"ProgId" content=3D"Word.Document">
<meta name=3D"Generator" content=3D"Microsoft Word 15">
<meta name=3D"Originator" content=3D"Microsoft Word 15">
<link rel=3D"File-List" href=3D"cid:filelist.xml@01D74BEC.5F2515F0"><!--[if=
 gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false" DefSem=
iHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99" LatentStyleCount=
=3D"376">
<w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"No=
rmal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"he=
ading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"header"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footer"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index heading"/>
<w:LsdException Locked=3D"false" Priority=3D"35" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"caption"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of figures"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope return"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"line number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"page number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of authorities"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"macro"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"toa heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 5"/>
<w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true" Name=3D"T=
itle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Closing"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Signature"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" Name=3D"Default Paragraph Font"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Message Header"/>
<w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"true" Name=3D"S=
ubtitle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Salutation"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Date"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Note Heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Block Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"FollowedHyperlink"/>
<w:LsdException Locked=3D"false" Priority=3D"22" QFormat=3D"true" Name=3D"S=
trong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" QFormat=3D"true" Name=3D"E=
mphasis"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Document Map"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Plain Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"E-mail Signature"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Top of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Bottom of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal (Web)"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Acronym"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Cite"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Code"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Definition"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Keyboard"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Preformatted"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Sample"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Typewriter"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Variable"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation subject"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"No List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Contemporary"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Elegant"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Professional"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Balloon Text"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Placeholder Te=
xt"/>
<w:LsdException Locked=3D"false" Priority=3D"1" QFormat=3D"true" Name=3D"No=
 Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1"/=
>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2"/=
>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading"/=
>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" QFormat=3D"true" Name=3D"L=
ist Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" Name=3D"Q=
uote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" QFormat=3D"true" Name=3D"I=
ntense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 1=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 2=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 3=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 4=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 5=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 6=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true" Name=3D"S=
ubtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"true" Name=3D"I=
ntense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"true" Name=3D"S=
ubtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" QFormat=3D"true" Name=3D"I=
ntense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" Name=3D"B=
ook Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"TOC Heading"/>
<w:LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table 1"/>
<w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"Plain Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"44" Name=3D"Plain Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table 5"/>
<w:LsdException Locked=3D"false" Priority=3D"40" Name=3D"Grid Table Light"/=
>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Mention"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Smart Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hashtag"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Unresolved Mention"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Smart Link"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Palatino Linotype";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536869121 1107305727 33554432 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Century Gothic";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-469750017 -1073732485 9 0 511 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-style-unhide:no;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"tab-interval:.=
5in;word-wrap:break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;">The received-metric and ca=
lculated-metric are read-only parameters. They come
 from the babel implementation and are never provided from the data model t=
o the implementation. Their calculation and use (by the implementation) is =
governed fully by RFC 8966. For the Babel routing protocol implementers, NU=
LL (a variable of zero-length) and
 zero (a value of zero) are separate and distinct values. Various computer =
languages allow for this distinction &#8211; even when passing around integ=
ers. Data models (and relational databases like
<span class=3D"SpellE">sql</span> and such) often struggle with this distin=
ction because they don&#8217;t allow zero-length integer fields.<o:p></o:p>=
</span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;"><o:p>&nbsp;</o:p></span></=
font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;">If the route is originated=
 by this router, advertised by this router, and never
 advertised by another router in the network, then the received-metric (per=
 the implementation) will be NULL. If the router is going to advertise a ro=
ute that it originates, it will have to generate a calculated-metric. It ma=
y calculate the calculated-metric
 for itself to be zero &#8211; thus ensuring, if it subsequently receives a=
n advertisement from another router for the same route, the received-metric=
 supplied by the other router will never be less than the calculated-metric=
 it has.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;"><o:p>&nbsp;</o:p></span></=
font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;">Anyway, this is why &#8220=
;</span>This metric will be NULL if the route was not received
 from a neighbor but was generated through other means.&quot; Note that thi=
s sentence is about the *<b><span style=3D"font-weight:bold">route</span></=
b>* being received from a neighbor (or the *<b><span style=3D"font-weight:b=
old">route</span></b>* being generated through
 other means). The received-metric is never &#8220;generated&#8221;. It is =
populated by the neighbor-supplied metric for an advertised route. And when=
 an entry in the route table is locally originated and there is no received=
 value, then it needs to be properly noted that
 there is no value. An absence of received value is NULL, and not a value o=
f zero.<o:p></o:p></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">What happens when both values are non-zero, is a matter of l=
ocal implementation policy, as described in RFC 8966 3.5.2 and some of RFC =
8966&#8217;s Appendices that provide examples
 for how metrics and costs can be computed and used. The data model has abs=
olutely no say over what values are passed to it. But it is an error if it =
has no metric at all (received or calculated) for a route that is in the ro=
ute table.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Barbara</span></font><span style=3D"mso-ascii-font-family:Ca=
libri;mso-hansi-font-family:Calibri;mso-bidi-font-family:&quot;Times New Ro=
man&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;m=
so-bidi-font-family:&quot;Times New Roman&quot;"><o:p>&nbsp;</o:p></span></=
font></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Calibri"><span style=3D"=
font-size:11.0pt;mso-fareast-font-family:&quot;Times New Roman&quot;;font-w=
eight:bold">From:</span></font></b><span style=3D"mso-fareast-font-family:&=
quot;Times New Roman&quot;"> Martin Duke &lt;martin.h.duke@gmail.com&gt;
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, May 18, 2021 =
1:10 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Mahesh Jethanandani &lt;=
mjethanandani@gmail.com&gt;<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> The IESG &lt;iesg@ietf.o=
rg&gt;; draft-ietf-babel-yang-model@ietf.org; babel-chairs &lt;babel-chairs=
@ietf.org&gt;; Babel at IETF &lt;babel@ietf.org&gt;; Donald Eastlake &lt;d3=
e3e3@gmail.com&gt;<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: Martin Duke's N=
o Objection on draft-ietf-babel-yang-model-10: (with COMMENT)<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">That's fine. In the original text, you refer to zero and NUL=
L as if they're separate quantities. As these are uints, I think s/NULL/zer=
o would solve the problem.<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">It would be helpful to clarify what happens when both values=
 are nonzero.<o:p></o:p></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani &lt;<a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a>&gt; wro=
te:<o:p></o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;mso-border=
-left-alt:solid #CCCCCC .75pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;m=
argin-right:0in">
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Hi Martin,<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">You bring up a point that I have been struggling with.<o:p><=
/o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><br style=3D"mso-special-character:line-break">
<![if !supportLineBreakNewLine]><br style=3D"mso-special-character:line-bre=
ak">
<![endif]><o:p></o:p></span></font></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker &lt=
;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>=
&gt; wrote:<o:p></o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Martin Duke has entered the following ballot position for<br=
>
draft-ietf-babel-yang-model-10: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://urldefense.com/v3/__https:/www.ietf.org/=
iesg/statement/discuss-criteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVx=
mAJwtD6CK8WYDmdULfjXSa496wEIOefq9NP$" target=3D"_blank">
https://www.ietf.org/iesg/statement/discuss-criteria.html</a><br>
for more information about DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draf=
t-ietf-babel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WY=
DmdULfjXSa496wEIOvbIEVE$" target=3D"_blank">https://datatracker.ietf.org/do=
c/draft-ietf-babel-yang-model/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
(2.3)<br>
<br>
leaf received-metric {<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type uint16;<br=
>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&qu=
ot;The metric with which this route was advertised by the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;neighbor, or maximum value (infinity) to indicate the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;route was recently retracted and is temporarily<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;unreachable. This metric will be 0 (zero) if the route<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;was not received from a neighbor but was generated<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;through other means. At least one of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;calculated-metric or received-metric MUST be non-NULL.&quot;;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;reference<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&qu=
ot;RFC ZZZZ: Babel Information Model, Section 3.6,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;RFC 8966: The Babel Routing Protocol, Section 2.1.&quot;;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf calculated-metric {<br=
>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type uint16;<br=
>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&qu=
ot;A calculated metric for this route. How the metric is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;calculated is implementation-specific. Maximum value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;(infinity) indicates the route was recently retracted<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;and is temporarily unreachable. At least one of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;calculated-metric or received-metric MUST be non-NULL.&quot;;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;reference<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&qu=
ot;RFC ZZZZ: Babel Information Model, Section 3.6,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;RFC 8966: The Babel Routing Protocol, Section 2.1.&quot;;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br>
<br>
I don't understand the relationship between these two. If the metric was<br=
>
calculated rather than received, why would the value be zero instead of NUL=
L?<br>
Isn't a zero metric dangerous in a routing algorithm?<o:p></o:p></span></fo=
nt></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">How do you represent NULL? By definition, NULL means there i=
s no value, that we are looking at an empty leaf. A &#8216;received-metric&=
#8217; per my reading, cannot be empty. It is either
 received from a neighbor, or is a generated value, and therefore cannot be=
 empty. Same is the case for &#8216;calculated-metric&#8217;. Combine this =
with the fact that the info model defines the leaf of type unsigned int 16,=
 and thus the value of 0. Would it help to add
 something to this effect?<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">&quot;A value of 0 implies a NULL value, and SHOULD NOT be u=
sed in metric calculation&quot;.<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Alternatively, one could change the type to signed int 16, s=
omething the TR-181 model does. In that case the value has two meanings. If=
 the value is less than 0, it means the
 value is NULL, but if the value is greater than 0, then it carries the act=
ual metric value??<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">In either case, an implementor cannot take the value of the =
metric as is and use it, without checking if it is 0 or -1.<o:p></o:p></spa=
n></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><br style=3D"mso-special-character:line-break">
<![if !supportLineBreakNewLine]><br style=3D"mso-special-character:line-bre=
ak">
<![endif]><o:p></o:p></span></font></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><br>
(4) &quot;config true perspective&quot;<o:p></o:p></span></font></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Dropped the phrase from the sentence.<o:p></o:p></span></fon=
t></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt">Thanks<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">Mahesh Jethanandani<o:p></o:p></=
span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black"><a href=3D"mailto:mjethanandani@=
gmail.com" target=3D"_blank">mjethanandani@gmail.com</a><o:p></o:p></span><=
/font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black"><o:p>&nbsp;</o:p></span></font><=
/p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black"><o:p>&nbsp;</o:p></span></font><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"2" face=
=3D"Calibri"><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p></span></fon=
t></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_DM6PR02MB692424BDA3D24B163D1E37F4C32C9DM6PR02MB6924namp_--


From nobody Tue May 18 14:40:03 2021
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60483A100C; Tue, 18 May 2021 14:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.997 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 kAFHGK70OfBG; Tue, 18 May 2021 14:39:52 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 1D2043A1009; Tue, 18 May 2021 14:39:52 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id z24so10946558ioj.7; Tue, 18 May 2021 14:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7UyYdY4AnOVbBLnwGIuA/Ah+PFIYF2CG6X1rrblPXgc=; b=nSdczCgW/q3XKbkH1n0/KQeFCmr/vWTZoR1WnvV9Uzhb+FP9xDhD9mAoE/QLBDm61q E0RQj37yzPX9eyR2RflBWL4MoUqY4EifRGnhGdKYsq7pPHDmbXfI1zOS9R8qbzeQmvQR 6r88ofYZTygAwLIecrgxZYZJuful6j2OSyZU84K/thNcn4ZSmhoyXX1pz2ABTZJ5j+G0 zX2l98NC74sZZyIgvK9M3yCBfNHnp+GS9UFEFjuTtNq+2usqXFBthBrL87twZ1g3IAnQ qUn+OyQiPmr7i6a+y+gR1ApPOtglGDigPBlxGf4knOXda4hcQWQKgYqnOL9eRHFARkqZ b5HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7UyYdY4AnOVbBLnwGIuA/Ah+PFIYF2CG6X1rrblPXgc=; b=RI/ngB7KbmQkM847hAZL1HLSm3Gb8Bx4/JVZtxz2CYnkpk39a5547SOCL7hwb2DUpM YBQrhlCojZoEYuM1b6WzhsnISNinzPJRjiBTL3M8ZQg6Cn9mIndFyGZ1gVbFNblija6v p7+aO0lTAoMYQqDqmc0jBiTYEQenUkD9GvdnqLxqmcgjshZgxzLi1wNhTTG0qhcrip6W JbhoKQVFIZi4NTVem2oLt+DxVuv24jUuz+MLzA/9pEesuf+4NWJgq9IzxFCxI2+cB076 k++No5LpJcqBk1N7Z4ZrRPIFhirfqArJpoAQr92wzvcJMPl4qDzbPCjqzaDYH8dhF06a D/fA==
X-Gm-Message-State: AOAM531T4UPzcnSgAC2XhWSiPd2DEwSJ9gCbFs4FZPxBWv+heqL0qEmc LX7/pu7RmH7/xulVMr35Kh3g8vzoB0cHexA54M4=
X-Google-Smtp-Source: ABdhPJxVY4lWxg+FKJyVscvjlXtFJP9PDG1VY6Mj7yd4SpgObWpGteF90kMXEsaZJ0wkC0WbMzMZarEWLml+CvNM5OI=
X-Received: by 2002:a5e:c10e:: with SMTP id v14mr6222850iol.51.1621373989911;  Tue, 18 May 2021 14:39:49 -0700 (PDT)
MIME-Version: 1.0
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com> <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com> <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com> <DM6PR02MB692424BDA3D24B163D1E37F4C32C9@DM6PR02MB6924.namprd02.prod.outlook.com>
In-Reply-To: <DM6PR02MB692424BDA3D24B163D1E37F4C32C9@DM6PR02MB6924.namprd02.prod.outlook.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 18 May 2021 14:39:46 -0700
Message-ID: <CAM4esxT76NZKJ_6--ryJSnpjtRs7Hkhg4KCrA_h322P1j+YXrQ@mail.gmail.com>
To: "STARK, BARBARA H" <bs7652@att.com>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, The IESG <iesg@ietf.org>,  "draft-ietf-babel-yang-model@ietf.org" <draft-ietf-babel-yang-model@ietf.org>, babel-chairs <babel-chairs@ietf.org>,  Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b77ee405c2a18c51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/XLKpvIC8QNLKpZdtw1uyL7UUFmE>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2021 21:39:57 -0000

--000000000000b77ee405c2a18c51
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Barbara,

On Tue, May 18, 2021 at 11:48 AM STARK, BARBARA H <bs7652@att.com> wrote:

> The received-metric and calculated-metric are read-only parameters. They
> come from the babel implementation and are never provided from the data
> model to the implementation. Their calculation and use (by the
> implementation) is governed fully by RFC 8966. For the Babel routing
> protocol implementers, NULL (a variable of zero-length) and zero (a value
> of zero) are separate and distinct values. Various computer languages all=
ow
> for this distinction =E2=80=93 even when passing around integers. Data mo=
dels (and
> relational databases like sql and such) often struggle with this
> distinction because they don=E2=80=99t allow zero-length integer fields.
>

Thanks for clarifying -- that's a fine distinction to make, although the
authors should agree that they're making it!


>
>
> If the route is originated by this router, advertised by this router, and
> never advertised by another router in the network, then the received-metr=
ic
> (per the implementation) will be NULL. If the router is going to advertis=
e
> a route that it originates, it will have to generate a calculated-metric.
> It may calculate the calculated-metric for itself to be zero =E2=80=93 th=
us
> ensuring, if it subsequently receives an advertisement from another route=
r
> for the same route, the received-metric supplied by the other router will
> never be less than the calculated-metric it has.
>
>
>
> Anyway, this is why =E2=80=9CThis metric will be NULL if the route was no=
t
> received from a neighbor but was generated through other means." Note tha=
t
> this sentence is about the **route** being received from a neighbor (or
> the **route** being generated through other means). The received-metric
> is never =E2=80=9Cgenerated=E2=80=9D. It is populated by the neighbor-sup=
plied metric for
> an advertised route. And when an entry in the route table is locally
> originated and there is no received value, then it needs to be properly
> noted that there is no value. An absence of received value is NULL, and n=
ot
> a value of zero.
>

This makes sense, but it's not what the text says! See my original email.


>
>
> What happens when both values are non-zero, is a matter of local
> implementation policy, as described in RFC 8966 3.5.2 and some of RFC
> 8966=E2=80=99s Appendices that provide examples for how metrics and costs=
 can be
> computed and used. The data model has absolutely no say over what values
> are passed to it. But it is an error if it has no metric at all (received
> or calculated) for a route that is in the route table.
>
> Barbara
>
>
>
> *From:* Martin Duke <martin.h.duke@gmail.com>
> *Sent:* Tuesday, May 18, 2021 1:10 PM
> *To:* Mahesh Jethanandani <mjethanandani@gmail.com>
> *Cc:* The IESG <iesg@ietf.org>; draft-ietf-babel-yang-model@ietf.org;
> babel-chairs <babel-chairs@ietf.org>; Babel at IETF <babel@ietf.org>;
> Donald Eastlake <d3e3e3@gmail.com>
> *Subject:* Re: Martin Duke's No Objection on
> draft-ietf-babel-yang-model-10: (with COMMENT)
>
>
>
> That's fine. In the original text, you refer to zero and NULL as if
> they're separate quantities. As these are uints, I think s/NULL/zero woul=
d
> solve the problem.
>
>
>
> It would be helpful to clarify what happens when both values are nonzero.
>
>
>
> On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani <
> mjethanandani@gmail.com> wrote:
>
> Hi Martin,
>
>
>
> You bring up a point that I have been struggling with.
>
>
>
> On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker <noreply@ietf.or=
g>
> wrote:
>
>
>
> Martin Duke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>
> 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/iesg/statement/discuss-criteria.html
> <https://urldefense.com/v3/__https:/www.ietf.org/iesg/statement/discuss-c=
riteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa49=
6wEIOefq9NP$>
> for more information about DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-b=
abel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjX=
Sa496wEIOvbIEVE$>
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> (2.3)
>
> leaf received-metric {
>           type uint16;
>           description
>             "The metric with which this route was advertised by the
>              neighbor, or maximum value (infinity) to indicate the
>              route was recently retracted and is temporarily
>              unreachable. This metric will be 0 (zero) if the route
>              was not received from a neighbor but was generated
>              through other means. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>
>         leaf calculated-metric {
>           type uint16;
>           description
>             "A calculated metric for this route. How the metric is
>              calculated is implementation-specific. Maximum value
>              (infinity) indicates the route was recently retracted
>              and is temporarily unreachable. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>
> I don't understand the relationship between these two. If the metric was
> calculated rather than received, why would the value be zero instead of
> NULL?
> Isn't a zero metric dangerous in a routing algorithm?
>
>
>
> How do you represent NULL? By definition, NULL means there is no value,
> that we are looking at an empty leaf. A =E2=80=98received-metric=E2=80=99=
 per my reading,
> cannot be empty. It is either received from a neighbor, or is a generated
> value, and therefore cannot be empty. Same is the case for
> =E2=80=98calculated-metric=E2=80=99. Combine this with the fact that the =
info model defines
> the leaf of type unsigned int 16, and thus the value of 0. Would it help =
to
> add something to this effect?
>
>
>
> "A value of 0 implies a NULL value, and SHOULD NOT be used in metric
> calculation".
>
>
>
> Alternatively, one could change the type to signed int 16, something the
> TR-181 model does. In that case the value has two meanings. If the value =
is
> less than 0, it means the value is NULL, but if the value is greater than
> 0, then it carries the actual metric value??
>
>
>
> In either case, an implementor cannot take the value of the metric as is
> and use it, without checking if it is 0 or -1.
>
>
>
>
> (4) "config true perspective"
>
>
>
> Dropped the phrase from the sentence.
>
>
>
> Thanks
>
>
>
> Mahesh Jethanandani
>
> mjethanandani@gmail.com
>
>
>
>
>
>
>
>
>
>

--000000000000b77ee405c2a18c51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Barbara,<br></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 18, 2021 at 11=
:48 AM STARK, BARBARA H &lt;<a href=3D"mailto:bs7652@att.com">bs7652@att.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>







<div style=3D"overflow-wrap: break-word;" lang=3D"EN-US">
<div class=3D"gmail-m_6714943240863696188WordSection1">
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">The received-metric and calculated-metric are read-only parame=
ters. They come
 from the babel implementation and are never provided from the data model t=
o the implementation. Their calculation and use (by the implementation) is =
governed fully by RFC 8966. For the Babel routing protocol implementers, NU=
LL (a variable of zero-length) and
 zero (a value of zero) are separate and distinct values. Various computer =
languages allow for this distinction =E2=80=93 even when passing around int=
egers. Data models (and relational databases like
<span class=3D"gmail-m_6714943240863696188SpellE">sql</span> and such) ofte=
n struggle with this distinction because they don=E2=80=99t allow zero-leng=
th integer fields.</span></font></p></div></div></blockquote><div><br></div=
><div>Thanks for clarifying -- that&#39;s a fine distinction to make, altho=
ugh the authors should agree that they&#39;re making it! <br></div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"ov=
erflow-wrap: break-word;" lang=3D"EN-US"><div class=3D"gmail-m_671494324086=
3696188WordSection1"><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibr=
i"><span style=3D"font-size:11pt"><u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">If the route is originated by this router, advertised by this =
router, and never
 advertised by another router in the network, then the received-metric (per=
 the implementation) will be NULL. If the router is going to advertise a ro=
ute that it originates, it will have to generate a calculated-metric. It ma=
y calculate the calculated-metric
 for itself to be zero =E2=80=93 thus ensuring, if it subsequently receives=
 an advertisement from another router for the same route, the received-metr=
ic supplied by the other router will never be less than the calculated-metr=
ic it has.<u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Anyway, this is why =E2=80=9C</span>This metric will be NULL i=
f the route was not received
 from a neighbor but was generated through other means.&quot; Note that thi=
s sentence is about the *<b><span style=3D"font-weight:bold">route</span></=
b>* being received from a neighbor (or the *<b><span style=3D"font-weight:b=
old">route</span></b>* being generated through
 other means). The received-metric is never =E2=80=9Cgenerated=E2=80=9D. It=
 is populated by the neighbor-supplied metric for an advertised route. And =
when an entry in the route table is locally originated and there is no rece=
ived value, then it needs to be properly noted that
 there is no value. An absence of received value is NULL, and not a value o=
f zero.</font></p></div></div></blockquote><div><br></div><div>This makes s=
ense, but it&#39;s not what the text says! See my original email.<br></div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div sty=
le=3D"overflow-wrap: break-word;" lang=3D"EN-US"><div class=3D"gmail-m_6714=
943240863696188WordSection1"><p class=3D"MsoNormal"><font size=3D"2" face=
=3D"Calibri"><u></u><u></u></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">What happens when both values are non-zero, is a matter of loc=
al implementation policy, as described in RFC 8966 3.5.2 and some of RFC 89=
66=E2=80=99s Appendices that provide examples
 for how metrics and costs can be computed and used. The data model has abs=
olutely no say over what values are passed to it. But it is an error if it =
has no metric at all (received or calculated) for a route that is in the ro=
ute table.<u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Barbara</span></font><span><u></u><u></u></span></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<div style=3D"border-color:currentcolor currentcolor currentcolor blue;bord=
er-style:none none none solid;border-width:medium medium medium 1.5pt;paddi=
ng:0in 0in 0in 4pt">
<div>
<div style=3D"border-color:rgb(225,225,225) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Calibri"><span style=3D"=
font-size:11pt;font-weight:bold">From:</span></font></b><span> Martin Duke =
&lt;<a href=3D"mailto:martin.h.duke@gmail.com" target=3D"_blank">martin.h.d=
uke@gmail.com</a>&gt;
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, May 18, 2021 =
1:10 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Mahesh Jethanandani &lt;=
<a href=3D"mailto:mjethanandani@gmail.com" target=3D"_blank">mjethanandani@=
gmail.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> The IESG &lt;<a href=3D"=
mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a>&gt;; <a href=3D"m=
ailto:draft-ietf-babel-yang-model@ietf.org" target=3D"_blank">draft-ietf-ba=
bel-yang-model@ietf.org</a>; babel-chairs &lt;<a href=3D"mailto:babel-chair=
s@ietf.org" target=3D"_blank">babel-chairs@ietf.org</a>&gt;; Babel at IETF =
&lt;<a href=3D"mailto:babel@ietf.org" target=3D"_blank">babel@ietf.org</a>&=
gt;; Donald Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_bla=
nk">d3e3e3@gmail.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: Martin Duke&#39=
;s No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)<u></u><u>=
</u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">That&#39;s fine. In the original text, you refer to zero and N=
ULL as if they&#39;re separate quantities. As these are uints, I think s/NU=
LL/zero would solve the problem.<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">It would be helpful to clarify what happens when both values a=
re nonzero.<u></u><u></u></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani &lt;<a hr=
ef=3D"mailto:mjethanandani@gmail.com" target=3D"_blank">mjethanandani@gmail=
.com</a>&gt; wrote:<u></u><u></u></span></font></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Hi Martin,<u></u><u></u></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">You bring up a point that I have been struggling with.<u></u><=
u></u></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><br>
<u></u><br>
<u></u><u></u><u></u></span></font></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker &lt;<=
a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&g=
t; wrote:<u></u><u></u></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Martin Duke has entered the following ballot position for<br>
draft-ietf-babel-yang-model-10: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://urldefense.com/v3/__https:/www.ietf.org/=
iesg/statement/discuss-criteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVx=
mAJwtD6CK8WYDmdULfjXSa496wEIOefq9NP$" target=3D"_blank">
https://www.ietf.org/iesg/statement/discuss-criteria.html</a><br>
for more information about DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draf=
t-ietf-babel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WY=
DmdULfjXSa496wEIOvbIEVE$" target=3D"_blank">https://datatracker.ietf.org/do=
c/draft-ietf-babel-yang-model/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
(2.3)<br>
<br>
leaf received-metric {<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0type uint16;<br=
>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0description<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&qu=
ot;The metric with which this route was advertised by the<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0neighbor, or maximum value (infinity) to indicate the<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0route was recently retracted and is temporarily<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0unreachable. This metric will be 0 (zero) if the route<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0was not received from a neighbor but was generated<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0through other means. At least one of<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0calculated-metric or received-metric MUST be non-NULL.&quot;;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reference<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&qu=
ot;RFC ZZZZ: Babel Information Model, Section 3.6,<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0RFC 8966: The Babel Routing Protocol, Section 2.1.&quot;;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0}<br>
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0leaf calculated-metric {<br=
>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0type uint16;<br=
>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0description<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&qu=
ot;A calculated metric for this route. How the metric is<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0calculated is implementation-specific. Maximum value<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0(infinity) indicates the route was recently retracted<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0and is temporarily unreachable. At least one of<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0calculated-metric or received-metric MUST be non-NULL.&quot;;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reference<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&qu=
ot;RFC ZZZZ: Babel Information Model, Section 3.6,<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0RFC 8966: The Babel Routing Protocol, Section 2.1.&quot;;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0}<br>
<br>
I don&#39;t understand the relationship between these two. If the metric wa=
s<br>
calculated rather than received, why would the value be zero instead of NUL=
L?<br>
Isn&#39;t a zero metric dangerous in a routing algorithm?<u></u><u></u></sp=
an></font></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">How do you represent NULL? By definition, NULL means there is =
no value, that we are looking at an empty leaf. A =E2=80=98received-metric=
=E2=80=99 per my reading, cannot be empty. It is either
 received from a neighbor, or is a generated value, and therefore cannot be=
 empty. Same is the case for =E2=80=98calculated-metric=E2=80=99. Combine t=
his with the fact that the info model defines the leaf of type unsigned int=
 16, and thus the value of 0. Would it help to add
 something to this effect?<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">&quot;A value of 0 implies a NULL value, and SHOULD NOT be use=
d in metric calculation&quot;.<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Alternatively, one could change the type to signed int 16, som=
ething the TR-181 model does. In that case the value has two meanings. If t=
he value is less than 0, it means the
 value is NULL, but if the value is greater than 0, then it carries the act=
ual metric value??<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">In either case, an implementor cannot take the value of the me=
tric as is and use it, without checking if it is 0 or -1.<u></u><u></u></sp=
an></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><br>
<u></u><br>
<u></u><u></u><u></u></span></font></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><br>
(4) &quot;config true perspective&quot;<u></u><u></u></span></font></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Dropped the phrase from the sentence.<u></u><u></u></span></fo=
nt></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt">Thanks<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" color=3D"black"><s=
pan style=3D"font-size:11pt;color:black">Mahesh Jethanandani<u></u><u></u><=
/span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" color=3D"black"><s=
pan style=3D"font-size:11pt;color:black"><a href=3D"mailto:mjethanandani@gm=
ail.com" target=3D"_blank">mjethanandani@gmail.com</a><u></u><u></u></span>=
</font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" color=3D"black"><s=
pan style=3D"font-size:11pt;color:black"><u></u>=C2=A0<u></u></span></font>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" color=3D"black"><s=
pan style=3D"font-size:11pt;color:black"><u></u>=C2=A0<u></u></span></font>=
</p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><font size=3D"2" face=
=3D"Calibri"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></fo=
nt></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11pt"><u></u>=C2=A0<u></u></span></font></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>

--000000000000b77ee405c2a18c51--


From nobody Tue May 18 19:29:47 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31293A19BF; Tue, 18 May 2021 19:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 doOLuOjCZd5n; Tue, 18 May 2021 19:29:37 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 10A8D3A19BE; Tue, 18 May 2021 19:29:36 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id l15so5770597iln.8; Tue, 18 May 2021 19:29:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Vw5o5uA9rTGySutYiOizz/A1QE13vnscopzzmK0z7dg=; b=dpKznIK8jXIuWhfCkiPDfCpZQ8P1I2i4X6uj1zsT8l3qhrsnDdx3DCxYqAb3DLn+wW JRwm2d0K0PCSza4IMpRu0tHq1GbT0i+tV0YAme7CVewJNdwmL7EimasBsHZh45Vhnlmv 3zv6dBn+ZQY+jLVn8WYdcOr12wu9toHfGGzq1e0v0t1BJJK1LxCiCqjZB+lhbCYK5ZRs Fmqd0On4ak1zGcq0KXSo2vQqColBJLrlo6zJ2lIsbN8shPYkN77t5DOIEIzxtzNgkKCi werCXj7u3wS0vKsAEif2OXB9U1lmvuOIFjFxcHc5YXLGYgEN+j8BThKJ1l1KpztVm9nC hUEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Vw5o5uA9rTGySutYiOizz/A1QE13vnscopzzmK0z7dg=; b=YjKjPdGt0JAUQn16ISCQQGkTo5g9clxq2FJQSipwZf/6fLW2IAYz8eFoLaKard02kP Wjv+wbdE2vlV+FRBCWpWQ06pY7jsZx7VRrwVYFXLNq0kmfbVsrBUjz6RhRFuEypNceZx 1ewdoU4jag1qRfZv6GGyWOAvpHbgy+IFpVF6arVrO5X9q97+IRRUfzJFmFPibtEjP6ma 5x4epj23BneKriwp31jCTxb44WxwlchECrBzVBAtdGRl56lufuvBltwWxf1F3z0PVCaO XnMQOW5XEt2y3RGzPnVZwEKS4NBILtrqqHO8gCLy6veYhZ01ruXjiZLF4rqcgARngE4l hvdg==
X-Gm-Message-State: AOAM531K4qab4UT44Jc7KjBieyoxJcDENy0IXbovzT6X7lxw3yK3VtaO bZGNakVmhuKO/c8M6/1nDZjvI8+fG9lGvyS0tLpq49iGCiRohQ==
X-Google-Smtp-Source: ABdhPJy8tcZHXRfW/CDcr64JCluKg1W50S0guvO38WSO0uNhNdFRjFUV7hlMGkxqGX3R6UiEZCHoy4rbXWWq0iRF8Jo=
X-Received: by 2002:a05:6e02:1b83:: with SMTP id h3mr7011046ili.199.1621391375403;  Tue, 18 May 2021 19:29:35 -0700 (PDT)
MIME-Version: 1.0
References: <162124475990.8618.15255310968103028424@ietfa.amsl.com>
In-Reply-To: <162124475990.8618.15255310968103028424@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 18 May 2021 22:29:24 -0400
Message-ID: <CAF4+nEHO5TGRrpp97uVa_39S+AwnLMK2jGsU-cWf_xKLo_SYGg@mail.gmail.com>
To: =?UTF-8?B?w4lyaWMgVnluY2tl?= <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org,  babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/-dLg8JQiGPkDjfrIX55MmQu2_dQ>
Subject: Re: [babel]  =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-bab?= =?utf-8?q?el-yang-model-10=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 02:29:42 -0000

Hi =C3=89ric,

On Mon, May 17, 2021 at 5:46 AM =C3=89ric Vyncke via Datatracker
<noreply@ietf.org> wrote:
> =C3=89ric Vyncke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: Discuss
> ...
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> ...
> Thank you to Donald Eastlake for his shepherd's write-up (including the W=
G
> consensus).

You're welcome.

> ...
> -=C3=A9ric
>
> =3D=3D DISCUSS =3D=3D
> ...
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> =3D=3D COMMENTS =3D=3D
> ...
>
> -- Section 5 --
> Is there any reason why the doc shepherd is not acknowledged ?

I don't feel any need to be listed in the acknowledgements. While I
did do the Shepherd write up (PROTO), I really don't recall making any
suggestions for change to this draft which is by two experienced
authors. My general policy, when I am an author, is to acknowledge
people whose comments resulted in technical or substantial editorial
changes, If the Shepherd should be listed just because they are the
Shepherd then why shouldn't the Chair(s) and AD be listed in the
Acknowledgements?

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


From nobody Tue May 18 21:10:30 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2613A1CEB; Tue, 18 May 2021 21:10:29 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 EMg92n2MJm4T; Tue, 18 May 2021 21:10:24 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 0EFFC3A1CEC; Tue, 18 May 2021 21:10:20 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id o17-20020a17090a9f91b029015cef5b3c50so2766153pjp.4;  Tue, 18 May 2021 21:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AjMGJIjYo6YcbM9kfF1zDrJi+HP9q+vKr8CcxDvz75s=; b=k5nO+6kwrgDYOUAGCoq2Pg4ECn7Cdl1zSJ/gcEi6scnCY4+BlXaTW+gedvxOipM4UI rRjw3d6FP+RwMakPLHtvWhW4GHq+C2haj8A/2SzVo4KUouvxqFt5AUJCWvb0eyPAg4Tb O9ySmNiExeogGEN+8+hg11qfsH+HzxHo36jgvcMW5kZzwn/H1yHsLy8urYXq81tgOFQe l2TfCurQdX50/4BZ9A2pLeRiY0arg4Oto+9P+dnscxf/p6OUr72Fgwhr2hlWVHUMZUE2 xUpNvNrOCNZZQn9lE7AUCrCx8jbvABjYJmnc5RqadhfQ6zVINMsx+JUxxPFqgoXkM5N5 RSUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AjMGJIjYo6YcbM9kfF1zDrJi+HP9q+vKr8CcxDvz75s=; b=J/d88X+PWCjIL9DsXKr1wX1kcsxvxXuteRIUAou9iVuLXBp1aWAsgBEnHKQ3HhUVdt 3tsR1W7IixqyDkl3jWt/j+KRqsGpbusoOUnjqRRRLxHA1zTSx5kCjogukhw2E6skikr8 RvpmLB/mFs7Vrba8CeBbrDunJ0hiuF9F+LYjUDIjdRGt1NFPPgdYklLoLFa//E3V26ZD pgdBW02/q60cw3sDeHrRUmaSDOpN63ERA2EgZbRd7UO4Rz5f060kTnPBA8MMtFjX9nRm RDAbIExE29oTYiA0OGJ9Ffa4t4kaM002N8J57ZeI0cwSn5+DKCky3zWcFXfN/faME3tZ 5rDQ==
X-Gm-Message-State: AOAM532kv0CJ4TBg45WTBvkacIveXxZmlHwBZbyhvtDJJZikOGolG8pd uHmIKmprZl66qlXQTeq6LAY=
X-Google-Smtp-Source: ABdhPJxDN6VGd34HPfh00wvJukgAUfO97zJn4oDiNNxS3tnPXBZt8EY6XxDz6cwnsNk9XoNdf7w1Vg==
X-Received: by 2002:a17:90a:8902:: with SMTP id u2mr9386477pjn.143.1621397418956;  Tue, 18 May 2021 21:10:18 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:6d33:9714:88ad:dd50? ([2601:647:5600:5020:6d33:9714:88ad:dd50]) by smtp.gmail.com with ESMTPSA id v18sm13826206pff.90.2021.05.18.21.10.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 May 2021 21:10:18 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <39A68691-1C3F-4EF8-8621-D2FC5707B5AA@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2AAB24A4-C81F-482B-BF2A-483D7E086F46"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 18 May 2021 21:10:17 -0700
In-Reply-To: <162124475990.8618.15255310968103028424@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
To: =?utf-8?Q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
References: <162124475990.8618.15255310968103028424@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/LNt4r5P2RJAFxyE-UChsDubM4Dc>
Subject: Re: [babel]  =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-bab?= =?utf-8?q?el-yang-model-10=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 04:10:29 -0000

--Apple-Mail=_2AAB24A4-C81F-482B-BF2A-483D7E086F46
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Eric,

Thank you for the review. See inline.

> On May 17, 2021, at 2:45 AM, =C3=89ric Vyncke via Datatracker =
<noreply@ietf.org> wrote:
>=20
> =C3=89ric Vyncke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: Discuss
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> Thank you for the work put into this document. I really like the fact =
that the
> information model is built before the data model. Congratulations !
>=20
> Please find below one blocking (but trivial to fix) DISCUSS point, =
some
> non-blocking COMMENT points (but replies would be appreciated), and =
one nit.
>=20
> Thank you to Donald Eastlake for his shepherd's write-up (including =
the WG
> consensus).
>=20
> I hope that this helps to improve the document,
>=20
> Regards,
>=20
> -=C3=A9ric
>=20
> =3D=3D DISCUSS =3D=3D
>=20
> The YANG module does not compile correctly with PYANG, it should be =
easy to fix
> though :-) See: =
https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html
> Or is it a PYANG error ?

This is a tooling error (even though I have gone ahead and changed it in =
the model). The ABNF grammar says the following for identity-stmt in RFC =
7950.

   identity-stmt       =3D identity-keyword sep identifier-arg-str =
optsep
                         (";" /
                          "{" stmtsep
                              ;; these stmts can appear in any order
                              *if-feature-stmt
                              *base-stmt
                              [status-stmt]
                              [description-stmt]
                              [reference-stmt]
                          "}") stmtsep

According to it, the =E2=80=98if-feature=E2=80=99 and =E2=80=98base-stmt=E2=
=80=99 can appear in any order. But for some reason pyang version 2.4.0 =
insists on a particular order. I will bring this up with tooling folks.

>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> =3D=3D COMMENTS =3D=3D
>=20
> The related links on should be updated. E.g., the YANG catalog entry =
should be:
> =
https://www.yangcatalog.org/yang-search/module_details.php?module=3Dietf-b=
abel@2021-05-12
>=20
> -- Section 2.2 --
> I usually use the expanded tree view rather the YANG module itself to =
get a
> global view. Is there any reason why the full tree view is not =
included?

Added this to the Appendix.

>=20
> -- Section 5 --
> Is there any reason why the doc shepherd is not acknowledged ?
>=20
> =3D=3D NITS =3D=3D
>=20
> -- Section 2.3 --
> s/MAC based security/MAC-based security/ ?

Fixed.

Thanks.

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_2AAB24A4-C81F-482B-BF2A-483D7E086F46
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
dir=3D"auto" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;" class=3D"">Hi Eric,<div class=3D""><br =
class=3D""></div><div class=3D"">Thank you for the review. See =
inline.<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 17, 2021, at 2:45 AM, =C3=89ric Vyncke =
via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
class=3D"">noreply@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">=C3=89=
ric Vyncke has entered the following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: Discuss<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Thank you for the work put into =
this document. I really like the fact that the<br class=3D"">information =
model is built before the data model. Congratulations !<br class=3D""><br =
class=3D"">Please find below one blocking (but trivial to fix) DISCUSS =
point, some<br class=3D"">non-blocking COMMENT points (but replies would =
be appreciated), and one nit.<br class=3D""><br class=3D"">Thank you to =
Donald Eastlake for his shepherd's write-up (including the WG<br =
class=3D"">consensus).<br class=3D""><br class=3D"">I hope that this =
helps to improve the document,<br class=3D""><br class=3D"">Regards,<br =
class=3D""><br class=3D"">-=C3=A9ric<br class=3D""><br class=3D"">=3D=3D =
DISCUSS =3D=3D<br class=3D""><br class=3D"">The YANG module does not =
compile correctly with PYANG, it should be easy to fix<br =
class=3D"">though :-) See: =
https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html<br =
class=3D"">Or is it a PYANG error ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>This is a =
tooling error (even though I have gone ahead and changed it in the =
model). The ABNF grammar says the following for identity-stmt in RFC =
7950.</div><div><br class=3D""></div><div><pre class=3D"newpage" =
style=3D"font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; =
break-before: page; font-variant-ligatures: normal; orphans: 2; widows: =
2; text-decoration-thickness: initial;">   identity-stmt       =3D =
identity-keyword sep identifier-arg-str optsep
                         (";" /
                          "{" stmtsep
                              ;; these stmts can appear in any order
                              *if-feature-stmt
                              *base-stmt
                              [status-stmt]
                              [description-stmt]
                              [reference-stmt]
                          "}") stmtsep
</pre><div class=3D""><br class=3D""></div><div class=3D"">According to =
it, the =E2=80=98if-feature=E2=80=99 and =E2=80=98base-stmt=E2=80=99 can =
appear in any order. But for some reason pyang version 2.4.0 insists on =
a particular order. I will bring this up with tooling folks.</div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">=3D=3D COMMENTS =3D=3D<br =
class=3D""><br class=3D"">The related links on should be updated. E.g., =
the YANG catalog entry should be:<br class=3D""><a =
href=3D"https://www.yangcatalog.org/yang-search/module_details.php?module=3D=
ietf-babel@2021-05-12" =
class=3D"">https://www.yangcatalog.org/yang-search/module_details.php?modu=
le=3Dietf-babel@2021-05-12</a><br class=3D""><br class=3D"">-- Section =
2.2 --<br class=3D"">I usually use the expanded tree view rather the =
YANG module itself to get a<br class=3D"">global view. Is there any =
reason why the full tree view is not included?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Added this =
to the Appendix.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">-- Section 5 =
--<br class=3D"">Is there any reason why the doc shepherd is not =
acknowledged ?<br class=3D""><br class=3D"">=3D=3D NITS =3D=3D<br =
class=3D""><br class=3D"">-- Section 2.3 --<br class=3D"">s/MAC based =
security/MAC-based security/ ?<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div>Fixed.</div><div><br =
class=3D""></div><div>Thanks.</div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_2AAB24A4-C81F-482B-BF2A-483D7E086F46--


From nobody Tue May 18 23:42:20 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFB363A1428; Tue, 18 May 2021 23:42:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <162140653428.10531.12882764411636560226@ietfa.amsl.com>
Date: Tue, 18 May 2021 23:42:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/qHU_bAqDp16qph21E0q2JL2KAwI>
Subject: [babel] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-babel-yang-model-10=3A_=28with_COMMENT=29?=
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 06:42:15 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-babel-yang-model-10: No Objection

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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you Mahesh for the YANG syntax information, it is clear that the PYANG
tool is plain wrong. I have cleared my DISCUSS position (but keeping the text
below for archive purpose), I also noted that you replied/acted upon my
original COMMENT

Regards

-éric

--- Start of archive (to be ignored) ---

Thank you for the work put into this document. I really like the fact that the
information model is built before the data model. Congratulations !

Please find below one blocking (but trivial to fix) DISCUSS point, some
non-blocking COMMENT points (but replies would be appreciated), and one nit.

Thank you to Donald Eastlake for his shepherd's write-up (including the WG
consensus).

I hope that this helps to improve the document,

Regards,

-éric

== DISCUSS ==

The YANG module does not compile correctly with PYANG, it should be easy to fix
though :-) See: https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html
Or is it a PYANG error ?

== COMMENTS ==

The related links on should be updated. E.g., the YANG catalog entry should be:
https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-babel@2021-05-12

-- Section 2.2 --
I usually use the expanded tree view rather the YANG module itself to get a
global view. Is there any reason why the full tree view is not included?

-- Section 5 --
Is there any reason why the doc shepherd is not acknowledged ?

== NITS ==

-- Section 2.3 --
s/MAC based security/MAC-based security/ ?




From nobody Wed May 19 08:18:32 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C2B3A1421; Wed, 19 May 2021 08:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 hxgR5i_COK_5; Wed, 19 May 2021 08:18:21 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 976A53A1426; Wed, 19 May 2021 08:18:20 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id v14so6957939pgi.6; Wed, 19 May 2021 08:18:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XvN23qW6bBeGduRTXJLbnUsLqRGV9rtOK/4Q9LFoG9E=; b=QdxuUBwEHNFSyLAzLZgEi98kd04WEwhVcjQvFDgsAtaD0Awftzu9LAFOxeE8EsNbR7 c+7SMJYE+/cNO1n35hClVsmw1X7ZScXiktGJga2I9tHo9133frmMTznYWYgpQIvUXzUV +vy9PnmvDdoxWGreDTl7o5/fuChODuaqC130g5GeBGgmyifamKY4IhFWPGIOYDH4Gb9p kbW0FJnAV6HxQZX/3iipZ9goKoQWz9BQoIIFUSCAUjY5ysHrVy0pOwLzsEZdtVXzVta7 ck3RWSIqy6UWprQppvrzhJVKnFiLfFx/YPxBoBw3Z5WQZOndrm0z6DVQgqZER+drYiM5 iVUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XvN23qW6bBeGduRTXJLbnUsLqRGV9rtOK/4Q9LFoG9E=; b=cLH8uUvZCiHVNK6lstuxRkp09AKoeY5rNclnNvH2b4qiwdJsiUN3aI5zTSW1JODpDr XR/W0xGMArC6MnYkKVHi7dRKnU69SUXLYEllZDAInMN+SIoPnvTkLLE63KqItPSP+Vic F7RPWmSjeScNl7QnK2mI1BCixxjpQN4Ew3EITf4PDETHb0xm/C8+PDasP6jYo0w/sECo OaMxL/aID2Mayy2quKQgFm87KapyfcXDkbanGRn2rgwNfLGFG4FKz/TjrHdwS5UsIrCx OJmeK1GOo3vYfK8BdWLPGv7jjbQjJ2vXyLXoKPM+oP1Zp8x0DWZ/LXu2YNovSz58E+J1 G4ow==
X-Gm-Message-State: AOAM530PIToTYduFQtzvrFuIwbG42p2T7W8AgJsZB1N8XaoeKnqAMjRW l110fcjQS0JssYKk1oSbyUg=
X-Google-Smtp-Source: ABdhPJxx7GXGx0p5/JoH/Ttzqzz3fMSfoMvSrHh+bt2SawWuqb44rcvg4oPjtCo3L/c8bJwr6tOaaw==
X-Received: by 2002:aa7:839a:0:b029:27a:8c0b:3f5e with SMTP id u26-20020aa7839a0000b029027a8c0b3f5emr11120916pfm.69.1621437499508;  Wed, 19 May 2021 08:18:19 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:2058:9156:1cae:4ffc? ([2601:647:5600:5020:2058:9156:1cae:4ffc]) by smtp.gmail.com with ESMTPSA id t22sm1055589pfg.119.2021.05.19.08.18.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 May 2021 08:18:18 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <A5BAF28D-8856-482A-AA5E-F41ED3BA9BD2@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3E36B04-A891-4699-B856-5C22CE633E67"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 19 May 2021 08:18:16 -0700
In-Reply-To: <20210519.084054.1713468977677987317.id@4668.se>
Cc: =?utf-8?Q?=C3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
References: <162124475990.8618.15255310968103028424@ietfa.amsl.com> <39A68691-1C3F-4EF8-8621-D2FC5707B5AA@gmail.com> <20210519.084054.1713468977677987317.id@4668.se>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/5JQqt3chfyidC--BhKtoNdBqJmk>
Subject: Re: [babel]  =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-bab?= =?utf-8?q?el-yang-model-10=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 15:18:27 -0000

--Apple-Mail=_F3E36B04-A891-4699-B856-5C22CE633E67
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Martin,

> On May 18, 2021, at 11:40 PM, Martin Bj=C3=B6rklund <mbj+ietf@4668.se> =
wrote:
>=20
> Hi,
>=20
>>>=20
>>> The YANG module does not compile correctly with PYANG, it should be
>>> easy to fix
>>> though :-) See:
>>> https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html
>>> Or is it a PYANG error ?
>>=20
>> This is a tooling error (even though I have gone ahead and changed it
>> in the model). The ABNF grammar says the following for identity-stmt
>> in RFC 7950.
>>=20
>>   identity-stmt       =3D identity-keyword sep identifier-arg-str =
optsep
>>                         (";" /
>>                          "{" stmtsep
>>                              ;; these stmts can appear in any order
>>                              *if-feature-stmt
>>                              *base-stmt
>>                              [status-stmt]
>>                              [description-stmt]
>>                              [reference-stmt]
>>                          "}") stmtsep
>>=20
>> According to it, the =E2=80=98if-feature=E2=80=99 and =E2=80=98base-stm=
t=E2=80=99 can appear in any
>> order. But for some reason pyang version 2.4.0 insists on a =
particular
>> order. I will bring this up with tooling folks.
>=20
> This is not a tooling error.  The error message is:
>=20
>  ietf-babel@2021-05-12.yang <mailto:ietf-babel@2021-05-12.yang>:148: =
error: keyword "if-feature" not in
>    canonical order (see RFC 6020, Section 12)
>=20
> [side note: the RFC ref in this error message should be updated to RFC
> 7950 Section 14]
>=20
> The referenced section says:
>=20
>   The ABNF grammar [RFC5234] [RFC7405] defines the canonical order.
>=20
> When we publish YANG models in RFCs we use the canonical order in
> order to have a consistent format.  pyang checks this when the flag
> --ietf is used.

I am trying to understand, and this is more for my education, what rule =
within the grammar is determining the canonical order?

Also, should pyang report this as an error, or maybe a warning might be =
better? After all, this is being done for consistency reasons.

>=20
>=20
> /martin
>=20
>=20
>=20
>>=20
>>>=20
>>>=20
>>>=20
>> =
----------------------------------------------------------------------
>>> COMMENT:
>>>=20
>> =
----------------------------------------------------------------------
>>>=20
>>> =3D=3D COMMENTS =3D=3D
>>>=20
>>> The related links on should be updated. E.g., the YANG catalog entry
>>> should be:
>>> =
https://www.yangcatalog.org/yang-search/module_details.php?module=3Dietf-b=
abel@2021-05-12
>>>=20
>>> -- Section 2.2 --
>>> I usually use the expanded tree view rather the YANG module itself =
to
>>> get a
>>> global view. Is there any reason why the full tree view is not
>>> included?
>>=20
>> Added this to the Appendix.
>>=20
>>>=20
>>> -- Section 5 --
>>> Is there any reason why the doc shepherd is not acknowledged ?
>>>=20
>>> =3D=3D NITS =3D=3D
>>>=20
>>> -- Section 2.3 --
>>> s/MAC based security/MAC-based security/ ?
>>=20
>> Fixed.
>>=20
>> Thanks.
>>=20
>> Mahesh Jethanandani
>> mjethanandani@gmail.com

Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_F3E36B04-A891-4699-B856-5C22CE633E67
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Martin,<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 18, 2021, at 11:40 PM, Martin =
Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi,</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The YANG =
module does not compile correctly with PYANG, it should be<br =
class=3D"">easy to fix<br class=3D"">though :-) See:<br class=3D""><a =
href=3D"https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html" =
class=3D"">https://yangcatalog.org/results/ietf-babel@2021-05-12_ietf.html=
</a><br class=3D"">Or is it a PYANG error ?<br class=3D""></blockquote><br=
 class=3D"">This is a tooling error (even though I have gone ahead and =
changed it<br class=3D"">in the model). The ABNF grammar says the =
following for identity-stmt<br class=3D"">in RFC 7950.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;identity-stmt =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D identity-keyword sep =
identifier-arg-str optsep<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;(";" /<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;"{" stmtsep<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;; these stmts can appear in any =
order<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*if-feature-stmt<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*base-stmt<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[status-stmt]<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[description-stmt]<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[reference-stmt]<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;"}") stmtsep<br class=3D""><br class=3D"">According to it, =
the =E2=80=98if-feature=E2=80=99 and =E2=80=98base-stmt=E2=80=99 can =
appear in any<br class=3D"">order. But for some reason pyang version =
2.4.0 insists on a particular<br class=3D"">order. I will bring this up =
with tooling folks.<br class=3D""></blockquote><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">This is not a tooling error. &nbsp;The error message =
is:</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">&nbsp;</span><a=
 href=3D"mailto:ietf-babel@2021-05-12.yang" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">ietf-babel@2021-05-12.yang</a><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">:148: error: keyword "if-feature" not in</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">&nbsp;&nbsp;&nbsp;canonical =
order (see RFC 6020, Section 12)</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">[side note: the RFC ref in this error message should be =
updated to RFC</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">7950 Section 14]</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">The referenced section says:</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&nbsp;&nbsp;The ABNF grammar [RFC5234] [RFC7405] defines the =
canonical order.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">When we publish YANG models in RFCs we use the canonical =
order in</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">order to have =
a consistent format. &nbsp;pyang checks this when the flag</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">--ietf is used.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote><div><br class=3D""></div>I am trying to =
understand, and this is more for my education, what rule within the =
grammar is determining the canonical order?</div><div><br =
class=3D""></div><div>Also, should pyang report this as an error, or =
maybe a warning might be better? After all, this is being done for =
consistency reasons.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">/martin</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D""><br class=3D""><br =
class=3D""></blockquote>--------------------------------------------------=
--------------------<br class=3D""><blockquote type=3D"cite" =
class=3D"">COMMENT:<br class=3D""><br =
class=3D""></blockquote>--------------------------------------------------=
--------------------<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">=3D=3D COMMENTS =3D=3D<br class=3D""><br =
class=3D"">The related links on should be updated. E.g., the YANG =
catalog entry<br class=3D"">should be:<br class=3D""><a =
href=3D"https://www.yangcatalog.org/yang-search/module_details.php?module=3D=
ietf-babel@2021-05-12" =
class=3D"">https://www.yangcatalog.org/yang-search/module_details.php?modu=
le=3Dietf-babel@2021-05-12</a><br class=3D""><br class=3D"">-- Section =
2.2 --<br class=3D"">I usually use the expanded tree view rather the =
YANG module itself to<br class=3D"">get a<br class=3D"">global view. Is =
there any reason why the full tree view is not<br class=3D"">included?<br =
class=3D""></blockquote><br class=3D"">Added this to the Appendix.<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">-- Section 5 --<br class=3D"">Is there any reason why the doc =
shepherd is not acknowledged ?<br class=3D""><br class=3D"">=3D=3D NITS =
=3D=3D<br class=3D""><br class=3D"">-- Section 2.3 --<br class=3D"">s/MAC =
based security/MAC-based security/ ?<br class=3D""></blockquote><br =
class=3D"">Fixed.<br class=3D""><br class=3D"">Thanks.<br class=3D""><br =
class=3D"">Mahesh Jethanandani<br class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></blockquote></div></blockquote></di=
v><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_F3E36B04-A891-4699-B856-5C22CE633E67--


From nobody Wed May 19 09:11:57 2021
Return-Path: <toke@toke.dk>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482B83A15E8; Wed, 19 May 2021 09:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=toke.dk
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 b27K6c_ntoT5; Wed, 19 May 2021 09:11:50 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55A323A1636; Wed, 19 May 2021 09:11:49 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1621440706; bh=0f5Bf70Qwe9R7YY1UzlIoSLtXslguxu64IOXac7R5dk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=jPC0Ol7KZQqGfGSp7fPZ4G7742WU6jHifS0hL0maYQr6W5xzg2UHmtLQJ0DiNK2bm dQG1IJei8L00+dkEDBwrGzLphuDAl2Y0eL65EpYH9E4o+esJPBhh5J5I/bsFVAMc7l E77k1jbj9QAoHvhdsexhb/zBe/KaWGt47enwem7pRh1DE+tM3UIt/X4kOahqa/0DqV rKkZvRAyZfhW8PfTeyjHB93GZKsXirquGWgpabe9rnzfMF/a0XopL7GS18GyRBY40j 6HATxqln4hHPeMAfzo3aAzTm851XOYm5PWZ20oVY6Nhwxz3/ehebV1rF8KoqsYGyp7 kDkNpXuuSiC3g==
To: Donald Eastlake <d3e3e3@gmail.com>, Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
In-Reply-To: <CAF4+nEHpePFnypWuM_rVzjCqZFuDjNJyc-nPKOhzAb74Mm09Xw@mail.gmail.com>
References: <161902119477.7566.8966155269813261543@ietfa.amsl.com> <CAF4+nEHpePFnypWuM_rVzjCqZFuDjNJyc-nPKOhzAb74Mm09Xw@mail.gmail.com>
Date: Wed, 19 May 2021 18:11:43 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87h7iy1z5s.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/b8hyVsY__BZaNZyvmuCBnITtqHY>
Subject: Re: [babel] WG Last Call on draft-ietf-babel-v4viav6-03.txt through 5 May
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 16:11:56 -0000

Donald Eastlake <d3e3e3@gmail.com> writes:

> Hi,
>
> I don't think there are any current open questions on this draft so I
> am beginning a WG Last call through Cinco de Mayo.

I support publication (and will try to get around to implementing this
as well!).

-Toke


From nobody Wed May 19 13:31:38 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C543B3A1E13; Wed, 19 May 2021 13:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 w-3HpOBmcVGE; Wed, 19 May 2021 13:31:31 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 669C33A1E14; Wed, 19 May 2021 13:31:31 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id d24so14353611ios.2; Wed, 19 May 2021 13:31:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KeXB177dwV+8sxRQwUS0e/LeiCJ4FjLKDrd0J8P/C6o=; b=OPOawKJq4l5bcPnIKIvsSFGaskDZ0f2iAXBclGKzTkcXsgO+yy4lYoIK6aH+K6+VAY IYnuBKTKsVK1WYobEeu/DUeDcQ+b6g0ppmDRSUKlsNQDNpwOUKu32ZXL/hYT+ayNjJcI ZaGfNVDaejPNpyBIj0o4bU6m4/egJvaIwfxzGFT0Y9mOUWMtrrEcuXOvRHODkH1vGh08 CAXwuwIZfNbxfY1+4w8OElGA7h6kigCHSlY6Rxicd9xt1Jz6sSNRytPDikEw+pK+ipkk XXbcbwI/x0FmWz2EGSj+uv2IBaWZGSLMsI6JiGJzEH0BFXpjC59IcK5SbopCf/semo6M bEwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KeXB177dwV+8sxRQwUS0e/LeiCJ4FjLKDrd0J8P/C6o=; b=gC4Vk4wYoOrIWB+SmJ/WkQ09zglh/3jzA7ckUA3ZTLiSgHKn91s43S8PQhElfbIxxz 4EQJVwk8a5FcHCYQU4SblHy8lwxeOe/X5dRuRbuD7Edyqrx0aY7BQFuL4olRYDAjGzHL upcXYZjCQW8Kra7U0NUMLya7grlKxEfG+epOZ902U0A0xEfF2D4HWfmCY0S+U9doaJh6 poNXf0X1bWQyYDZA2dwXLRFNWtsratdJgntY1uUcCDWw7/pts37PmCiKvB2bNQnUKDMF E15Wg7gUHNCN+UcbWHbd4UGaP0xmViw9bCw8k0xv+RCMro7+D3xghITuTa5lZVN3jSfp YA4w==
X-Gm-Message-State: AOAM532b+X2JBTEhvGOAz+0DjP8FQInfAWV/jdMyvATXof6O+E57ECTL BIygVr20+/ZOlLRIZqD4jpZQ6SJcl2JHNfa/AqJ1EX9Fm6c=
X-Google-Smtp-Source: ABdhPJxbTsDrNriYNOr4gGnMx7jVZqJJYS6B9sF5u1DMJloYtR+evzMZAuP8uNZ1u1cu5JXyoYDLpOhCbkmT0R6koiI=
X-Received: by 2002:a5d:8d87:: with SMTP id b7mr1351296ioj.46.1621456289454; Wed, 19 May 2021 13:31:29 -0700 (PDT)
MIME-Version: 1.0
References: <161902119477.7566.8966155269813261543@ietfa.amsl.com> <CAF4+nEHpePFnypWuM_rVzjCqZFuDjNJyc-nPKOhzAb74Mm09Xw@mail.gmail.com>
In-Reply-To: <CAF4+nEHpePFnypWuM_rVzjCqZFuDjNJyc-nPKOhzAb74Mm09Xw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 19 May 2021 16:31:18 -0400
Message-ID: <CAF4+nEGQE74h5qJ2d1W5_BTLc=_vBtTttPfVT15wpfvto4SV0w@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/sOXsSZqQhhREPREGRVTV2JuJpf8>
Subject: [babel] Consensus Call for draft-ietf-babel-v4viav6
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 20:31:36 -0000

Hi,

Based on the support shown when this was discussed at the Babel WG
meetings at IETF 108 and 110, comments on the mailing list, and the
responses to the WG Last Call, I judge that this draft has WG
consensus and will request publication.

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

On Wed, Apr 21, 2021 at 4:02 PM Donald Eastlake <d3e3e3@gmail.com> wrote:
>
> Hi,
>
> I don't think there are any current open questions on this draft so I
> am beginning a WG Last call through Cinco de Mayo.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Wed, Apr 21, 2021 at 12:07 PM
> Subject: [babel] I-D Action: draft-ietf-babel-v4viav6-03.txt
> To: <i-d-announce@ietf.org>
> Cc: <babel@ietf.org>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Babel routing protocol WG of the IETF.
>
>         Title           : IPv4 routes with an IPv6 next-hop in the
> Babel routing protocol
>         Author          : Juliusz Chroboczek
>         Filename        : draft-ietf-babel-v4viav6-03.txt
>         Pages           : 9
>         Date            : 2021-04-21
>
> Abstract:
>    This document defines an extension to the Babel routing protocol that
>    allows annoncing routes to an IPv4 prefix with an IPv6 next-hop,
>    which makes it possible for IPv4 traffic to flow through interfaces
>    that have not been assigned an IPv4 address.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-babel-v4viav6/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-babel-v4viav6-03
> https://datatracker.ietf.org/doc/html/draft-ietf-babel-v4viav6-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-babel-v4viav6-03
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/


From nobody Wed May 19 15:26:42 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258E73A218C; Wed, 19 May 2021 15:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 R1ItP5nvqADY; Wed, 19 May 2021 15:26:37 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 11FA53A218A; Wed, 19 May 2021 15:26:36 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id j30so13552960ila.5; Wed, 19 May 2021 15:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=l+MU1yoycGPK8MAWKYjk7PNsuYnXrRHPNViHbOpChuc=; b=QibMENf9C6NWqMvcxldcNFjBv0bR+3gGtcVm51kcTvB3lKJLgOc1YQ6zbI1aIvGrA4 6ycITmrv9KPRddn6mt0qF9VSVWJHZ9hjiaNELQ7hdg3VPMM4eiik46MOeLXgYgHNzl6K 4fcHv3M1Cq3G/iKu/RHJ0OY495Fx/hJmz02tpKAXzihwCY2h6fx2SL2Ou13CYPjGwrue VQDhFDsTlxDaAmiO/joYR5thwem3sioCFmVDRMVChIY5KY0LwiuRJ2ERlcfFSZnzetDs Sm2u5vjUlTP4gr2qZfIkSUnmkNpihQ2tipwUkLnEONGgvEQymlLm3Pic2JsT10arpjna 0neg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=l+MU1yoycGPK8MAWKYjk7PNsuYnXrRHPNViHbOpChuc=; b=ZbpOBqX4IbLuxsmXLpVQzi+iCWefbrg3HmF2h02y+xZszrkhFv3hbzyMbPMjnxBHc6 QBVdK95j6fNDNsLE5KTbdaP8hJuFsDoJIju3/pO39LX7x1ePiKxjeHhD0LC2RTtcWbnz jjp5+cEPha0+rvl9uE5POTp85P5u59jGbYlGHDGATrdwBKS+yy2Ueu+VXsAgNakjgSfX mKOWaZXHHHn+ED50Xo7eNMoCQtEutRqg9+FnAGv9hiQMIoZYBCdkRvE6E4Wos6kVCa+4 BPq9+eRtlyizchAWal931dN2vR7iXo1/GsK2wJRpfKJt8LlLJjs0U7Fpz7f+aDZMG6z+ BfKA==
X-Gm-Message-State: AOAM533IGmNaVfZF3MR/fqgN7FiDqORNor/zE9FitHKql5PtQXFsRNDW gOoPoeVxBh/uc1yNC0wrpkWpFzGvWpWOZmX5OYoeMeUizMgD2g==
X-Google-Smtp-Source: ABdhPJwf1UxaoItYrRiLbf5o9+jalNStJFmAqp4PsTSkTBcQ0jtoMnJd5FlMVMXGARUnmm8FQ4Qk+VJLYbGGLjS7puA=
X-Received: by 2002:a92:6b05:: with SMTP id g5mr1509483ilc.40.1621463195399; Wed, 19 May 2021 15:26:35 -0700 (PDT)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 19 May 2021 18:26:24 -0400
Message-ID: <CAF4+nEGXt+x6BsQNuXwL7MMgChEB574=dW77_y71XMoL_J1rBw@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c73b8f05c2b65151"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI>
Subject: [babel] Shepherd review of draft-ietf-babel-v4viav6-03
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2021 22:26:40 -0000

--000000000000c73b8f05c2b65151
Content-Type: text/plain; charset="UTF-8"

Hi,

I've done a review of this draft as Shepherd. See below:


INTRODUCTION

The introduction is generally quite good but, in the first paragraph, some
wording feels just the slightest bit off.  For example, it appears to
assume that ND or ARP would always be used when the next-hop to link-
layer address mapping might be statically configured in a wired portion
of a network. Here is some suggested text for the author's
consideration:
OLD
   Traditionally, a routing table maps a network prefix of a given
   address family to a next-hop address in the same address family.  The
   sole purpose of this next-hop address is to serve as an input to a
   protocol that will map it to a link-layer address, Neighbour
   Discovery (ND) [RFC4861] in the case of IPv6, Address Resolution
   (ARP) [RFC0826] in the case of IPv4.  Therefore, there is no reason
   why the address family of the next hop address should match that of
   the prefix being announced: an IPv6 next-hop yields a link-layer
   address that is suitable for forwarding both IPv6 or IPv4 traffic.
NEW
   Traditionally, a routing table maps a network prefix in a given
   address family to a next-hop address in the same address family.
   The sole use of this next-hop address is to determine the
   link-layer address of the next-hop node, for example using
   Neighbour Discovery (ND) [RFC4861] in the case of IPv6 or Address
   Resolution (ARP) [RFC0826] in the case of IPv4.  Therefore, the
   address family of this next-hop address need not match that of the
   prefix being announced: an IPv6 next-hop can determine a link-layer
   address that is suitable for forwarding both IPv6 and IPv4 traffic.



IANA CONSIDERATIONS

Globally TDB -> 4
Also:
OLD
   IANA is requested to allocate a value (4 suggested) in the "Babel
   Address Encodings" registry as follows:

                   +=====+===========+=================+
                   | AE  | Name      | Reference       |
                   +=====+===========+=================+
                   | TBD | v4-via-v6 | (this document) |
                   +-----+-----------+-----------------+
NEW
   IANA has assigned the value 4 in the "Babel Address Encodings"
   registry as follows:

                   +=====+===========+=================+
                   | AE  | Name      | Reference       |
                   +=====+===========+=================+
                   |  4  | v4-via-v6 | (this document) |
                   +-----+-----------+-----------------+



REFERENCES

Update reference to RFC 5549 to RFC 8950.



TRIVIA

Section 2, 1st line: It is more common in IETF documents to say
"dual-stack" rather than "double-stack".

anoncing -> announcing

annoucements -> announcements

administatoris -> administrators

next hop -> next-hop   (7 times)

eg. -> e.g.   (twice)

It would be preferable, within the Normative and the Informative
References, that RFCs be listed in numeric order.

I notice this draft generally uses British spelling. I think that's OK
as long as it is consistent.



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

--000000000000c73b8f05c2b65151
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;ve done a review of this draf=
t as Shepherd. See below:</div><div><br></div><div><br></div><div>INTRODUCT=
ION<br><br>The introduction is generally quite good but, in the first parag=
raph, some<br>wording feels just the slightest bit off.=C2=A0 For example, =
it appears to<br>assume that ND or ARP would always be used when the next-h=
op to link-<br>layer address mapping might be statically configured in a wi=
red portion<br>of a network. Here is some suggested text for the author&#39=
;s<br>consideration:<br>OLD<br>=C2=A0 =C2=A0Traditionally, a routing table =
maps a network prefix of a given<br>=C2=A0 =C2=A0address family to a next-h=
op address in the same address family.=C2=A0 The<br>=C2=A0 =C2=A0sole purpo=
se of this next-hop address is to serve as an input to a<br>=C2=A0 =C2=A0pr=
otocol that will map it to a link-layer address, Neighbour<br>=C2=A0 =C2=A0=
Discovery (ND) [RFC4861] in the case of IPv6, Address Resolution<br>=C2=A0 =
=C2=A0(ARP) [RFC0826] in the case of IPv4.=C2=A0 Therefore, there is no rea=
son<br>=C2=A0 =C2=A0why the address family of the next hop address should m=
atch that of<br>=C2=A0 =C2=A0the prefix being announced: an IPv6 next-hop y=
ields a link-layer<br>=C2=A0 =C2=A0address that is suitable for forwarding =
both IPv6 or IPv4 traffic.<br>NEW<br>=C2=A0 =C2=A0Traditionally, a routing =
table maps a network prefix in a given<br>=C2=A0 =C2=A0address family to a =
next-hop address in the same address family.<br>=C2=A0 =C2=A0The sole use o=
f this next-hop address is to determine the<br>=C2=A0 =C2=A0link-layer addr=
ess of the next-hop node, for example using<br>=C2=A0 =C2=A0Neighbour Disco=
very (ND) [RFC4861] in the case of IPv6 or Address<br>=C2=A0 =C2=A0Resoluti=
on (ARP) [RFC0826] in the case of IPv4.=C2=A0 Therefore, the<br>=C2=A0 =C2=
=A0address family of this next-hop address need not match that of the<br>=
=C2=A0 =C2=A0prefix being announced: an IPv6 next-hop can determine a link-=
layer<br>=C2=A0 =C2=A0address that is suitable for forwarding both IPv6 and=
 IPv4 traffic.<br><br><br><br>IANA CONSIDERATIONS<br><br>Globally TDB -&gt;=
 4</div><div>Also:<br>OLD<br>=C2=A0 =C2=A0IANA is requested to allocate a v=
alue (4 suggested) in the &quot;Babel<br>=C2=A0 =C2=A0Address Encodings&quo=
t; registry as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0+=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| AE =C2=A0| Name =
=C2=A0 =C2=A0 =C2=A0| Reference =C2=A0 =C2=A0 =C2=A0 |<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+=3D=3D=3D=3D=3D+=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D+<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0| TBD | v4-via-v6 | (this document) |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+-----+-----------+---------------=
--+<br>NEW<br>=C2=A0 =C2=A0IANA has assigned the value 4 in the &quot;Babel=
 Address Encodings&quot;<br>=C2=A0 =C2=A0registry as follows:<br><br>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+=3D=3D=3D=
=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D+<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0| AE =C2=A0| Name =C2=A0 =C2=A0 =C2=A0| Reference =C2=A0 =
=C2=A0 =C2=A0 |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0+=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A04 =C2=A0| v4-via-v6 | (thi=
s document) |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0+-----+-----------+-----------------+<br><br><br><br>REFERENCE=
S<br><br>Update reference to RFC 5549 to RFC 8950.<br><br><br><br>TRIVIA<br=
><br>Section 2, 1st line: It is more common in IETF documents to say<br>&qu=
ot;dual-stack&quot; rather than &quot;double-stack&quot;.<br><br>anoncing -=
&gt; announcing<br><br>annoucements -&gt; announcements<br><br>administator=
is -&gt; administrators<br><br>next hop -&gt; next-hop =C2=A0 (7 times)<br>=
<br>eg. -&gt; e.g. =C2=A0 (twice)<br><br>It would be preferable, within the=
 Normative and the Informative<br>References, that RFCs be listed in numeri=
c order.<br><br>I notice this draft generally uses British spelling. I thin=
k that&#39;s OK<br>as long as it is consistent.<br><br><div><div dir=3D"ltr=
" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><br></div><d=
iv dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"=
><br></div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gma=
il_signature">Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=C2=A0Donald E. E=
astlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A02386 Panoramic Circle, A=
popka, FL 32703 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gmail.com" target=3D"=
_blank">d3e3e3@gmail.com</a></div></div></div></div>

--000000000000c73b8f05c2b65151--


From nobody Wed May 19 21:09:56 2021
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85B1F3A2D93; Wed, 19 May 2021 21:09:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-yang-model@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <162148379451.10850.9563671396439074857@ietfa.amsl.com>
Date: Wed, 19 May 2021 21:09:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/my6fguik8hoi7f28rEiu6g8ViI0>
Subject: [babel] Benjamin Kaduk's Discuss on draft-ietf-babel-yang-model-10: (with DISCUSS and COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 04:09:55 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-babel-yang-model-10: 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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This is kind of nitpicky, and I'm sorry to pull out the heavy hammer of
DISCUSS for it, but for the "dtls-cached-info" leaf with description:

               "Indicates whether the cached_info extension is included
                in ClientHello and ServerHello packets. The extension
                is included if the value is 'true'.";

It is factually false to just say that "the extension is included if the
value is true", and it contradicts the DTLS specification to say so.  In
particular, the extension can only be included in the ServerHello
message if it was present in the ClientHello message being responded to.
So maybe we can say "enabled for inclusion" or append "when permitted by
the protocol", or something similar?

There's also a few places where we didn't quite clean up all the fallout
from switching from enumerations to identities (for MAC and
DTLS-adjacent algorithms), that really ought to get fixed before
publication.  I try to note them in the COMMENT.

I also think we need to be a bit more specific about the structure of
the (binary) private-key leaf/values provided when a certificate entry
is created.  Ideally this would just be by reference to some other spec,
but the situation is unfortunately messy.  (It doesn't help that we
allow DTLS 1.2, which allows certificates that are used for key-exchange
as opposed to signing, and those are not terribly mainstream.)  We may
need to pull in some other experts to figure out the right way to write
about this.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 2.2

   In addition to information like the version number implemented by
   this device, the model contains subtrees on 'constants',
   'interfaces', 'routes' and 'security'.

I don't see a 'security' node, but rather separate 'mac-key-set' and
'dtls' nodes, both of which contain subtrees.

Section 2.3

   A router running Babel routing protocol can determine the parameters
   it needs to use for an interface based on the interface name.  [...]

Is this always true, or only sometimes?

   Transport Layer Security Version 1.2 [RFC6347], The Blake2

(DTLS 1.3 is in the RFC Editor's queue, FWIW.)

         leaf router-id {
           type binary;
           description
             "router-id of the source router for which this route is
              advertised.";

IIRC we can do length constraints in YANG, and in Babel router-ids are 8
octets.  Should we enshrine that in the YANG?

         leaf next-hop {
           type inet:ip-address;
           description
             "The next-hop address of this route. This will be empty if
              this route has no next-hop address.";

What does it mean for an inet:ip-address to be "empty"?  That the node
is absent?

               "List of supported certificate types, in order of
                preference. The values MUST be among those listed in
                dtls-cert-types. This list is used to populate the

Since the element is of type leafref to the actual list of certs, it
seems like this MUST is achieved by construction (and thus need not be
listed specifically).  Though, "dtls-cert-types" appears in this
document only as the base identity for Babel DTLS certificate types, so
this phrasing seems a bit odd...perhaps it is fallout from an
enumeration/identity conversion.

                server_certificate_type extension in a Client Hello.
                Values that are present in at least one instance in the
                certs object under dtls of a referenced dtls instance
                and that have a non-empty private-key will be used to
                populate the client_certificate_type extension in a
                Client Hello.";

Since the DTLS server picks which certificate types are actually used,
it is conceivable that the preference order in this list could also be
used as input to the server's choice of type.  That said, I don't think
there is universal API support for DTLS servers accepting a preference
list directly, so we would not want to imply that this list would always
be used in such a fashion.  But it could be used in such a fashion.

           container stats {
             config false;
             description
               "Statistics collection object for this interface.";

Often, YANG models with such statistics containers will also include a
leaf to indicate the "discontinuity time" at which the counters were
last reset.

             leaf hello-mcast-history {
               type string;
               description
                 "The multicast Hello history of whether or not the
                  multicast Hello packets prior to exp-mcast-
                  hello-seqno were received, with a '1' for the most
                  recent Hello placed in the most significant bit and
                  prior Hellos shifted right (with '0' bits placed
                  between prior Hellos and most recent Hello for any
                  not-received Hellos); represented as a string using
                  utf-8 encoded hex digits where a '1' bit = Hello
                  received and a '0' bit = Hello not received.";

I'd consider adding a few more words to confirm that this is the hex
representation of a bitstring (so, all hex digits are possible), not a
string consisting of only '1' and '0' characters.
(Likewise for hello-ucast-history.)

             leaf exp-mcast-hello-seqno {
               type uint16;
               default "0";
               description
                 "Expected multicast Hello sequence number of next Hello
                  to be received from this neighbor; if multicast Hello
                  packets are not expected, or processing of multicast
                  packets is not enabled, this MUST be NULL.";

It's not really clear to me that assigning semantics to a NULL leaf
makes sense when there is a default value for it (that has already
assigned semantics to an absent leaf).
(et seq)

             leaf value {
               type binary;
               mandatory true;
               description
                 "The value of the MAC key. An implementation MUST NOT
                  allow this parameter to be read. This can be done by

I believe that we can incorporate this restriction in the YANG itself
with something like "nacm:default-deny-all".

               description
                 "The name of the MAC algorithm used with this key. The
                  value MUST be the same as one of the enumerations
                  listed in the mac-algorithms parameter.";

It's now an identityref, not a name.  Accordingly, there are also not
any enumerations listed in the mac-algorithms parameter.

               description
                 "The name of the certificate type of this object
                  instance. The value MUST be the same as one of the
                  enumerations listed in the dtls-cert-types
                  parameter. This value can only be provided when this

Similarly, this is also identityref, and also has no enumerations listed
in the dtls-cert-types parameter.

             leaf private-key {
               type binary;
               mandatory true;
               description
                 "The value of the private key. If this is non-empty,
                  this certificate can be used by this implementation to
                  provide a certificate during DTLS handshaking. An
                  implementation MUST NOT allow this parameter to be
                  read. This can be done by always providing an empty

(nacm:default-deny-all could be useful here as well)

                  string, or through permissions, or other means. This
                  value can only be provided when this instance is
                  created, and is not subsequently writable.";

It is perhaps a bit limiting to require the actual private key value to
be supplied, since that would preclude the use of (e.g.) HSM-based
private keys.  But since we are basically inheriting from the
information model here, I won't press it too hard.

Section 4

It might be worth referencing the security considerations of
8966/8967/8968 as being applicable.

The security (privacy, really) considerations of RFC 7924 are also
arguably relevant, relating to the use of the TLS "cached_info"
extension.

Are there any security and/or privacy considerations relating to the
logging of babel packets?

   There are a number of data nodes defined in the YANG module which are
   writable/created/deleted (i.e., config true, which is the default).

I don't think "writable/created/deleted" is part of the template.

   'babel/hmac' and 'babel/dtls': These contain security credentials
   that influence whether packets are trusted.

I'd consider making two separate (but related) points about controlling
whether incoming packets are trusted, and whether outgoing packets are
produced in a way such that the receiver will treat them as trusted.
(Changing just the use-send/use-verify values can allow for a valid key
to be misused, without changing the actual keys being used, which could
present an interesting attack in some scenarios.)

   Some of the readable data or config false nodes in this YANG module
   may be considered sensitive or vulnerable in some network
   [...]
   'babel/hmac' and 'babel/dtls': These contain security credentials,
   include private credentials of the router.

We do require the actual secret keys to not be readable, so we might
consider phrasing this more as a reiteration of that requirement than a
statement of risk if they are read out.

   Some of the RPC operations in this YANG module may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control access to these operations.  These are the
   operations and their sensitivity/vulnerability from a RPC operation
   perspective:

   This model does not define any RPC operations.

We do define a couple of actions, though, which are like RPCs except
"[t]he difference between an action and an rpc is that an action is tied
to a node in the datastore, whereas an rpc is not".  This is perhaps an
omission in the YANG security considerations template, but I don't think
we should let that stop us from noting the actions we define are
carefully designed to have minimal security impact and minimal
side-channel leakage.  (Well, I guess that's not hard for the
stats-reset one, but for the MAC key test one it's quite important.)

Section 6.1

I don't have a great sense for why RFC 4868 needs to be normative.

RFC 8968 seems missing as a listed reference at all (which would of
course need to be normative as 8967 is).

Section 6.2

I think RFC 7693 should be normative, since you need it in order to do
the blake2 stuff.

RFC 8341 might become normative if we add nacm:default-deny-all stanzas.

NITS

The tree diagram and the prose use different orders for the various
child elements, which is a little distracting.

Section 1

   [RFC8966].  The data model is defined using YANG 1.1 [RFC7950] data
   modeling language and is Network Management Datastore Architecture

"the YANG [data modeling language]"

Section 2.1

   Information Model and this data module.  The information model
   mandates the definition of some of the attributes, e.g.  'babel-

comma after "e.g." (as well as before).  (I'll try to only note it once,
though it appears many times.)  Likewise for "i.e."

Section 2.2

   In addition to information like the version number implemented by
   this device, the model contains subtrees on 'constants',

The actual data model (and the information model, for that matter) show
that the 'version' leaf contains "the name and version of this
implementation of the Babel protocol".  The text here suggests that it
contains the protocol version number implemented by the device, which is
different.  So I'd suggest "the implementation and version used by this
device" instead.

   The 'interfaces' subtree describes attributes such as 'interface'
   object that is being referenced, the type of link, e.g. wired,

"the 'interface'"

   wireless or tunnel, as enumerated by 'metric-algorithm' and 'split-
   horizon' and whether the interface is enabled or not.

I suggest using semicolons for the outer layer of grouping, to avoid
overloading commas for different hierarchies of separation.

   Finally, for security two subtree are defined to contain MAC keys and
   DTLS certificates.  The 'mac-key-set' subtree contains keys used with

"subtrees"

   interfaces.  The dtls subtree contains certificates used with DTLS

single quotes for 'dtls'.
"the DTLS"

Section 2.3

   Similarly, an interface that is a metered 3G link, and used for
   fallback connectivity needs much higher default time constants, e.g.

Comma after "connectivity".

   HMAC: Keyed-Hashing for Message Authentication [RFC2104], Using
   HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 [RFC4868], Datagram

The "with IPsec" part of RFC 4868's title seems to have been dropped.

         "This implementation supports two-out-of-three metric
          comp algorithm.";

"the two-out-of-three".
Also, do we really need to (silently) abbreviate "metric computation"
(multiple occurrences)?

         "This implementation supports Expected Transmission Count

"the Expected"

         "This implementation supports hmac-sha256 MAC algorithm.";

"the hmac-sha256"

         "This implementation supports x-509 certificate type.";

"the X.509"

         "This implementation supports raw-public-key certificate
          type.";

Missing article, per the theme, but I think it would also be more
conventional to spell the name as "RawPublicKey".

       base metric-comp-algorithms;
       if-feature "etx-supported";
       description
         "Expected Transmission Count.";

I'd put an "algorithm" in here somewhere

         "BLAKE2s algorithms supported. Specifically, BLAKE2-128 is
          supported.";

I'd just say "BLAKE2-128 algorithm supported."

         "Raw Public Key type.";

"certificate type"

         leaf router-id {
           type binary;

(If length constraint is applied earlier, it should apply here as well.)

             "Indicates whether statistics collection is enabled (true)
              or disabled (false) on all interfaces. When enabled,
              existing statistics values are not cleared and will be
              incremented as new packets are counted.";

I suggest "on transition to enabled".
(Also, thank you for clearly spelling out which behaviors true/false map
to!)

                A value of true indicates split horizon optimization
                is used.";
"the split"

               "List of references to the mac entries that apply
                to this interface. When an interface instance is
                created, all mac instances with default-apply 'true'

s/mac/MAC/ (twice)

               "Indicates whether the cached_info extension is included
                in ClientHello and ServerHello packets. The extension

s/packets/messages/.
Also, it's conventional to refer to TLS extension names enclosed by
double quotes, but I guess in the context of a YANG leaf description
that's not really feasible.

                dtls-cert-types. This list is used to populate the
                server_certificate_type extension in a Client Hello.

s/Client Hello/ClientHello/.

         list mac-key-set {
           key "name";

           description
             "A mac key set object. If this object is implemented, it
              provides access to parameters related to the MAC security
              mechanism.";

s/mac/MAC/

               "A string that uniquely identifies the mac object.";

s/mac/MAC key/

                If 'true', this instance is applied to new babel-
                interfaces instances at the time they are created,
                by including it in the mac-key-sets list under
                interfaces. If 'false', this instance is not applied

s/under interfaces/under the interface/

                to new interfaces instances when they are created.";

s/interfaces/interface/

                If 'true', this instance is applied to new interfaces
                instances at the time they are created, by including it
                in the dtls-certs list under interfaces. If 'false',

s/under interfaces/under the interface/

                this instance is not applied to new interfaces
                instances when they are created.";

s/interfaces/interface/




From nobody Thu May 20 12:16:07 2021
Return-Path: <mjethanandani@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B653A22BD; Thu, 20 May 2021 12:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTTPS_HTTP_MISMATCH=0.1, 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 P_WZthWJxwcj; Thu, 20 May 2021 12:15:59 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 5B6BB3A22BB; Thu, 20 May 2021 12:15:59 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id t21so9676923plo.2; Thu, 20 May 2021 12:15:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=y2EjV8UgJPHVhO95cngVFM0kSzFg8n0et51oE0dTygs=; b=jbOZlXhFFVtUQAfoU/xyL8uAjIZEl/1NWgbPCvUk+K0LGSlMkoSVEt+y/l4AGOIdP1 nieOHaB4d5X7Cq8BcpNyWWnVCzGOmnH45+5wMstfzt/OlfwFDUoFfh8vMbmaz9ON51To cLf70J8H425b2MSywmtUBCIzQ0iUxG3zKMb68fxMidFaKh1k2OAgueW6HGuxhO92tiia IwQihHDsoJBzS75W1JbMsanNOntnK9MDwkWU8uTlSNkJsHDuNU6G7sbsmzPZIBDzkmIr 7BuzoKCm9W/bQfUkfDohGkTIjQuJD/LFD50obhqDIcH09/MaFeJk8tjh28aQ8rw47oA3 QN1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=y2EjV8UgJPHVhO95cngVFM0kSzFg8n0et51oE0dTygs=; b=kB3sXlI60pUCSAbG4Zg/0D8PQNEUFuYMOTCSpRz96OLznRN00XLXxmaIHvRsh0jPMv VpV9IfeH+DLu6VWtgTmjbYoBKVrt3UFrK6ela0PXgrb8A7L4IRq3NboMxKNOOC2d/SOe sE6Mxu1ApLx7aWnYt/PqFsebfow7NMnWAUHo8VlGLDm5Pd5TN+c6BW88MAHLog+psZxz scqFfa3FwKKrjZ1MwDvM8CJLok43at+3bJwk0+2Yd80EUnW99WKdYvWIP9t6sYdD0YqQ FfA/Uhxy9dMFjqmK5qJQNSN4vfwbprLt+OZ7cBmxzH50HwtsQUmZP0OnMlrts2vONhXm HFNg==
X-Gm-Message-State: AOAM530pZS9gm3rOs5LlaTahG1VGYBDtO0eeLPj1AsN1XLVOjx/t7Cad uapu+u1zKrujjuv7y2o0okc=
X-Google-Smtp-Source: ABdhPJy9Hue5PWB9AOp4ypI0N001rXsz/UFvruQvDD8ZDkMN2UviYGc/hsFMlSaHifZ1HcYLge9jcg==
X-Received: by 2002:a17:90a:8c8b:: with SMTP id b11mr6365358pjo.236.1621538157121;  Thu, 20 May 2021 12:15:57 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:b9a7:c51d:2455:8f4f? ([2601:647:5600:5020:b9a7:c51d:2455:8f4f]) by smtp.gmail.com with ESMTPSA id s80sm2683663pfs.59.2021.05.20.12.15.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 May 2021 12:15:55 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <8310B1F3-BB5C-4882-99CE-21D6DA916D3A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B4883053-ED06-4E85-A3DA-FB9B61F08B14"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 20 May 2021 12:15:54 -0700
In-Reply-To: <CAM4esxT76NZKJ_6--ryJSnpjtRs7Hkhg4KCrA_h322P1j+YXrQ@mail.gmail.com>
Cc: "STARK, BARBARA H" <bs7652@att.com>, The IESG <iesg@ietf.org>, "draft-ietf-babel-yang-model@ietf.org" <draft-ietf-babel-yang-model@ietf.org>,  babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com> <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com> <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com> <DM6PR02MB692424BDA3D24B163D1E37F4C32C9@DM6PR02MB6924.namprd02.prod.outlook.com> <CAM4esxT76NZKJ_6--ryJSnpjtRs7Hkhg4KCrA_h322P1j+YXrQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Ecqid5V-XQjPZrWh6JwP32p6H68>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 19:16:05 -0000

--Apple-Mail=_B4883053-ED06-4E85-A3DA-FB9B61F08B14
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Martin,

Barbara and I did some wordsmithing offline and came up with the =
following description text for =E2=80=98received-metric=E2=80=99.

OLD:
             "The metric with which this route was advertised by the
              neighbor, or maximum value (infinity) to indicate the
              route was recently retracted and is temporarily
              unreachable. This metric will be 0 (zero) if the route
              was not received from a neighbor but was generated
              through other means. At least one of
              calculated-metric or received-metric MUST be non-NULL.";

NEW:
             "The metric with which this route was advertised by the
              neighbor, or maximum value (infinity) to indicate the
              route was recently retracted and is temporarily
              unreachable. This metric will be NULL (no value) if the
              route was not received from a neighbor but instead was
              injected through means external to the Babel routing
              protocol. At least one of calculated-metric or
              received-metric MUST be non-NULL.";

Does this address your COMMENT?

Thanks

> On May 18, 2021, at 2:39 PM, Martin Duke <martin.h.duke@gmail.com> =
wrote:
>=20
> Hi Barbara,
>=20
> On Tue, May 18, 2021 at 11:48 AM STARK, BARBARA H <bs7652@att.com =
<mailto:bs7652@att.com>> wrote:
> The received-metric and calculated-metric are read-only parameters. =
They come from the babel implementation and are never provided from the =
data model to the implementation. Their calculation and use (by the =
implementation) is governed fully by RFC 8966. For the Babel routing =
protocol implementers, NULL (a variable of zero-length) and zero (a =
value of zero) are separate and distinct values. Various computer =
languages allow for this distinction =E2=80=93 even when passing around =
integers. Data models (and relational databases like sql and such) often =
struggle with this distinction because they don=E2=80=99t allow =
zero-length integer fields.
>=20
>=20
> Thanks for clarifying -- that's a fine distinction to make, although =
the authors should agree that they're making it!=20
> =20
> =20
>=20
> If the route is originated by this router, advertised by this router, =
and never advertised by another router in the network, then the =
received-metric (per the implementation) will be NULL. If the router is =
going to advertise a route that it originates, it will have to generate =
a calculated-metric. It may calculate the calculated-metric for itself =
to be zero =E2=80=93 thus ensuring, if it subsequently receives an =
advertisement from another router for the same route, the =
received-metric supplied by the other router will never be less than the =
calculated-metric it has.
>=20
> =20
>=20
> Anyway, this is why =E2=80=9CThis metric will be NULL if the route was =
not received from a neighbor but was generated through other means." =
Note that this sentence is about the *route* being received from a =
neighbor (or the *route* being generated through other means). The =
received-metric is never =E2=80=9Cgenerated=E2=80=9D. It is populated by =
the neighbor-supplied metric for an advertised route. And when an entry =
in the route table is locally originated and there is no received value, =
then it needs to be properly noted that there is no value. An absence of =
received value is NULL, and not a value of zero.
>=20
>=20
> This makes sense, but it's not what the text says! See my original =
email.
> =20
> =20
>=20
> What happens when both values are non-zero, is a matter of local =
implementation policy, as described in RFC 8966 3.5.2 and some of RFC =
8966=E2=80=99s Appendices that provide examples for how metrics and =
costs can be computed and used. The data model has absolutely no say =
over what values are passed to it. But it is an error if it has no =
metric at all (received or calculated) for a route that is in the route =
table.
>=20
> Barbara
>=20
> =20
>=20
> From: Martin Duke <martin.h.duke@gmail.com =
<mailto:martin.h.duke@gmail.com>>=20
> Sent: Tuesday, May 18, 2021 1:10 PM
> To: Mahesh Jethanandani <mjethanandani@gmail.com =
<mailto:mjethanandani@gmail.com>>
> Cc: The IESG <iesg@ietf.org <mailto:iesg@ietf.org>>; =
draft-ietf-babel-yang-model@ietf.org =
<mailto:draft-ietf-babel-yang-model@ietf.org>; babel-chairs =
<babel-chairs@ietf.org <mailto:babel-chairs@ietf.org>>; Babel at IETF =
<babel@ietf.org <mailto:babel@ietf.org>>; Donald Eastlake =
<d3e3e3@gmail.com <mailto:d3e3e3@gmail.com>>
> Subject: Re: Martin Duke's No Objection on =
draft-ietf-babel-yang-model-10: (with COMMENT)
>=20
> =20
>=20
> That's fine. In the original text, you refer to zero and NULL as if =
they're separate quantities. As these are uints, I think s/NULL/zero =
would solve the problem.
>=20
> =20
>=20
> It would be helpful to clarify what happens when both values are =
nonzero.
>=20
> =20
>=20
> On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani =
<mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>> wrote:
>=20
> Hi Martin,
>=20
> =20
>=20
> You bring up a point that I have been struggling with.
>=20
>=20
>=20
>=20
> On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker =
<noreply@ietf.org <mailto:noreply@ietf.org>> wrote:
>=20
> =20
>=20
> Martin Duke has entered the following ballot position for
> draft-ietf-babel-yang-model-10: No Objection
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html =
<https://urldefense.com/v3/__https:/www.ietf.org/iesg/statement/discuss-cr=
iteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa49=
6wEIOefq9NP$>
> for more information about DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/ =
<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-ba=
bel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjX=
Sa496wEIOvbIEVE$>
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (2.3)
>=20
> leaf received-metric {
>           type uint16;
>           description
>             "The metric with which this route was advertised by the
>              neighbor, or maximum value (infinity) to indicate the
>              route was recently retracted and is temporarily
>              unreachable. This metric will be 0 (zero) if the route
>              was not received from a neighbor but was generated
>              through other means. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>=20
>         leaf calculated-metric {
>           type uint16;
>           description
>             "A calculated metric for this route. How the metric is
>              calculated is implementation-specific. Maximum value
>              (infinity) indicates the route was recently retracted
>              and is temporarily unreachable. At least one of
>              calculated-metric or received-metric MUST be non-NULL.";
>           reference
>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>         }
>=20
> I don't understand the relationship between these two. If the metric =
was
> calculated rather than received, why would the value be zero instead =
of NULL?
> Isn't a zero metric dangerous in a routing algorithm?
>=20
> =20
>=20
> How do you represent NULL? By definition, NULL means there is no =
value, that we are looking at an empty leaf. A =E2=80=98received-metric=E2=
=80=99 per my reading, cannot be empty. It is either received from a =
neighbor, or is a generated value, and therefore cannot be empty. Same =
is the case for =E2=80=98calculated-metric=E2=80=99. Combine this with =
the fact that the info model defines the leaf of type unsigned int 16, =
and thus the value of 0. Would it help to add something to this effect?
>=20
> =20
>=20
> "A value of 0 implies a NULL value, and SHOULD NOT be used in metric =
calculation".
>=20
> =20
>=20
> Alternatively, one could change the type to signed int 16, something =
the TR-181 model does. In that case the value has two meanings. If the =
value is less than 0, it means the value is NULL, but if the value is =
greater than 0, then it carries the actual metric value??
>=20
> =20
>=20
> In either case, an implementor cannot take the value of the metric as =
is and use it, without checking if it is 0 or -1.
>=20
>=20
>=20
>=20
>=20
> (4) "config true perspective"
>=20
> =20
>=20
> Dropped the phrase from the sentence.
>=20
> =20
>=20
> Thanks
>=20
> =20
>=20
> Mahesh Jethanandani
>=20
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
Mahesh Jethanandani
mjethanandani@gmail.com






--Apple-Mail=_B4883053-ED06-4E85-A3DA-FB9B61F08B14
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Martin,<div class=3D""><br class=3D""></div><div class=3D"">Barbara and =
I did some wordsmithing offline and came up with the following =
description text for =E2=80=98received-metric=E2=80=99.</div><div =
class=3D""><br class=3D""></div><div class=3D"">OLD:</div><div =
class=3D""><pre class=3D"newpage" style=3D"font-size: 13.3333px; =
margin-top: 0px; margin-bottom: 0px; break-before: page; =
font-variant-ligatures: normal; orphans: 2; widows: 2; =
text-decoration-thickness: initial;">             "The metric with which =
this route was advertised by the
              neighbor, or maximum value (infinity) to indicate the
              route was recently retracted and is temporarily
              unreachable. This metric will be 0 (zero) if the route
              was not received from a neighbor but was generated
              through other means. At least one of
              calculated-metric or received-metric MUST be =
non-NULL.";</pre><div class=3D""><br class=3D""></div><div =
class=3D"">NEW:</div><div class=3D""><div class=3D""><font face=3D"Menlo" =
size=3D"2" class=3D""><span style=3D"font-style: normal;" =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"The metric =
with which this route was advertised by the</span></font></div><div =
class=3D""><font face=3D"Menlo" size=3D"2" class=3D""><span =
style=3D"font-style: normal;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; neighbor, or maximum value (infinity) to indicate =
the</span></font></div><div class=3D""><font face=3D"Menlo" size=3D"2" =
class=3D""><span style=3D"font-style: normal;" class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; route was recently retracted and is =
temporarily</span></font></div><div class=3D""><font face=3D"Menlo" =
size=3D"2" class=3D""><span style=3D"font-style: normal;" =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; unreachable. =
This metric will be NULL (no value) if the</span></font></div><div =
class=3D""><font face=3D"Menlo" size=3D"2" class=3D""><span =
style=3D"font-style: normal;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; route was not received from a neighbor but instead =
was</span></font></div><div class=3D""><font face=3D"Menlo" size=3D"2" =
class=3D""><span style=3D"font-style: normal;" class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; injected through means external to =
the Babel routing</span></font></div><div class=3D""><font face=3D"Menlo" =
size=3D"2" class=3D""><span style=3D"font-style: normal;" =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; protocol. At =
least one of calculated-metric or</span></font></div><div class=3D""><font=
 face=3D"Menlo" size=3D"2" class=3D""><span style=3D"font-style: =
normal;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
received-metric MUST be non-NULL.";</span></font></div></div><div><br =
class=3D""></div><div>Does this address your COMMENT?</div><div><br =
class=3D""></div><div>Thanks</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On May 18, 2021, at 2:39 PM, =
Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.com" =
class=3D"">martin.h.duke@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><div =
dir=3D"ltr" class=3D"">Hi Barbara,<br class=3D""></div><br class=3D""><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May =
18, 2021 at 11:48 AM STARK, BARBARA H &lt;<a =
href=3D"mailto:bs7652@att.com" class=3D"">bs7652@att.com</a>&gt; =
wrote:<br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin: 0px 0px 0px 0.8ex; border-left-width: 1px; =
border-left-style: solid; border-left-color: rgb(204, 204, 204); =
padding-left: 1ex;"><div lang=3D"EN-US" style=3D"overflow-wrap: =
break-word;" class=3D""><div =
class=3D"gmail-m_6714943240863696188WordSection1"><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">The received-metric and =
calculated-metric are read-only parameters. They come from the babel =
implementation and are never provided from the data model to the =
implementation. Their calculation and use (by the implementation) is =
governed fully by RFC 8966. For the Babel routing protocol implementers, =
NULL (a variable of zero-length) and zero (a value of zero) are separate =
and distinct values. Various computer languages allow for this =
distinction =E2=80=93 even when passing around integers. Data models =
(and relational databases like<span =
class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"gmail-m_6714943240863696188SpellE">sql</span><span =
class=3D"Apple-converted-space">&nbsp;</span>and such) often struggle =
with this distinction because they don=E2=80=99t allow zero-length =
integer fields.</span></font></p></div></div></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks for clarifying -- =
that's a fine distinction to make, although the authors should agree =
that they're making it!<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""></div><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
lang=3D"EN-US" style=3D"overflow-wrap: break-word;" class=3D""><div =
class=3D"gmail-m_6714943240863696188WordSection1"><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u><u =
class=3D""></u></span></font></p><p class=3D"MsoNormal"><font size=3D"2" =
face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt;" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">If the route is originated by this =
router, advertised by this router, and never advertised by another =
router in the network, then the received-metric (per the implementation) =
will be NULL. If the router is going to advertise a route that it =
originates, it will have to generate a calculated-metric. It may =
calculate the calculated-metric for itself to be zero =E2=80=93 thus =
ensuring, if it subsequently receives an advertisement from another =
router for the same route, the received-metric supplied by the other =
router will never be less than the calculated-metric it has.<u =
class=3D""></u><u class=3D""></u></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p><p class=3D"MsoNormal"><font size=3D"2" =
face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt;" =
class=3D"">Anyway, this is why =E2=80=9C</span>This metric will be NULL =
if the route was not received from a neighbor but was generated through =
other means." Note that this sentence is about the *<b class=3D""><span =
style=3D"font-weight: bold;" class=3D"">route</span></b>* being received =
from a neighbor (or the *<b class=3D""><span style=3D"font-weight: =
bold;" class=3D"">route</span></b>* being generated through other =
means). The received-metric is never =E2=80=9Cgenerated=E2=80=9D. It is =
populated by the neighbor-supplied metric for an advertised route. And =
when an entry in the route table is locally originated and there is no =
received value, then it needs to be properly noted that there is no =
value. An absence of received value is NULL, and not a value of =
zero.</font></p></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">This makes sense, but it's not what the =
text says! See my original email.<br class=3D""></div><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
lang=3D"EN-US" style=3D"overflow-wrap: break-word;" class=3D""><div =
class=3D"gmail-m_6714943240863696188WordSection1"><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><u =
class=3D""></u><u class=3D""></u></font></p><p class=3D"MsoNormal"><font =
size=3D"2" face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt;" =
class=3D""><u class=3D""></u>&nbsp;<u class=3D""></u></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">What happens when both values are =
non-zero, is a matter of local implementation policy, as described in =
RFC 8966 3.5.2 and some of RFC 8966=E2=80=99s Appendices that provide =
examples for how metrics and costs can be computed and used. The data =
model has absolutely no say over what values are passed to it. But it is =
an error if it has no metric at all (received or calculated) for a route =
that is in the route table.<u class=3D""></u><u =
class=3D""></u></span></font></p><p class=3D"MsoNormal"><font size=3D"2" =
face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt;" =
class=3D"">Barbara</span></font><span class=3D""><u class=3D""></u><u =
class=3D""></u></span></p><p class=3D"MsoNormal"><font size=3D"2" =
face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt;" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></span></font></p><div =
style=3D"border-color: currentcolor currentcolor currentcolor blue; =
border-style: none none none solid; border-width: medium medium medium =
1.5pt; padding: 0in 0in 0in 4pt;" class=3D""><div class=3D""><div =
style=3D"border-color: rgb(225, 225, 225) currentcolor currentcolor; =
border-style: solid none none; border-width: 1pt medium medium; padding: =
3pt 0in 0in;" class=3D""><p class=3D"MsoNormal"><b class=3D""><font =
size=3D"2" face=3D"Calibri" class=3D""><span style=3D"font-size: 11pt; =
font-weight: bold;" class=3D"">From:</span></font></b><span =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>Martin =
Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.com" target=3D"_blank" =
class=3D"">martin.h.duke@gmail.com</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, May 18, 2021 1:10 =
PM<br class=3D""><b class=3D""><span style=3D"font-weight: bold;" =
class=3D"">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Mahesh Jethanandani &lt;<a =
href=3D"mailto:mjethanandani@gmail.com" target=3D"_blank" =
class=3D"">mjethanandani@gmail.com</a>&gt;<br class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Cc:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>The IESG &lt;<a =
href=3D"mailto:iesg@ietf.org" target=3D"_blank" =
class=3D"">iesg@ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-babel-yang-model@ietf.org" target=3D"_blank" =
class=3D"">draft-ietf-babel-yang-model@ietf.org</a>; babel-chairs &lt;<a =
href=3D"mailto:babel-chairs@ietf.org" target=3D"_blank" =
class=3D"">babel-chairs@ietf.org</a>&gt;; Babel at IETF &lt;<a =
href=3D"mailto:babel@ietf.org" target=3D"_blank" =
class=3D"">babel@ietf.org</a>&gt;; Donald Eastlake &lt;<a =
href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank" =
class=3D"">d3e3e3@gmail.com</a>&gt;<br class=3D""><b class=3D""><span =
style=3D"font-weight: bold;" class=3D"">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: Martin Duke's No =
Objection on draft-ietf-babel-yang-model-10: (with COMMENT)<u =
class=3D""></u><u class=3D""></u></span></p></div></div><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p><div class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">That's fine. In the original text, =
you refer to zero and NULL as if they're separate quantities. As these =
are uints, I think s/NULL/zero would solve the problem.<u =
class=3D""></u><u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><u =
class=3D""></u>&nbsp;<u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D"">It would be =
helpful to clarify what happens when both values are nonzero.<u =
class=3D""></u><u class=3D""></u></span></font></p></div></div><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p><div class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">On Tue, May 18, 2021 at 11:01 AM =
Mahesh Jethanandani &lt;<a href=3D"mailto:mjethanandani@gmail.com" =
target=3D"_blank" class=3D"">mjethanandani@gmail.com</a>&gt; wrote:<u =
class=3D""></u><u class=3D""></u></span></font></p></div><blockquote =
style=3D"border-color: currentcolor currentcolor currentcolor rgb(204, =
204, 204); border-style: none none none solid; border-width: medium =
medium medium 1pt; padding: 0in 0in 0in 6pt; margin-left: 4.8pt; =
margin-right: 0in;" class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">Hi Martin,<u class=3D""></u><u =
class=3D""></u></span></font></p><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">You bring up a point that I have =
been struggling with.<u class=3D""></u><u =
class=3D""></u></span></font></p><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><br class=3D""><u class=3D""></u><br=
 class=3D""><u class=3D""></u><u class=3D""></u><u =
class=3D""></u></span></font></p><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">On May 17, 2021, at 2:10 PM, =
Martin Duke via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
target=3D"_blank" class=3D"">noreply@ietf.org</a>&gt; wrote:<u =
class=3D""></u><u class=3D""></u></span></font></p></div><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p><div class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">Martin Duke has entered the =
following ballot position for<br =
class=3D"">draft-ietf-babel-yang-model-10: No Objection<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer =
to<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://urldefense.com/v3/__https:/www.ietf.org/iesg/statement/dis=
cuss-criteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdUL=
fjXSa496wEIOefq9NP$" target=3D"_blank" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-=
ietf-babel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYD=
mdULfjXSa496wEIOvbIEVE$" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">(2.3)<br class=3D""><br =
class=3D"">leaf received-metric {<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typ=
e uint16;<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;des=
cription<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;"The metric with which this route was advertised by the<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;neighbor, or maximum value (infinity) to indicate the<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;route was recently retracted and is temporarily<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;unreachable. This metric will be 0 (zero) if the route<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;was not received from a neighbor but was generated<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;through other means. At least one of<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;calculated-metric or received-metric MUST be =
non-NULL.";<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ref=
erence<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;"RFC ZZZZ: Babel Information Model, Section 3.6,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;RFC 8966: The Babel Routing Protocol, Section 2.1.";<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br =
class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf =
calculated-metric {<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typ=
e uint16;<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;des=
cription<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;"A calculated metric for this route. How the metric is<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;calculated is implementation-specific. Maximum value<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;(infinity) indicates the route was recently retracted<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;and is temporarily unreachable. At least one of<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;calculated-metric or received-metric MUST be =
non-NULL.";<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ref=
erence<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;"RFC ZZZZ: Babel Information Model, Section 3.6,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;RFC 8966: The Babel Routing Protocol, Section 2.1.";<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br =
class=3D""><br class=3D"">I don't understand the relationship between =
these two. If the metric was<br class=3D"">calculated rather than =
received, why would the value be zero instead of NULL?<br class=3D"">Isn't=
 a zero metric dangerous in a routing algorithm?<u class=3D""></u><u =
class=3D""></u></span></font></p></div></div></blockquote><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><u =
class=3D""></u>&nbsp;<u class=3D""></u></span></font></p></div><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">How do you represent NULL? By =
definition, NULL means there is no value, that we are looking at an =
empty leaf. A =E2=80=98received-metric=E2=80=99 per my reading, cannot =
be empty. It is either received from a neighbor, or is a generated =
value, and therefore cannot be empty. Same is the case for =
=E2=80=98calculated-metric=E2=80=99. Combine this with the fact that the =
info model defines the leaf of type unsigned int 16, and thus the value =
of 0. Would it help to add something to this effect?<u class=3D""></u><u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">"A value of 0 implies a NULL =
value, and SHOULD NOT be used in metric calculation".<u class=3D""></u><u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">Alternatively, one could change =
the type to signed int 16, something the TR-181 model does. In that case =
the value has two meanings. If the value is less than 0, it means the =
value is NULL, but if the value is greater than 0, then it carries the =
actual metric value??<u class=3D""></u><u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">In either case, an implementor =
cannot take the value of the metric as is and use it, without checking =
if it is 0 or -1.<u class=3D""></u><u =
class=3D""></u></span></font></p></div><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><br class=3D""><u class=3D""></u><br=
 class=3D""><u class=3D""></u><u class=3D""></u><u =
class=3D""></u></span></font></p><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><div class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D""><br class=3D"">(4) "config true =
perspective"<u class=3D""></u><u =
class=3D""></u></span></font></p></div></div></blockquote><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><u =
class=3D""></u>&nbsp;<u class=3D""></u></span></font></p></div><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">Dropped the phrase from the =
sentence.<u class=3D""></u><u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><u =
class=3D""></u>&nbsp;<u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D"">Thanks<u =
class=3D""></u><u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><u =
class=3D""></u>&nbsp;<u class=3D""></u></span></font></p></div><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><p =
class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">Mahesh Jethanandani<u =
class=3D""></u><u class=3D""></u></span></font></p></div><div =
class=3D""><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri" =
class=3D""><span style=3D"font-size: 11pt;" class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" target=3D"_blank" =
class=3D"">mjethanandani@gmail.com</a></span></font></p></div></div></div>=
</div></div></div></blockquote></div></div></div></div></blockquote></div>=
</div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_B4883053-ED06-4E85-A3DA-FB9B61F08B14--


From nobody Thu May 20 12:25:00 2021
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCF43A2301; Thu, 20 May 2021 12:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.997 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 1m1z5nzelFgg; Thu, 20 May 2021 12:24:51 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 8FC503A22FE; Thu, 20 May 2021 12:24:50 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id a11so17798469ioo.0; Thu, 20 May 2021 12:24:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GRAQqdJotdwKnkvSg42Uopq45vuszltt3FUslH+FBEc=; b=N5knLKG03/ZPcz1yjMAMDTqnZSdiYdkTgn9rzzJvsBlh9XzSILmIdfgiZboaaauOMm Sp11n4jpYHH8vOzcGpqj8OhOB4Y6ghu1j5H9RpqigSwjDFCKU3gAT56Y6iYRqzgGutVw fHfT2i2kSgBSH6sWGPGZvmGrl4VcSIVDApSQo0/xKN9SXMe+IvnIFsOeV/weNIocpAKf ti56pJSLSQ6K3k9swheD43Tja+JoOqmITVbnbuTBw7Lz6EojJQhCsvM9Ogxyd07mZehV NHuYcLNDQx5Eb2lPrc/sRQ6d3vsOq+7IwiriRQpRRXPd+rg9PMZbgLdInhz/+18GWfBB JOug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GRAQqdJotdwKnkvSg42Uopq45vuszltt3FUslH+FBEc=; b=d3849H6ShtozOQs6bx9LOUF+egW2ecZlKAwFJo5WChTqrtD7xBHAFxE9tZYF+t8KnD Fngp/4eALabtxiBsabgt6oFWHAl7flcnt0PlNLLORiWnGyJyIA4rNLVzW9FzZlhJoFjT /hEYidzfgOU+f1/gg+KhMXXQgYZWs0B+DMbfKY3moMaHJaNkimUonRSBS2TnOM02yYQ/ lWothKLiBr/n7KmfLTuGtK53t4dCi5gPa4Q0Ak81jkjW+kx4gVC1/FUisUoSjUHDUPRm evQj2OcRuDZJRN1LhZLnTVR0zxIduJcES/kRQDUZklOWjsBm6eQjY0/Y5CrKYM1utnyR KbJw==
X-Gm-Message-State: AOAM532lhhN9DJNku9rkofw7n0sQNAGUwROdmlkONYwl4CTL56+Y0ywF w/eDuWPG6YwptacMyBlDs2ie9ffNxnaMB6CgdKo=
X-Google-Smtp-Source: ABdhPJz2J+0ek6M4tnGhvZTxMZmAINlY1KW0cPzqlm0zKVHmL49v10jwKD1QmGkHYkLpEIE5YEdfzoyEgeWvhWEMekY=
X-Received: by 2002:a05:6602:446:: with SMTP id e6mr7501863iov.20.1621538688317;  Thu, 20 May 2021 12:24:48 -0700 (PDT)
MIME-Version: 1.0
References: <162128583297.9778.8228421381328520899@ietfa.amsl.com> <260E6E49-BB6D-4195-BD12-673A946FF346@gmail.com> <CAM4esxQLR-ULMf-RRT5_7y0U55zy+EqCqi7FhFhDtGitRz7LxA@mail.gmail.com> <DM6PR02MB692424BDA3D24B163D1E37F4C32C9@DM6PR02MB6924.namprd02.prod.outlook.com> <CAM4esxT76NZKJ_6--ryJSnpjtRs7Hkhg4KCrA_h322P1j+YXrQ@mail.gmail.com> <8310B1F3-BB5C-4882-99CE-21D6DA916D3A@gmail.com>
In-Reply-To: <8310B1F3-BB5C-4882-99CE-21D6DA916D3A@gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 20 May 2021 12:24:37 -0700
Message-ID: <CAM4esxR_cEBNmz2ODDg4deo_Hw8n5eijJMPeAEP+swXuMd=okQ@mail.gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: "STARK, BARBARA H" <bs7652@att.com>, The IESG <iesg@ietf.org>,  "draft-ietf-babel-yang-model@ietf.org" <draft-ietf-babel-yang-model@ietf.org>,  babel-chairs <babel-chairs@ietf.org>,  Babel at IETF <babel@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000081c0d905c2c7e56c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/4n1xJXnfZbVHqvYmg62ngrzbiJs>
Subject: Re: [babel] Martin Duke's No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 19:24:56 -0000

--00000000000081c0d905c2c7e56c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes, it does.

On Thu, May 20, 2021 at 12:15 PM Mahesh Jethanandani <
mjethanandani@gmail.com> wrote:

> Hi Martin,
>
> Barbara and I did some wordsmithing offline and came up with the followin=
g
> description text for =E2=80=98received-metric=E2=80=99.
>
> OLD:
>
>              "The metric with which this route was advertised by the
>               neighbor, or maximum value (infinity) to indicate the
>               route was recently retracted and is temporarily
>               unreachable. This metric will be 0 (zero) if the route
>               was not received from a neighbor but was generated
>               through other means. At least one of
>               calculated-metric or received-metric MUST be non-NULL.";
>
>
> NEW:
>              "The metric with which this route was advertised by the
>               neighbor, or maximum value (infinity) to indicate the
>               route was recently retracted and is temporarily
>               unreachable. This metric will be NULL (no value) if the
>               route was not received from a neighbor but instead was
>               injected through means external to the Babel routing
>               protocol. At least one of calculated-metric or
>               received-metric MUST be non-NULL.";
>
> Does this address your COMMENT?
>
> Thanks
>
> On May 18, 2021, at 2:39 PM, Martin Duke <martin.h.duke@gmail.com> wrote:
>
> Hi Barbara,
>
> On Tue, May 18, 2021 at 11:48 AM STARK, BARBARA H <bs7652@att.com> wrote:
>
>> The received-metric and calculated-metric are read-only parameters. They
>> come from the babel implementation and are never provided from the data
>> model to the implementation. Their calculation and use (by the
>> implementation) is governed fully by RFC 8966. For the Babel routing
>> protocol implementers, NULL (a variable of zero-length) and zero (a valu=
e
>> of zero) are separate and distinct values. Various computer languages al=
low
>> for this distinction =E2=80=93 even when passing around integers. Data m=
odels (and
>> relational databases like sql and such) often struggle with this
>> distinction because they don=E2=80=99t allow zero-length integer fields.
>>
>
> Thanks for clarifying -- that's a fine distinction to make, although the
> authors should agree that they're making it!
>
>
>>
>>
>> If the route is originated by this router, advertised by this router, an=
d
>> never advertised by another router in the network, then the received-met=
ric
>> (per the implementation) will be NULL. If the router is going to adverti=
se
>> a route that it originates, it will have to generate a calculated-metric=
.
>> It may calculate the calculated-metric for itself to be zero =E2=80=93 t=
hus
>> ensuring, if it subsequently receives an advertisement from another rout=
er
>> for the same route, the received-metric supplied by the other router wil=
l
>> never be less than the calculated-metric it has.
>>
>>
>>
>> Anyway, this is why =E2=80=9CThis metric will be NULL if the route was n=
ot
>> received from a neighbor but was generated through other means." Note th=
at
>> this sentence is about the **route** being received from a neighbor (or
>> the **route** being generated through other means). The received-metric
>> is never =E2=80=9Cgenerated=E2=80=9D. It is populated by the neighbor-su=
pplied metric for
>> an advertised route. And when an entry in the route table is locally
>> originated and there is no received value, then it needs to be properly
>> noted that there is no value. An absence of received value is NULL, and =
not
>> a value of zero.
>>
>
> This makes sense, but it's not what the text says! See my original email.
>
>
>>
>>
>> What happens when both values are non-zero, is a matter of local
>> implementation policy, as described in RFC 8966 3.5.2 and some of RFC
>> 8966=E2=80=99s Appendices that provide examples for how metrics and cost=
s can be
>> computed and used. The data model has absolutely no say over what values
>> are passed to it. But it is an error if it has no metric at all (receive=
d
>> or calculated) for a route that is in the route table.
>>
>> Barbara
>>
>>
>>
>> *From:* Martin Duke <martin.h.duke@gmail.com>
>> *Sent:* Tuesday, May 18, 2021 1:10 PM
>> *To:* Mahesh Jethanandani <mjethanandani@gmail.com>
>> *Cc:* The IESG <iesg@ietf.org>; draft-ietf-babel-yang-model@ietf.org;
>> babel-chairs <babel-chairs@ietf.org>; Babel at IETF <babel@ietf.org>;
>> Donald Eastlake <d3e3e3@gmail.com>
>> *Subject:* Re: Martin Duke's No Objection on
>> draft-ietf-babel-yang-model-10: (with COMMENT)
>>
>>
>>
>> That's fine. In the original text, you refer to zero and NULL as if
>> they're separate quantities. As these are uints, I think s/NULL/zero wou=
ld
>> solve the problem.
>>
>>
>>
>> It would be helpful to clarify what happens when both values are nonzero=
.
>>
>>
>>
>> On Tue, May 18, 2021 at 11:01 AM Mahesh Jethanandani <
>> mjethanandani@gmail.com> wrote:
>>
>> Hi Martin,
>>
>>
>>
>> You bring up a point that I have been struggling with.
>>
>>
>>
>> On May 17, 2021, at 2:10 PM, Martin Duke via Datatracker <
>> noreply@ietf.org> wrote:
>>
>>
>>
>> Martin Duke has entered the following ballot position for
>> draft-ietf-babel-yang-model-10: No Objection
>>
>> 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/iesg/statement/discuss-criteria.htm=
l
>> <https://urldefense.com/v3/__https:/www.ietf.org/iesg/statement/discuss-=
criteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa4=
96wEIOefq9NP$>
>> for more information about DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/
>> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-=
babel-yang-model/__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfj=
XSa496wEIOvbIEVE$>
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> (2.3)
>>
>> leaf received-metric {
>>           type uint16;
>>           description
>>             "The metric with which this route was advertised by the
>>              neighbor, or maximum value (infinity) to indicate the
>>              route was recently retracted and is temporarily
>>              unreachable. This metric will be 0 (zero) if the route
>>              was not received from a neighbor but was generated
>>              through other means. At least one of
>>              calculated-metric or received-metric MUST be non-NULL.";
>>           reference
>>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>>         }
>>
>>         leaf calculated-metric {
>>           type uint16;
>>           description
>>             "A calculated metric for this route. How the metric is
>>              calculated is implementation-specific. Maximum value
>>              (infinity) indicates the route was recently retracted
>>              and is temporarily unreachable. At least one of
>>              calculated-metric or received-metric MUST be non-NULL.";
>>           reference
>>             "RFC ZZZZ: Babel Information Model, Section 3.6,
>>              RFC 8966: The Babel Routing Protocol, Section 2.1.";
>>         }
>>
>> I don't understand the relationship between these two. If the metric was
>> calculated rather than received, why would the value be zero instead of
>> NULL?
>> Isn't a zero metric dangerous in a routing algorithm?
>>
>>
>>
>> How do you represent NULL? By definition, NULL means there is no value,
>> that we are looking at an empty leaf. A =E2=80=98received-metric=E2=80=
=99 per my reading,
>> cannot be empty. It is either received from a neighbor, or is a generate=
d
>> value, and therefore cannot be empty. Same is the case for
>> =E2=80=98calculated-metric=E2=80=99. Combine this with the fact that the=
 info model defines
>> the leaf of type unsigned int 16, and thus the value of 0. Would it help=
 to
>> add something to this effect?
>>
>>
>>
>> "A value of 0 implies a NULL value, and SHOULD NOT be used in metric
>> calculation".
>>
>>
>>
>> Alternatively, one could change the type to signed int 16, something the
>> TR-181 model does. In that case the value has two meanings. If the value=
 is
>> less than 0, it means the value is NULL, but if the value is greater tha=
n
>> 0, then it carries the actual metric value??
>>
>>
>>
>> In either case, an implementor cannot take the value of the metric as is
>> and use it, without checking if it is 0 or -1.
>>
>>
>>
>>
>> (4) "config true perspective"
>>
>>
>>
>> Dropped the phrase from the sentence.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Mahesh Jethanandani
>>
>> mjethanandani@gmail.com
>>
>>
> Mahesh Jethanandani
> mjethanandani@gmail.com
>
>
>
>
>
>

--00000000000081c0d905c2c7e56c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, it does. <br></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Thu, May 20, 2021 at 12:15 PM Mahesh =
Jethanandani &lt;<a href=3D"mailto:mjethanandani@gmail.com">mjethanandani@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div style=3D"overflow-wrap: break-word;">Hi Martin,<div><br></div>=
<div>Barbara and I did some wordsmithing offline and came up with the follo=
wing description text for =E2=80=98received-metric=E2=80=99.</div><div><br>=
</div><div>OLD:</div><div><pre style=3D"font-size:13.3333px;margin-top:0px;=
margin-bottom:0px;break-before:page;font-variant-ligatures:normal">        =
     &quot;The metric with which this route was advertised by the
              neighbor, or maximum value (infinity) to indicate the
              route was recently retracted and is temporarily
              unreachable. This metric will be 0 (zero) if the route
              was not received from a neighbor but was generated
              through other means. At least one of
              calculated-metric or received-metric MUST be non-NULL.&quot;;=
</pre><div><br></div><div>NEW:</div><div><div><font size=3D"2" face=3D"Menl=
o"><span style=3D"font-style:normal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&quot;The metric with which this route was advertised by the</spa=
n></font></div><div><font size=3D"2" face=3D"Menlo"><span style=3D"font-sty=
le:normal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 neighbor, or ma=
ximum value (infinity) to indicate the</span></font></div><div><font size=
=3D"2" face=3D"Menlo"><span style=3D"font-style:normal">=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 route was recently retracted and is tempora=
rily</span></font></div><div><font size=3D"2" face=3D"Menlo"><span style=3D=
"font-style:normal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 unreac=
hable. This metric will be NULL (no value) if the</span></font></div><div><=
font size=3D"2" face=3D"Menlo"><span style=3D"font-style:normal">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 route was not received from a neighb=
or but instead was</span></font></div><div><font size=3D"2" face=3D"Menlo">=
<span style=3D"font-style:normal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 injected through means external to the Babel routing</span></font><=
/div><div><font size=3D"2" face=3D"Menlo"><span style=3D"font-style:normal"=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protocol. At least one of=
 calculated-metric or</span></font></div><div><font size=3D"2" face=3D"Menl=
o"><span style=3D"font-style:normal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 received-metric MUST be non-NULL.&quot;;</span></font></div></di=
v><div><br></div><div>Does this address your COMMENT?</div><div><br></div><=
div>Thanks</div><div><br><blockquote type=3D"cite"><div>On May 18, 2021, at=
 2:39 PM, Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.com" target=
=3D"_blank">martin.h.duke@gmail.com</a>&gt; wrote:</div><br><div><div dir=
=3D"ltr" style=3D"font-family:Helvetica;font-size:12px;font-style:normal;fo=
nt-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px;text-decoration:none"><div dir=3D"ltr">Hi Barbara,<br></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 18, 20=
21 at 11:48 AM STARK, BARBARA H &lt;<a href=3D"mailto:bs7652@att.com" targe=
t=3D"_blank">bs7652@att.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNormal">=
<font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">The receiv=
ed-metric and calculated-metric are read-only parameters. They come from th=
e babel implementation and are never provided from the data model to the im=
plementation. Their calculation and use (by the implementation) is governed=
 fully by RFC 8966. For the Babel routing protocol implementers, NULL (a va=
riable of zero-length) and zero (a value of zero) are separate and distinct=
 values. Various computer languages allow for this distinction =E2=80=93 ev=
en when passing around integers. Data models (and relational databases like=
<span>=C2=A0</span><span>sql</span><span>=C2=A0</span>and such) often strug=
gle with this distinction because they don=E2=80=99t allow zero-length inte=
ger fields.</span></font></p></div></div></blockquote><div><br></div><div>T=
hanks for clarifying -- that&#39;s a fine distinction to make, although the=
 authors should agree that they&#39;re making it!<span>=C2=A0</span><br></d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
lang=3D"EN-US"><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri=
"><span style=3D"font-size:11pt"><u></u><u></u></span></font></p><p class=
=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:1=
1pt"><u></u>=C2=A0<u></u></span></font></p><p class=3D"MsoNormal"><font siz=
e=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">If the route is ori=
ginated by this router, advertised by this router, and never advertised by =
another router in the network, then the received-metric (per the implementa=
tion) will be NULL. If the router is going to advertise a route that it ori=
ginates, it will have to generate a calculated-metric. It may calculate the=
 calculated-metric for itself to be zero =E2=80=93 thus ensuring, if it sub=
sequently receives an advertisement from another router for the same route,=
 the received-metric supplied by the other router will never be less than t=
he calculated-metric it has.<u></u><u></u></span></font></p><p class=3D"Mso=
Normal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt"><u=
></u>=C2=A0<u></u></span></font></p><p class=3D"MsoNormal"><font size=3D"2"=
 face=3D"Calibri"><span style=3D"font-size:11pt">Anyway, this is why =E2=80=
=9C</span>This metric will be NULL if the route was not received from a nei=
ghbor but was generated through other means.&quot; Note that this sentence =
is about the *<b><span style=3D"font-weight:bold">route</span></b>* being r=
eceived from a neighbor (or the *<b><span style=3D"font-weight:bold">route<=
/span></b>* being generated through other means). The received-metric is ne=
ver =E2=80=9Cgenerated=E2=80=9D. It is populated by the neighbor-supplied m=
etric for an advertised route. And when an entry in the route table is loca=
lly originated and there is no received value, then it needs to be properly=
 noted that there is no value. An absence of received value is NULL, and no=
t a value of zero.</font></p></div></div></blockquote><div><br></div><div>T=
his makes sense, but it&#39;s not what the text says! See my original email=
.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><font size=3D"2" face=3D=
"Calibri"><u></u><u></u></font></p><p class=3D"MsoNormal"><font size=3D"2" =
face=3D"Calibri"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span>=
</font></p><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span s=
tyle=3D"font-size:11pt">What happens when both values are non-zero, is a ma=
tter of local implementation policy, as described in RFC 8966 3.5.2 and som=
e of RFC 8966=E2=80=99s Appendices that provide examples for how metrics an=
d costs can be computed and used. The data model has absolutely no say over=
 what values are passed to it. But it is an error if it has no metric at al=
l (received or calculated) for a route that is in the route table.<u></u><u=
></u></span></font></p><p class=3D"MsoNormal"><font size=3D"2" face=3D"Cali=
bri"><span style=3D"font-size:11pt">Barbara</span></font><span><u></u><u></=
u></span></p><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span=
 style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p><div style=
=3D"border-color:currentcolor currentcolor currentcolor blue;border-style:n=
one none none solid;border-width:medium medium medium 1.5pt;padding:0in 0in=
 0in 4pt"><div><div style=3D"border-color:rgb(225,225,225) currentcolor cur=
rentcolor;border-style:solid none none;border-width:1pt medium medium;paddi=
ng:3pt 0in 0in"><p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Calibri"=
><span style=3D"font-size:11pt;font-weight:bold">From:</span></font></b><sp=
an><span>=C2=A0</span>Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmail=
.com" target=3D"_blank">martin.h.duke@gmail.com</a>&gt;<span>=C2=A0</span><=
br><b><span style=3D"font-weight:bold">Sent:</span></b><span>=C2=A0</span>T=
uesday, May 18, 2021 1:10 PM<br><b><span style=3D"font-weight:bold">To:</sp=
an></b><span>=C2=A0</span>Mahesh Jethanandani &lt;<a href=3D"mailto:mjethan=
andani@gmail.com" target=3D"_blank">mjethanandani@gmail.com</a>&gt;<br><b><=
span style=3D"font-weight:bold">Cc:</span></b><span>=C2=A0</span>The IESG &=
lt;<a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a>&gt;=
;<span>=C2=A0</span><a href=3D"mailto:draft-ietf-babel-yang-model@ietf.org"=
 target=3D"_blank">draft-ietf-babel-yang-model@ietf.org</a>; babel-chairs &=
lt;<a href=3D"mailto:babel-chairs@ietf.org" target=3D"_blank">babel-chairs@=
ietf.org</a>&gt;; Babel at IETF &lt;<a href=3D"mailto:babel@ietf.org" targe=
t=3D"_blank">babel@ietf.org</a>&gt;; Donald Eastlake &lt;<a href=3D"mailto:=
d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>&gt;<br><b><span st=
yle=3D"font-weight:bold">Subject:</span></b><span>=C2=A0</span>Re: Martin D=
uke&#39;s No Objection on draft-ietf-babel-yang-model-10: (with COMMENT)<u>=
</u><u></u></span></p></div></div><p class=3D"MsoNormal"><font size=3D"2" f=
ace=3D"Calibri"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span><=
/font></p><div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri=
"><span style=3D"font-size:11pt">That&#39;s fine. In the original text, you=
 refer to zero and NULL as if they&#39;re separate quantities. As these are=
 uints, I think s/NULL/zero would solve the problem.<u></u><u></u></span></=
font></p></div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri=
"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></di=
v><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=
=3D"font-size:11pt">It would be helpful to clarify what happens when both v=
alues are nonzero.<u></u><u></u></span></font></p></div></div><p class=3D"M=
soNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">=
<u></u>=C2=A0<u></u></span></font></p><div><div><p class=3D"MsoNormal"><fon=
t size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">On Tue, May 18=
, 2021 at 11:01 AM Mahesh Jethanandani &lt;<a href=3D"mailto:mjethanandani@=
gmail.com" target=3D"_blank">mjethanandani@gmail.com</a>&gt; wrote:<u></u><=
u></u></span></font></p></div><blockquote style=3D"border-color:currentcolo=
r currentcolor currentcolor rgb(204,204,204);border-style:none none none so=
lid;border-width:medium medium medium 1pt;padding:0in 0in 0in 6pt;margin-le=
ft:4.8pt;margin-right:0in"><div><p class=3D"MsoNormal"><font size=3D"2" fac=
e=3D"Calibri"><span style=3D"font-size:11pt">Hi Martin,<u></u><u></u></span=
></font></p><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><=
span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></div><=
div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D=
"font-size:11pt">You bring up a point that I have been struggling with.<u><=
/u><u></u></span></font></p><div><p class=3D"MsoNormal"><font size=3D"2" fa=
ce=3D"Calibri"><span style=3D"font-size:11pt"><br><u></u><br><u></u><u></u>=
<u></u></span></font></p><blockquote style=3D"margin-top:5pt;margin-bottom:=
5pt"><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span st=
yle=3D"font-size:11pt">On May 17, 2021, at 2:10 PM, Martin Duke via Datatra=
cker &lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf=
.org</a>&gt; wrote:<u></u><u></u></span></font></p></div><p class=3D"MsoNor=
mal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt"><u></=
u>=C2=A0<u></u></span></font></p><div><div><p class=3D"MsoNormal"><font siz=
e=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">Martin Duke has ent=
ered the following ballot position for<br>draft-ietf-babel-yang-model-10: N=
o Objection<br><br>When responding, please keep the subject line intact and=
 reply to all<br>email addresses included in the To and CC lines. (Feel fre=
e to cut this<br>introductory paragraph, however.)<br><br><br>Please refer =
to<span>=C2=A0</span><a href=3D"https://urldefense.com/v3/__https:/www.ietf=
.org/iesg/statement/discuss-criteria.html__;!!BhdT!1VEP6dtIBxS8iSbw9v3eXWj6=
dKDVxmAJwtD6CK8WYDmdULfjXSa496wEIOefq9NP$" target=3D"_blank">https://www.ie=
tf.org/iesg/statement/discuss-criteria.html</a><br>for more information abo=
ut DISCUSS and COMMENT positions.<br><br><br>The document, along with other=
 ballot positions, can be found here:<br><a href=3D"https://urldefense.com/=
v3/__https:/datatracker.ietf.org/doc/draft-ietf-babel-yang-model/__;!!BhdT!=
1VEP6dtIBxS8iSbw9v3eXWj6dKDVxmAJwtD6CK8WYDmdULfjXSa496wEIOvbIEVE$" target=
=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/</=
a><br><br><br><br>---------------------------------------------------------=
-------------<br>COMMENT:<br>----------------------------------------------=
------------------------<br><br>(2.3)<br><br>leaf received-metric {<br>=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0type uint16;<br>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0description<br>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&qu=
ot;The metric with which this route was advertised by the<br>=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0neighbor,=
 or maximum value (infinity) to indicate the<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0route was recently retra=
cted and is temporarily<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0unreachable. This metric will be 0 (zero) if =
the route<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0was not received from a neighbor but was generated<br>=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
through other means. At least one of<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0calculated-metric or received-=
metric MUST be non-NULL.&quot;;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0reference<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;RFC ZZZZ: Babel Information Model, S=
ection 3.6,<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0RFC 8966: The Babel Routing Protocol, Section 2.1.&quot;;=
<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0}<br><br>=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0leaf calculated-metric {<br>=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0type uint16;<br>=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0description<br>=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;A c=
alculated metric for this route. How the metric is<br>=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0calculated is impl=
ementation-specific. Maximum value<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0(infinity) indicates the route wa=
s recently retracted<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0and is temporarily unreachable. At least one of<=
br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0calculated-metric or received-metric MUST be non-NULL.&quot;;<br>=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reference<br>=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&quot;=
RFC ZZZZ: Babel Information Model, Section 3.6,<br>=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0RFC 8966: The Babel R=
outing Protocol, Section 2.1.&quot;;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0}<br><br>I don&#39;t understand the relationship between the=
se two. If the metric was<br>calculated rather than received, why would the=
 value be zero instead of NULL?<br>Isn&#39;t a zero metric dangerous in a r=
outing algorithm?<u></u><u></u></span></font></p></div></div></blockquote><=
div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D=
"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></div><p class=3D"Ms=
oNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">H=
ow do you represent NULL? By definition, NULL means there is no value, that=
 we are looking at an empty leaf. A =E2=80=98received-metric=E2=80=99 per m=
y reading, cannot be empty. It is either received from a neighbor, or is a =
generated value, and therefore cannot be empty. Same is the case for =E2=80=
=98calculated-metric=E2=80=99. Combine this with the fact that the info mod=
el defines the leaf of type unsigned int 16, and thus the value of 0. Would=
 it help to add something to this effect?<u></u><u></u></span></font></p></=
div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span sty=
le=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></div><div><p c=
lass=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-si=
ze:11pt">&quot;A value of 0 implies a NULL value, and SHOULD NOT be used in=
 metric calculation&quot;.<u></u><u></u></span></font></p></div><div><p cla=
ss=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size=
:11pt"><u></u>=C2=A0<u></u></span></font></p></div><div><p class=3D"MsoNorm=
al"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt">Altern=
atively, one could change the type to signed int 16, something the TR-181 m=
odel does. In that case the value has two meanings. If the value is less th=
an 0, it means the value is NULL, but if the value is greater than 0, then =
it carries the actual metric value??<u></u><u></u></span></font></p></div><=
div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D=
"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></div><div><p class=
=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size:1=
1pt">In either case, an implementor cannot take the value of the metric as =
is and use it, without checking if it is 0 or -1.<u></u><u></u></span></fon=
t></p></div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><=
span style=3D"font-size:11pt"><br><u></u><br><u></u><u></u><u></u></span></=
font></p><blockquote style=3D"margin-top:5pt;margin-bottom:5pt"><div><div><=
p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"font=
-size:11pt"><br>(4) &quot;config true perspective&quot;<u></u><u></u></span=
></font></p></div></div></blockquote><div><p class=3D"MsoNormal"><font size=
=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u>=
</span></font></p></div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Cal=
ibri"><span style=3D"font-size:11pt">Dropped the phrase from the sentence.<=
u></u><u></u></span></font></p></div><div><p class=3D"MsoNormal"><font size=
=3D"2" face=3D"Calibri"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u>=
</span></font></p></div><div><p class=3D"MsoNormal"><font size=3D"2" face=
=3D"Calibri"><span style=3D"font-size:11pt">Thanks<u></u><u></u></span></fo=
nt></p></div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri">=
<span style=3D"font-size:11pt"><u></u>=C2=A0<u></u></span></font></p></div>=
<div><div><div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri=
"><span style=3D"font-size:11pt">Mahesh Jethanandani<u></u><u></u></span></=
font></p></div><div><p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri=
"><span style=3D"font-size:11pt"><a href=3D"mailto:mjethanandani@gmail.com"=
 target=3D"_blank">mjethanandani@gmail.com</a></span></font></p></div></div=
></div></div></div></div></blockquote></div></div></div></div></blockquote>=
</div></div></div></blockquote></div><br><div>
<div dir=3D"auto" style=3D"color:rgb(0,0,0);letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;text-decoration:none"><div style=3D"color:rgb(0,0,0);letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px"><div>Mahesh Jethanandani</div><div><a href=3D"mailto:mj=
ethanandani@gmail.com" target=3D"_blank">mjethanandani@gmail.com</a></div><=
div><br></div></div><br></div><br><br>
</div>
<br></div></div></blockquote></div>

--00000000000081c0d905c2c7e56c--


From nobody Fri May 21 01:10:39 2021
Return-Path: <daedulus@btconnect.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2FF43A1EC6; Fri, 21 May 2021 01:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 p4TKl62C7p29; Fri, 21 May 2021 01:10:32 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10128.outbound.protection.outlook.com [40.107.1.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83D43A1ECA; Fri, 21 May 2021 01:10:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cOVOFZIVEIQTscx+1PauN0k8bram5ekbP65hx3ooCw0o0ktpHjJUnJAo5vSOu0xK9ThDpTPCgM6K+TwQPsiqaMUYxBgoIZP8tbHyDVrD7fO1udcGYuRn/lq+QZ91ENUFV35gCN0TPWJz5EMWFmGEEXn1Au3Ah0p9fLoD8cRpckrZMp14FJraGs3kmYwcU5mfsSNylUIUT+saWy7vfGQ9nbpvd0In8vu0mtWsOOe7CSAmtUEArlI8sNt0U+ouDBnMGq0uvNmzgoPM+A0QJSUal8buDUzFsqRPgLV9Gu/C0QNYLQb0vWWQ9FD374GMP47ctcVAXTHse6D4a3gvR6hOzA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EGE1IcWvvS7Y7w8Lg/RFgfTVs52eHZhok6P3kJB4rsY=; b=FHJZi+SHqe3FJLsnk9/lhSpFZ4MZGtR2BM6OamI41OULNO/kx2+OeN3kAX3LVnCkyj4AWAQz4GsGqI70VjH7q2polJUmFV0pTAyXVGev8GbUqUWWaH/VHP7HKVBGqu4gWzIL2Olal6ddXv0hYGRwKBJCacN8B1JvWBQebYEk+NgQ6TJhS0WCU+BGvrmytYJ+cQWau9JAxh6ff0TcZWCESihYQeyHxtDP0aRL9JCta0dYMuK4j+9RqHPr6fHRpWGH4Tmvb4iznZrxO2uDQ0BVnT34vG4HR32ZMH2WMIxHka1JEKGoOpqAKL+cE9CM+cmJ/dLJUvsJucndUVWZYHJqBw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EGE1IcWvvS7Y7w8Lg/RFgfTVs52eHZhok6P3kJB4rsY=; b=gT48l9E3pLjKrTeFNfyPVSfnrp9N02478HGG4i2/QGjaVGVqxjgep0YL3RM3iAVKwdW7j2kA+e/spsuhAijNi+KUCWUWimvfLECnsS54se4X0RfYYhs1HxtX3/XuAozgWSvToFhChSw4LkoYo5+n9zUGenO6l1RNFwI1AJx7kOU=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB6861.eurprd07.prod.outlook.com (2603:10a6:800:19b::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4173.12; Fri, 21 May 2021 08:10:28 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4173.012; Fri, 21 May 2021 08:10:28 +0000
To: Mahesh Jethanandani <mjethanandani@gmail.com>
References: <161788580040.14525.8607775335520195175@ietfa.amsl.com> <607406F2.70500@btconnect.com> <BAD13FB1-2787-4DFF-ACD5-BB259FA0D43C@gmail.com> <609E4ED3.5010101@btconnect.com> <A42366E1-6C05-4E17-A371-66D6904B5BBF@gmail.com> <609EA6A3.1040303@btconnect.com> <185C6A7C-D5D8-4FAB-BCBB-62525CBCBDDC@gmail.com> <609FAB33.4000201@btconnect.com> <411086E6-9BE0-4523-AD75-49C2E7F2D3D0@gmail.com>
Cc: last-call@ietf.org, babel-chairs <babel-chairs@ietf.org>, draft-ietf-babel-yang-model@ietf.org, babel@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <60A76AF1.7050604@btconnect.com>
Date: Fri, 21 May 2021 09:10:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <411086E6-9BE0-4523-AD75-49C2E7F2D3D0@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.143.250.49]
X-ClientProxiedBy: LO4P123CA0036.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:151::23) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.143.250.49) by LO4P123CA0036.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:151::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4150.23 via Frontend Transport; Fri, 21 May 2021 08:10:27 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5095a2b5-c3f9-4da4-936c-08d91c2fe4cc
X-MS-TrafficTypeDiagnostic: VI1PR0701MB6861:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB686114F7D66ABF2AA348B98DC6299@VI1PR0701MB6861.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: oL3JD5YfNL65Cmd9vaUn0imKVYvPWIUUwWnUtXvFEXILWjfbfjl9V34P9uZWzwrWktyeB/TLzj7oeJtH1nesjr8dH/rTO4TW4WEWGyX9hrdErZ9UsVBxnnTbVV7UHHt0ZpCjfq/LNhwVOXcCjMnKExIWedbHzWXM27AWKCSU336aQjRw/wsNvt8OE/BRurtZNUBAUp5D6k63FVyA7aOo/KazNS1DW8HsyIVNeK6U3DLBQil4PyFBiidMzn6spyJ18jFqA/y/nBx5gzkIyYQeF4be1tQ/baWOQstyPfS2IHru6LNik/am69kCQfgZxMa9XqgMSCgtU69BekH5lIgwueof5vHZyvh67MIp2vH3chGZwxiV6ndtOl/90njINiZPE7joVY9vqQOXy6kr2l4v3MN6BdjqmCZIj32OPgN9WP4TNoxM3NSrBxf2TOEB2SqGTHtCtwUsYIonQnMzBPjO4HogfLFKK8isoSz7S8FBpQsoiX3btPbNkj89KQXpLj/QaRVjiGZtSa2MONzaZHNFevfErquADmoVAmEa9VwdxgB9KWTKtHZzYNgDzujlzW3jg1DXPZCXNxCFpW6Mehk3jipq6x8Nn4bD39auNtwmbOHa+3EDhUYgvJLl2M6Z8FI680B+6lhn+dn20W6G6twiQA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(376002)(346002)(136003)(39860400002)(366004)(33656002)(38100700002)(66946007)(38350700002)(66556008)(16576012)(316002)(66476007)(52116002)(186003)(4326008)(2616005)(956004)(6916009)(6486002)(16526019)(87266011)(478600001)(2906002)(86362001)(36756003)(8936002)(8676002)(53546011)(5660300002)(26005); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?Windows-1252?Q?Mdr37VY1GIRNtgv8DXOUSkZALzja/Wb/YJz98mQbtfJOXYBOvdEbc2kO?= =?Windows-1252?Q?ha4foTywvcEozxDkDKJLIkZFr7ugVnOwD8gV9dOKrI2ufCZJ0E1hriPS?= =?Windows-1252?Q?4feuvvDaYco0GrP3gEJtpMySKdrB9mrG/ZXVAdqsYcEbxuIzF1WSbL3T?= =?Windows-1252?Q?W1Mm2c9FWE54oQlRTrWKwDg5u018ISf5QBd3J7ybDc89yfS9+pk0THGk?= =?Windows-1252?Q?x/diKGr+BdvB6AggcCc+/Wez/psnzy/UmyXrz+ImHXRQxRjbT3IN6ZVY?= =?Windows-1252?Q?pDKLtqRS2ikq61BrY3e9juJjA8L3ZyhCiYArwQXc3I4oO8EvtyjQUObZ?= =?Windows-1252?Q?K1kKoiV+MmA+UqgNW4eAuddKTK/miRI02N87bNVyGDIToWKMYeMK3YUr?= =?Windows-1252?Q?nR2y7JxL17XAMaWTRrkguxIUPuyyYKfn+12y9eVTodFm5s3T7TgIXuPt?= =?Windows-1252?Q?EEC/l5Gm9XOLS5rls2kxdGy4Qc0j8bbJBo241W0gbi9aisuo+D8eKu0P?= =?Windows-1252?Q?zX4nq2zro8Cx46Lx8ZCgYJkqqjL0bYA+H3dLX6ZxpbYGiARH8G1wN7tf?= =?Windows-1252?Q?siWXw0hxnF+EIgZ/+73u765GW9ea+WK2ijDw+uOjbcA65Bti0A+Ctjlr?= =?Windows-1252?Q?L5hrFXMJEdAB/0EebYhFLCIiLrLcGDSyuzxg1qBztwTzsBb5V/Wem2Wn?= =?Windows-1252?Q?c0XQODUolYPcj3L4jB/HgLr6Xbvn0jhrOIcO1FmF1W1aOHgeoo43FJlr?= =?Windows-1252?Q?ub+7Mt+AdmieTqOcIvovk/Ofw1TYzS0n/AOAvyF9poNy+5u9Ato/hNF+?= =?Windows-1252?Q?wVjNIJAcRxFywJzRZYYsgbF9aU+QJmVk9+gPh3LO+do5mNWibUImIGzz?= =?Windows-1252?Q?wiFItV7BcF6KQ4V4AwJ6SYaLz/62+u2g24Jw5yoh7N6Wjf2XDXxdPy/2?= =?Windows-1252?Q?UNzwEC5aYBmhUh+o57YMBsEmNdksd0N2ru1AEHrgHvNn6DRv+5jEKa8k?= =?Windows-1252?Q?nwa5CJCPwT2H2UhP9RfbmWk1zM3OiL69iDIS1gsW2PZKHISpPvx5aAsp?= =?Windows-1252?Q?X6yel2l4GNQD5uCFr7cjb1ND+jj8576SZaA9fPnq11Mz3XI3f8Kf9ETd?= =?Windows-1252?Q?En9avSiLd3BhBBku9IcuFAk545ZMYx8aT4u2YZjawyKqjWoYAnN6Sk2g?= =?Windows-1252?Q?3lJ65VyNAaZmUQGjvapKTUmObzdkygBw8/trjUSX9ZlsFbCX+hZVibX0?= =?Windows-1252?Q?Jc+H5VZbVwwheVUBcKSzCWAyOXKI4NSn29JuXS7pNtKBFJp3MPLexUDv?= =?Windows-1252?Q?GrZH6YspxU+jEWBVYGi0LfPoyfeYqkx+PW3t/Iro4qBl4rO4hvrTAcSV?= =?Windows-1252?Q?258g8noM2BZEWdSxSoUoAPuKa+8Xo/aslC2ibBmgEiQRfXt5dtvi1MdQ?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5095a2b5-c3f9-4da4-936c-08d91c2fe4cc
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 May 2021 08:10:27.9150 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: FQI5AsQdE90q8RHl46Y4YDe6Tb0T4AeFlSrnimJ9xSSAIaMHSGlZVWDBEIZ1ynZb+gFn0YzruimRgo3ZytF6Bg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB6861
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/ytQIXjN15VU1ekXVOGGrFxe-Oso>
Subject: Re: [babel] Last Call: <draft-ietf-babel-yang-model-09.txt> (YANG Data Model for Babel) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 May 2021 08:10:37 -0000

On 17/05/2021 05:27, Mahesh Jethanandani wrote:
> Hi Tom,
>
>> On May 15, 2021, at 4:06 AM, tom petch <daedulus@btconnect.com> wrote:
>>
>> On 14/05/2021 17:59, Mahesh Jethanandani wrote:
>>> Hi Tom,
>>>
>>> Are you suggesting that there should be no references to RFC numbers in the description statement? Note, the reference statement that follows the description statement has the complete reference to the RFC which is being cited in the description statement.
>>
>> I am saying that [RFC ZZZZ] and such like are usually xML and not plain text and that a YANG module is required to be plain text as when it is extracted from the RFC and floats off on is own independent of the rest of the RFC.  The 'canonical form' of a YANG module is plain text!
>
> Where in RFC 7950 or RFC 8407 does it say that?

It ia implicit in RFC8407 as a careful reading may show.

Tom Petch

>> Tom Petch
>>
>>> Cheers.
>>>
>>>> On May 14, 2021, at 9:34 AM, tom petch <daedulus@btconnect.com> wrote:
>>>>
>>>> On 14/05/2021 17:17, Mahesh Jethanandani wrote:
>>>>> Hi Tom,
>>>>>
>>>>> Can you point to something specific? Thanks.
>>>>
>>>>
>>>> action reset
>>>> ...[RFC ZZZZ]
>>>> ...
>>>> leaf value
>>>> [RFC2104]...[RFC4868]... [RFC8697]...  [RFC7693]
>>>> ...
>>>> leaf value
>>>> [RFC7468]
>>>>
>>>> Tom Petch
>>>>
>>>>
>>>>
>>>>>
>>>>>> On May 14, 2021, at 3:20 AM, tom petch <daedulus@btconnect.com>
>>>>>> wrote:
>>>>>>
>>>>>> On 12/05/2021 21:46, Mahesh Jethanandani wrote:
>>>>>>> This has been addressed in -10 version of the draft. Cheers.
>>>>>>
>>>>>> Indeed it has.
>>>>>>
>>>>>> I note that some YANG clauses have [references] in them which are
>>>>>> likely not plain text; doubtless that will be fixed at some point
>>>>>> in the process.
>>>>>>
>>>>>> Tom Petch
>>>>>>>
>>>>>>>> On Apr 12, 2021, at 1:38 AM, tom petch
>>>>>>>> <daedulus@btconnect.com> wrote:
>>>>>>>>
>>>>>>>> This I-D introduces a new and unnecessary YANG prefix in
>>>>>>>> defiance of BCP216 s.4.2.
>>>>>>>>
>>>>>>>> It imports ietf-yang-types, perhaps the most widely imported
>>>>>>>> module in the world, and RFC6991, where that module is
>>>>>>>> specified, defines the proper prefix as 'yang'.  This I-D
>>>>>>>> invents a different one. Technically, YANG can cope with this
>>>>>>>> but that does not make it a sensible thing to do.
>>>>>>>>
>>>>>>>> Tom Petch
>>>>>>>>
>>>>>>>> On 08/04/2021 13:43, The IESG wrote:
>>
>>>>>
>>>>> Mahesh Jethanandani mjethanandani@gmail.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> Mahesh Jethanandani
>>> mjethanandani@gmail.com
>>>
>>>
>>>
>>>
>>>
>>>
>
> Mahesh Jethanandani
> mjethanandani@gmail.com
>
>
>
>
>
>


From nobody Mon May 24 19:57:44 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C54A3A0D39; Mon, 24 May 2021 19:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, 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 s5YIBLn7k0at; Mon, 24 May 2021 19:57:39 -0700 (PDT)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 1315A3A0D4B; Mon, 24 May 2021 19:57:35 -0700 (PDT)
Received: by mail-il1-x134.google.com with SMTP id g11so22844682ilq.3; Mon, 24 May 2021 19:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=STWhppK5U8QRZ3vlx2pVlQE+JpMaRoUbl9X05ik8tGY=; b=HLLqq/hKwZWGmIlQouAZxgFu876De4HOrg9ngKkaLxtHcGt+9RVL/G2brt6dm70170 cbroMc8y4y8eYmx+Wb+X4jSKzRPc7vj7I13Ju4PnzsymZKGx1z/jeTcRX6qQmWhJHqLf OjIvutXYRdZJiZSOe3ST/5F5CS7FkEriuGMkTGeH4Llomr3yvAml1jOlOAK6OadPU9i1 R/vIg/S+d/XnMfQvJDUVRE8cT4fLNIU2MeccC4q8YlbeLMx/muB8PeUWLg/NRzTMDxVr mtItPphlvKFssTbRpFvoOhmeFKUHOT4iLEPk4DEv0fDMkNsH7BTSfgn9u3oclcGb9xU3 L2Dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=STWhppK5U8QRZ3vlx2pVlQE+JpMaRoUbl9X05ik8tGY=; b=T5wY/UmbKvIEg3I737Bl/yc1feomufBsAHqfAMi37Xot4gyPtVEXlz6dTkc5KDt63a pQ9dWLaY31GAwQj3Jtj5PkydXxWrDPJLPdj30NU3JnHOJYxiTnmql2KzDCnfjRPXO/S6 R//fDrlJ8AcNXhL9M72j5pOIUfnooH2BHKNYuzGGXkYZCRV4j2i2OmWovlRP+ak8bm5W EHo7o8P6xSgpJn77brbgseKtsqg4CXDncyM7R078y4KEWdthyEtRD2fk0lKWp1+VH8ZQ s4ZM6EXkdvhJWtMvG/UGxjNinr2aqJZD48bKQnQV0/jUUoe05e2cCeBRoEAEzeJImBZM HXIA==
X-Gm-Message-State: AOAM530ylMEHXnqbjr1OMqWk7QXCuL8YrhSkYyoeSsqZjp0qkaiiiN3k CzVnkJqZBDAqO53dVDPEeo9L9Vn3xQ3/cDu68HhDn34UgHw=
X-Google-Smtp-Source: ABdhPJytQlO0giwF5z8033umAsRHUh99NSad7LtZq/Uxyou1MmOkK8rxsNQYo5e2wc7we432N+aX4KYqL3bA11eriH4=
X-Received: by 2002:a92:6b05:: with SMTP id g5mr18355311ilc.40.1621911454155;  Mon, 24 May 2021 19:57:34 -0700 (PDT)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 24 May 2021 22:57:23 -0400
Message-ID: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000015091b05c31eb06f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/IjB10dtbk680uhKef2MZ6U6f20U>
Subject: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 May 2021 02:57:43 -0000

--00000000000015091b05c31eb06f
Content-Type: text/plain; charset="UTF-8"

Hi,

Currently we have completed all the established milestones for the WG. It
seems to me that we should have some future milestones.

In the slides from the last Babel WG meeting at
https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-agenda-and-status-03
that were presented at the last IETF meeting, I suggested three additional
milestones. The last one related to Babel for 802.11 mesh was controversial
but there did not appear to be any objections to the other two.

So, I plan to add the following two milestones (I believe new milestones
need to be OKed by our AD):

  June 2021   IESG submission of IPv4 via IPv6.
  Sept 2021   WG adoption of a Babel multicast draft.

Perhaps the Babel WG meeting at the July IETF meeting (July 26-30) should
focus on multicast.

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

--00000000000015091b05c31eb06f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>Currently we have completed all the established=
 milestones for the WG. It seems to me that we should have some future mile=
stones.<br><br><div>In the slides from the last Babel WG meeting at<br><a h=
ref=3D"https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-=
agenda-and-status-03">https://datatracker.ietf.org/meeting/110/materials/sl=
ides-110-babel-agenda-and-status-03</a><br>that were presented at the last =
IETF meeting, I suggested three additional milestones. The last one related=
 to Babel for 802.11 mesh was controversial but there did not appear to be =
any objections to the other two.<br><br>So, I plan to add the following two=
 milestones (I believe new milestones need to be OKed by our AD):</div><div=
><br></div><div><font face=3D"monospace">=C2=A0 June 2021=C2=A0 =C2=A0IESG =
submission of IPv4 via IPv6.</font></div><div><font face=3D"monospace">=C2=
=A0 Sept 2021=C2=A0 =C2=A0WG adoption of a Babel multicast draft.</font><br=
><br>Perhaps the Babel WG meeting at the July IETF meeting (July 26-30) sho=
uld focus on multicast.</div><div><br>Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br>=C2=A0Donald E. Eastlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A0=
2386 Panoramic Circle, Apopka, FL 32703 USA<br>=C2=A0<a href=3D"mailto:d3e3=
e3@gmail.com">d3e3e3@gmail.com</a></div></div>

--00000000000015091b05c31eb06f--


From nobody Tue May 25 08:03:33 2021
Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710573A0E94 for <babel@ietfa.amsl.com>; Tue, 25 May 2021 08:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mg-bwc3VBDCQ for <babel@ietfa.amsl.com>; Tue, 25 May 2021 08:03:26 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48D623A0E62 for <babel@ietf.org>; Tue, 25 May 2021 08:03:25 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 14PF3K3o018703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 25 May 2021 17:03:20 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 14PF3KYN016247; Tue, 25 May 2021 17:03:20 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 2F8D4C0D6C; Tue, 25 May 2021 17:03:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id zfnX8uvlqLcP; Tue, 25 May 2021 17:03:17 +0200 (CEST)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 975B3C0D5B; Tue, 25 May 2021 17:03:15 +0200 (CEST)
Date: Tue, 25 May 2021 17:03:15 +0200
Message-ID: <87v976voss.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Babel at IETF <babel@ietf.org>
In-Reply-To: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com>
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/28.0 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 25 May 2021 17:03:20 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 25 May 2021 17:03:20 +0200 (CEST)
X-Miltered: at korolev with ID 60AD11B8.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 60AD11B8.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 60AD11B8.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@irif.fr>
X-j-chkmail-Enveloppe: 60AD11B8.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 60AD11B8.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 60AD11B8.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/7FNgB7n3U5F-DsVx2KrsWxR-kk8>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 May 2021 15:03:32 -0000

Hi Donald,

> So, I plan to add the following two milestones (I believe new milestones need
> to be OKed by our AD):
> 
>   June 2021   IESG submission of IPv4 via IPv6.

Donald, I'd like to expand the introduction to this document before it is
submitted to the IESG -- no content changes, just wording.  Is it possible
to do that without restarting last call?

>   Sept 2021   WG adoption of a Babel multicast draft.

What do you envision?  Babeld works with PIM-SM (that's what the
"reflect-kernel-metric" option is for), but I'm not seeing a lot of
interest.  I'm not following the DNSSD/mDNS community closely, but I'm
under the impression that they're focusing on multicast-to-unicast proxies
instead of site-local multicast (draft-cheshire-mdnsext-hybrid).

There's also Sandy's BIER for Babel work, but I fear it may have been
abandoned.

> Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
> should focus on multicast.

My personal plans are to finish merging HMAC and v4-via-v6 into babeld
mainline, and then to get back to working on network-layer mobility:

  https://www.irif.fr/~jch/software/sroamd.git

-- Juliusz


From nobody Tue May 25 11:25:04 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB9E3A187D for <babel@ietfa.amsl.com>; Tue, 25 May 2021 11:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 Kbv4iz9QUhFm for <babel@ietfa.amsl.com>; Tue, 25 May 2021 11:24:57 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 75D833A187A for <babel@ietf.org>; Tue, 25 May 2021 11:24:57 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id a8so24497263ioa.12 for <babel@ietf.org>; Tue, 25 May 2021 11:24:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Brygt4l9d1iGjQPyZRWJpMA1TPf0iCSLb1rMOC87Dn0=; b=DWVeDiWQSOp/IahtbUB2BFTi+3zHvUH4m0lHSAhbDcnmRsQf++JuiKwcnjbmSmsPf7 GFUZcovxljjtWBH5MOZ3y1NPKoFpayYzj98CyRu9lGEGko8r81YXtsYPMU2RcOBnC2wg rpQENRnvMyyKDWwbIooz8O/BWgZgM1yBTa2o9c65bd/f8nxnI3rIJWChwu/23McJfreg 32ZEjqGU2wP4QUdhnSV8C8ac6fNEWSdbHKIKbifQ/K0U4g2uX3XSlM+8uPBEDzZOKYQB fIkgkiDNFMXYLbWcU0s2M14CayvgrAp4vA+8OKtTNU1S0gLrRNhObZwsV8cXQLorQuPI PZ3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Brygt4l9d1iGjQPyZRWJpMA1TPf0iCSLb1rMOC87Dn0=; b=MF4jlxKbQ/GLnMtOSTdSXCqaJZhzTaybECFs1anV8+BZJ9FWz42LnY4GiBe45MAnYE n+19cJuT6q02+cvIurfFfMyS3pLIvfPN+XsWsinlbWUXIiYl6b6ZfekYaE50JgeYQVSu YxBdfqWTIR1GJDdXDAMwB7u5HnLaznjMHtY+4p32ZhJA90e6bf4uiyQU+3QBT+rNhxw+ NKUpmhFpQQzNq1Qrl+yePRPdPfWRcppw8DnbPnKDLQmzQFEnejGqO6msvkQ8b6Dzw4gz //3blRCJ4OVHUR3kZbz5cpx8nhSaBRhyxL+IfHMeidmMpTaVToa2J94n65n1RqEHdqQZ wiMQ==
X-Gm-Message-State: AOAM532mVWEuD+zQz/zT3da8a7YH+pdXG/Zz31cTLHPluoaQ1D6eXBMc LGrnyd/zRHz7AVltxNkItSixNUku/Wng8M+Khkk=
X-Google-Smtp-Source: ABdhPJzzFJSniLSagdxl0wXY8ElcStceZ4fS5EfaJ7D891a2fcFmt24mgSeEGJc8DqhvQWn6fGr02VbRHDlsGbstGY4=
X-Received: by 2002:a02:5409:: with SMTP id t9mr32848064jaa.50.1621967096190;  Tue, 25 May 2021 11:24:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr>
In-Reply-To: <87v976voss.wl-jch@irif.fr>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 25 May 2021 14:24:45 -0400
Message-ID: <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/xTUL_umu5X9ApUmGfgWTqu7AqTk>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 May 2021 18:25:02 -0000

Hi Juliusz,

On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> Hi Donald,
>
> > So, I plan to add the following two milestones (I believe new milestones need
> > to be OKed by our AD):
> >
> >   June 2021   IESG submission of IPv4 via IPv6.
>
> Donald, I'd like to expand the introduction to this document before it is
> submitted to the IESG -- no content changes, just wording.  Is it possible
> to do that without restarting last call?

Probably. The Introduction does not seem to be controversial. I
suggested a change to the Introduction here
https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
and there were no complaints. You could propose a different change to
the Introduction as a resolution to my comment. Since all this is
getting posted to the WG mailing list, if no one speaks up in 7 or 8
days and there are no technical changes to the protocol, I don't think
we would need a new WG Last Call.

> >   Sept 2021   WG adoption of a Babel multicast draft.
>
> What do you envision?

Multicast is mentioned in the Babel WG Charter as something optional
to work on. This is just my personal opinion but a routing system that
doesn't handle both unicast and multicast seems incomplete to me.

> Babeld works with PIM-SM (that's what the
> "reflect-kernel-metric" option is for), but I'm not seeing a lot of
> interest.

Is this discussed in any of the Babel RFCs or drafts? Seems like
something somewhere in the IETF Babel documentation should talk about
at least a way to do multicast.

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

> I'm not following the DNSSD/mDNS community closely, but I'm
> under the impression that they're focusing on multicast-to-unicast proxies
> instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
>
> There's also Sandy's BIER for Babel work, but I fear it may have been
> abandoned.
>
> > Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
> > should focus on multicast.
>
> My personal plans are to finish merging HMAC and v4-via-v6 into babeld
> mainline, and then to get back to working on network-layer mobility:
>
>   https://www.irif.fr/~jch/software/sroamd.git
>
> -- Juliusz


From nobody Tue May 25 17:24:14 2021
Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF0A3A152D for <babel@ietfa.amsl.com>; Tue, 25 May 2021 17:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 opsAXPrtuz8v for <babel@ietfa.amsl.com>; Tue, 25 May 2021 17:24:09 -0700 (PDT)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 E9DE43A1527 for <babel@ietf.org>; Tue, 25 May 2021 17:24:08 -0700 (PDT)
Received: by mail-pj1-x102b.google.com with SMTP id g6-20020a17090adac6b029015d1a9a6f1aso2682543pjx.1 for <babel@ietf.org>; Tue, 25 May 2021 17:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hb04AhiG41lgk+UFv5UiqRDc7cMwbRAiLi5efe/NO+0=; b=ompG6b+N1vWUMKQqHo7GNff2ziCPFYVvSJ/8qR5tXVB0I8LmRK6kUsPCbuQOJBd8j5 c+p/snVhJ7pSVNR9ghKYSLlV8eo2EKW1FoNQyoV+zLyh8cLewG03XUC8Wy5bOc4gdJ/x 90LVb/uJLjKbPEVhxNMDQ1L5TQPE485mCsXuYIxq1bz+m6+RKwHYTCOmagErWIdXk3tf /aS3JfcZSp0FZYBqxud3phFwiP+Wgf3C+oONvWcogjES4vdSW3H5NznjmT+2M4nmhF2P y1xu1zyLN4fu21HUtISmXlOFOikIeptbyA8Hx7s3Ntnp9Mtv2Gyhu6C//U9H2tg9LfaO yrpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hb04AhiG41lgk+UFv5UiqRDc7cMwbRAiLi5efe/NO+0=; b=TT+nhLnozW7XZKw3BYm4+n45aNXwfGsy19vpd3/u3YmYIFUC0mpDuEnjRKh/Nir+fZ EnMFL3gqgsKU+yQZLw2ZFa/1lUxx9K+0/iPeZ6ttMRaOB+r9ODr9t5wWdLndMz3NBdSL rkoA6IOG0E1UDlo1Aqsx0UvCTBONychIejUd9brO0Q5+3KjE0WlprA/xQdl+Mw5D3ALJ LVuOYG0y5ELyXiuEhSupUL9frsdVO5LjPC8nBLeOuOGGA1N2ddzC3wCrsdM7wcXgwk2F p41JOPDIwW4cFzBXemAAQvkXHX/CNr6U+OKGc1sezKIY/FLeLsyg3h5hsgns5fjjxg5n MS5g==
X-Gm-Message-State: AOAM530FPhnvxCH09lfAFAFnjGWWb3Y5uKZqDmrZvRnSPytJqU8gn9UG AxcbPVlTS9fsfpw8RhEeetgW76qvrNJRjthJkLA=
X-Google-Smtp-Source: ABdhPJySBFgELYgupkSP9+LD/SNwTjWEyR4ZbYj6v7WtdjS/CQKEczxVkh2sDsYZvqM7S8zGyGAoTUFsXzReVY/WmC4=
X-Received: by 2002:a17:902:650d:b029:f2:2012:a58 with SMTP id b13-20020a170902650db02900f220120a58mr32789447plk.5.1621988647883; Tue, 25 May 2021 17:24:07 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com>
In-Reply-To: <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 25 May 2021 17:23:56 -0700
Message-ID: <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002fd6b305c330a9cd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/UL0P2ZX-ca8QxU0R2PJHl5QvBKA>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 00:24:14 -0000

--0000000000002fd6b305c330a9cd
Content-Type: text/plain; charset="UTF-8"

Adding "IESG submission of IPv4 via IPv6" as a
milestone is fine by me, because we're about to do that
anyway. I've never found milestones to be useful, so
I'm not sure there's any benefit in doing this as opposed
to just submitting the draft for publication.

I'm supportive of Juliusz making editorial changes before
submitting to the IESG, I'm sure the IESG review will lead
to editorial changes anyway, and so will IETF last call.

Regarding the "WG adoption of a Babel multicast draft"
milestone, I would personally like to see such a draft
written and discussed at a WG meeting before a
milestone is added. That would ensure that we have folks
willing to do the work for this to happen.

I disagree with Donald's statement that "a routing system that
doesn't handle both unicast and multicast seems incomplete",
because I have yet to find a general-purpose use-case for
non-link-local multicast whereas unicast is general-purpose :-)

David

On Tue, May 25, 2021 at 11:25 AM Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Juliusz,
>
> On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr> wrote:
> >
> > Hi Donald,
> >
> > > So, I plan to add the following two milestones (I believe new
> milestones need
> > > to be OKed by our AD):
> > >
> > >   June 2021   IESG submission of IPv4 via IPv6.
> >
> > Donald, I'd like to expand the introduction to this document before it is
> > submitted to the IESG -- no content changes, just wording.  Is it
> possible
> > to do that without restarting last call?
>
> Probably. The Introduction does not seem to be controversial. I
> suggested a change to the Introduction here
> https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
> and there were no complaints. You could propose a different change to
> the Introduction as a resolution to my comment. Since all this is
> getting posted to the WG mailing list, if no one speaks up in 7 or 8
> days and there are no technical changes to the protocol, I don't think
> we would need a new WG Last Call.
>
> > >   Sept 2021   WG adoption of a Babel multicast draft.
> >
> > What do you envision?
>
> Multicast is mentioned in the Babel WG Charter as something optional
> to work on. This is just my personal opinion but a routing system that
> doesn't handle both unicast and multicast seems incomplete to me.
>
> > Babeld works with PIM-SM (that's what the
> > "reflect-kernel-metric" option is for), but I'm not seeing a lot of
> > interest.
>
> Is this discussed in any of the Babel RFCs or drafts? Seems like
> something somewhere in the IETF Babel documentation should talk about
> at least a way to do multicast.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
> > I'm not following the DNSSD/mDNS community closely, but I'm
> > under the impression that they're focusing on multicast-to-unicast
> proxies
> > instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
> >
> > There's also Sandy's BIER for Babel work, but I fear it may have been
> > abandoned.
> >
> > > Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
> > > should focus on multicast.
> >
> > My personal plans are to finish merging HMAC and v4-via-v6 into babeld
> > mainline, and then to get back to working on network-layer mobility:
> >
> >   https://www.irif.fr/~jch/software/sroamd.git
> >
> > -- Juliusz
>
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel
>

--0000000000002fd6b305c330a9cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Adding &quot;IESG submission of IPv4 via IPv6&quot; as a<d=
iv>milestone is fine by me, because we&#39;re about to do that</div><div>an=
yway. I&#39;ve never found milestones to be useful, so</div><div>I&#39;m no=
t sure there&#39;s any benefit in doing this as opposed</div><div>to just s=
ubmitting the draft for publication.</div><div><br></div><div>I&#39;m suppo=
rtive of Juliusz making editorial changes before</div><div>submitting to th=
e IESG, I&#39;m sure the IESG review will lead</div><div>to editorial chang=
es anyway, and so will IETF last call.</div><div><br></div><div>Regarding t=
he &quot;WG adoption of a Babel multicast draft&quot;</div><div>milestone, =
I would personally like to see such a draft</div><div>written and discussed=
 at a WG meeting before a</div><div>milestone is added. That would ensure t=
hat we have folks</div><div>willing to do the work for this to happen.</div=
><div><br></div><div>I disagree with Donald&#39;s statement that &quot;a ro=
uting system that</div>doesn&#39;t handle both unicast and multicast seems =
incomplete&quot;,<div>because I have yet to find a general-purpose use-case=
 for</div><div>non-link-local multicast whereas unicast is general-purpose=
=C2=A0:-) <br><div><br></div><div>David</div></div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 25, 2021 at =
11:25 AM Donald Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gma=
il.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">Hi Juliusz,<br>
<br>
On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek &lt;<a href=3D"mailto:j=
ch@irif.fr" target=3D"_blank">jch@irif.fr</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Donald,<br>
&gt;<br>
&gt; &gt; So, I plan to add the following two milestones (I believe new mil=
estones need<br>
&gt; &gt; to be OKed by our AD):<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0June 2021=C2=A0 =C2=A0IESG submission of IPv4 via IPv=
6.<br>
&gt;<br>
&gt; Donald, I&#39;d like to expand the introduction to this document befor=
e it is<br>
&gt; submitted to the IESG -- no content changes, just wording.=C2=A0 Is it=
 possible<br>
&gt; to do that without restarting last call?<br>
<br>
Probably. The Introduction does not seem to be controversial. I<br>
suggested a change to the Introduction here<br>
<a href=3D"https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy=
92hjfwI/" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org=
/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/</a><br>
and there were no complaints. You could propose a different change to<br>
the Introduction as a resolution to my comment. Since all this is<br>
getting posted to the WG mailing list, if no one speaks up in 7 or 8<br>
days and there are no technical changes to the protocol, I don&#39;t think<=
br>
we would need a new WG Last Call.<br>
<br>
&gt; &gt;=C2=A0 =C2=A0Sept 2021=C2=A0 =C2=A0WG adoption of a Babel multicas=
t draft.<br>
&gt;<br>
&gt; What do you envision?<br>
<br>
Multicast is mentioned in the Babel WG Charter as something optional<br>
to work on. This is just my personal opinion but a routing system that<br>
doesn&#39;t handle both unicast and multicast seems incomplete to me.<br>
<br>
&gt; Babeld works with PIM-SM (that&#39;s what the<br>
&gt; &quot;reflect-kernel-metric&quot; option is for), but I&#39;m not seei=
ng a lot of<br>
&gt; interest.<br>
<br>
Is this discussed in any of the Babel RFCs or drafts? Seems like<br>
something somewhere in the IETF Babel documentation should talk about<br>
at least a way to do multicast.<br>
<br>
Thanks,<br>
Donald<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>
=C2=A0Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br>
=C2=A02386 Panoramic Circle, Apopka, FL 32703 USA<br>
=C2=A0<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.co=
m</a><br>
<br>
&gt; I&#39;m not following the DNSSD/mDNS community closely, but I&#39;m<br=
>
&gt; under the impression that they&#39;re focusing on multicast-to-unicast=
 proxies<br>
&gt; instead of site-local multicast (draft-cheshire-mdnsext-hybrid).<br>
&gt;<br>
&gt; There&#39;s also Sandy&#39;s BIER for Babel work, but I fear it may ha=
ve been<br>
&gt; abandoned.<br>
&gt;<br>
&gt; &gt; Perhaps the Babel WG meeting at the July IETF meeting (July 26-30=
)<br>
&gt; &gt; should focus on multicast.<br>
&gt;<br>
&gt; My personal plans are to finish merging HMAC and v4-via-v6 into babeld=
<br>
&gt; mainline, and then to get back to working on network-layer mobility:<b=
r>
&gt;<br>
&gt;=C2=A0 =C2=A0<a href=3D"https://www.irif.fr/~jch/software/sroamd.git" r=
el=3D"noreferrer" target=3D"_blank">https://www.irif.fr/~jch/software/sroam=
d.git</a><br>
&gt;<br>
&gt; -- Juliusz<br>
<br>
_______________________________________________<br>
babel mailing list<br>
<a href=3D"mailto:babel@ietf.org" target=3D"_blank">babel@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/babel" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/babel</a><br>
</blockquote></div>

--0000000000002fd6b305c330a9cd--


From nobody Tue May 25 21:02:34 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0FE23A1E81 for <babel@ietfa.amsl.com>; Tue, 25 May 2021 21:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 FM50xXr__cCp for <babel@ietfa.amsl.com>; Tue, 25 May 2021 21:02:27 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 9B8CF3A1E80 for <babel@ietf.org>; Tue, 25 May 2021 21:02:27 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id b81so12126239iof.2 for <babel@ietf.org>; Tue, 25 May 2021 21:02:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CKVXm4z6DiE661ZUT0vQwFTCEOI/5mnp0iJllKCMf54=; b=e/eQHqg1Oc3HGj7n/f1rcA8plUi/GV4hTnMsHR0pHpNOeoVyrnNNbMkI6+cD3P7MCI s7vWQip0v5B2DztFFd7iEe7pXN0NYZlzDyodfAF9oygNehQ6ch/nCl1GJSa+JUIlTa0c OW8zTJNdgUau1ow2PLVglD8P0yI5usPhhAAKOLaxUM0ZvAjzzjuVOPco7XlYJKX1duzG k48DcG4T3VyUp9CSUAmEjJWl73YeEDl6K9d6J1oaFX89tH7nNnzRR4SkbABi+fBEIB9B UAgXFNYAjw1w064zqNdW2Wy8LQflVOv+EXx1S2+PaHr9LlhlatbVli/KUurYTXGU21p5 6yng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CKVXm4z6DiE661ZUT0vQwFTCEOI/5mnp0iJllKCMf54=; b=Wj8iKPXxtwOu4dCXnxXQG1sxggwbWHMBLTDXVzAjSgYGp+ycG/2dmnhWUYKo/6Dyi0 nS55KzsJFRAmEurLka/g9wdPfLUFVAba0v+2t6iwpb8qkixa1UWERZwuH0k4yxvJkUYd Ky6M4xx/gwV/siqzq3xRN64PysRNdyeBuUfxq+Wka9VhCwzC7xmbAiNEDYHeaHjJ3qsn Fa39F104zBo3tvz3N0lr/W5H0oIROBXlPtCAbE1Y1dRYY4bQ9cyo1OpWqAlPUeV1slZ5 GeLiyp4vHW/TJvEMYQOolY8zPNPHTWY6F03u/NxCeYJYu73iEIBMzGDtUcPFBo1fzb1p Ng4A==
X-Gm-Message-State: AOAM531JNcpkZsc4kqkBRydRPrHWFGv28h03uQFH+wfJKTvvgjHRVRa4 Mz/EF6EH/lVHosTdlJOp/kpfMxmp4r5il+aWA0E=
X-Google-Smtp-Source: ABdhPJzESJziJKhQTpfKLCkZ8wnExVqFjELWpZADHkSqLV3OqYf2OJODKTMKvLR2r7HdnKjH1UeBabvJIT+oO7bJZDA=
X-Received: by 2002:a5d:8d87:: with SMTP id b7mr20664038ioj.46.1622001746238;  Tue, 25 May 2021 21:02:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com>
In-Reply-To: <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 26 May 2021 00:02:15 -0400
Message-ID: <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Ho4S9gWwRy1TkOFL0VXnoYekvis>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 04:02:32 -0000

Hi David,

On Tue, May 25, 2021 at 8:24 PM David Schinazi <dschinazi.ietf@gmail.com> wrote:
>
> Adding "IESG submission of IPv4 via IPv6" as a
> milestone is fine by me, because we're about to do that
> anyway. I've never found milestones to be useful, so
> I'm not sure there's any benefit in doing this as opposed
> to just submitting the draft for publication.

I think milestones give an idea of what the WG has accomplished or may
accomplish in the future. They sort of supplement the Charter. But I'm
willing to admit that the "IESG submission of IPv4 via IPv6" doesn't
add that much. On the other hand, it's mostly the Chairs doing the
work to modify/track the set of milestones.

> I'm supportive of Juliusz making editorial changes before
> submitting to the IESG, I'm sure the IESG review will lead
> to editorial changes anyway, and so will IETF last call.

OK.

> Regarding the "WG adoption of a Babel multicast draft"
> milestone, I would personally like to see such a draft
> written and discussed at a WG meeting before a
> milestone is added. That would ensure that we have folks
> willing to do the work for this to happen.

I don't see why a milestone can't be aspirational.

> I disagree with Donald's statement that "a routing system that
> doesn't handle both unicast and multicast seems incomplete",
> because I have yet to find a general-purpose use-case for
> non-link-local multicast whereas unicast is general-purpose :-)

What makes one use "general" and another "special"?

What is a "link"? Say you have a network of Babel routers. Some
communicate by radio where the transmission on one of its radios by a
router may be received by zero, one, or more other routers. Some
communicate by wire/Ethernet but some of those connections are bridged
so those inter-router connections are more stable but can be
bi-lateral or multilateral. What exactly is a link in this network?

I tend to think of multicast as being either discovery multicast or
application multicast. For application multicast, generally you can
use head end replication and unicast which is less efficient in terms
of link utilization and generally has higher latency due to multiple
copies being sent on a link but might be simpler; on the other hand,
if there are lots of sources and multicast groups, these head ends
have to all keep track of who to unicast to. For discovery, you can't
do everything with unicast because, by definition, you want to be able
to find nodes that you don't know about yet; but you can probably get
away with unicast + link local multicast for some definition of link.
So I agree you can find some way to do everything with unicast and
link local multicast but that doesn't mean it is the best way to do
everything.

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

> David
>
> On Tue, May 25, 2021 at 11:25 AM Donald Eastlake <d3e3e3@gmail.com> wrote:
>>
>> Hi Juliusz,
>>
>> On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>> >
>> > Hi Donald,
>> >
>> > > So, I plan to add the following two milestones (I believe new milestones need
>> > > to be OKed by our AD):
>> > >
>> > >   June 2021   IESG submission of IPv4 via IPv6.
>> >
>> > Donald, I'd like to expand the introduction to this document before it is
>> > submitted to the IESG -- no content changes, just wording.  Is it possible
>> > to do that without restarting last call?
>>
>> Probably. The Introduction does not seem to be controversial. I
>> suggested a change to the Introduction here
>> https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
>> and there were no complaints. You could propose a different change to
>> the Introduction as a resolution to my comment. Since all this is
>> getting posted to the WG mailing list, if no one speaks up in 7 or 8
>> days and there are no technical changes to the protocol, I don't think
>> we would need a new WG Last Call.
>>
>> > >   Sept 2021   WG adoption of a Babel multicast draft.
>> >
>> > What do you envision?
>>
>> Multicast is mentioned in the Babel WG Charter as something optional
>> to work on. This is just my personal opinion but a routing system that
>> doesn't handle both unicast and multicast seems incomplete to me.
>>
>> > Babeld works with PIM-SM (that's what the
>> > "reflect-kernel-metric" option is for), but I'm not seeing a lot of
>> > interest.
>>
>> Is this discussed in any of the Babel RFCs or drafts? Seems like
>> something somewhere in the IETF Babel documentation should talk about
>> at least a way to do multicast.
>>
>> Thanks,
>> Donald
>> ===============================
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  2386 Panoramic Circle, Apopka, FL 32703 USA
>>  d3e3e3@gmail.com
>>
>> > I'm not following the DNSSD/mDNS community closely, but I'm
>> > under the impression that they're focusing on multicast-to-unicast proxies
>> > instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
>> >
>> > There's also Sandy's BIER for Babel work, but I fear it may have been
>> > abandoned.
>> >
>> > > Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
>> > > should focus on multicast.
>> >
>> > My personal plans are to finish merging HMAC and v4-via-v6 into babeld
>> > mainline, and then to get back to working on network-layer mobility:
>> >
>> >   https://www.irif.fr/~jch/software/sroamd.git
>> >
>> > -- Juliusz
>>
>> _______________________________________________
>> babel mailing list
>> babel@ietf.org
>> https://www.ietf.org/mailman/listinfo/babel


From nobody Wed May 26 11:41:53 2021
Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9691B3A07BA for <babel@ietfa.amsl.com>; Wed, 26 May 2021 11:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 fQkXlAvGjjaB for <babel@ietfa.amsl.com>; Wed, 26 May 2021 11:41:47 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 8983F3A07B6 for <babel@ietf.org>; Wed, 26 May 2021 11:41:47 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id f22so1653078pfn.0 for <babel@ietf.org>; Wed, 26 May 2021 11:41:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2e5dSuxiDhLvZLBlfxMCZNEI3nmt9JTGyl+hM6xKSpU=; b=jNyZHZM1rUXAQcoXy21JZWRZ7kqkkmCATuK+9mrcJ+9vVjlcJukxoyVxnk41LeKQgQ UvjEhM1G5zwvnD/Bz/0izouJzZ5qTQMtr4WjkGHpgW+ucmaEai6/ufUc67XYn3jPKb35 2pfPNK1DdONDHFcgUQE4RTw/MmR5pK6MsMXkWauWCQ6+kmvt/zkJCti2UhD53dQhIRsn K1xE8azDqOPnSOSB5HJitqMiue0pWkANARDpgbxnPlh9Ddd6TdXAKgIg4V2NFpXaBxRO 8atnveuCnEuVUkIZZo/uSewoFT62xDIvqQz6DTxL+UVB/5hPhDT4PWXMv+tMKqAgRtpO tWzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2e5dSuxiDhLvZLBlfxMCZNEI3nmt9JTGyl+hM6xKSpU=; b=GFXeEGcGP7g5xDDYM41FJNcguLQBELpgarPlTFsHoZjbOCULbciwyCNauHtFqO9VPI 5/9O73Y5sJgBDj6wQtlFz0rdgLRweNiBqrNORcIA7STgXBGqHJcTXpyLcDDsG83PSDzV jqwPKS/CbX/OnG4M1R1IcA5uRiVxKwyhx5rvy4EisQubZ0Fkq2M/VhU1RppwFmPexdHz QNzCTDypOUEmW6q5kzUaCLQHFK1Rex4ryPVPNv916k4RIIQiazwURqiRpdDuy8NzHiCC ZGT2YSZo2TxAvHt1Mnn0id1+2Z7xv2BTdnOWhe9qmw9j+AMYYj766odmTg/eIzakjEwx wT+Q==
X-Gm-Message-State: AOAM533cdX9zIUwpxemthKr3QKidOW+3Z3RzAG8P6VFzXXEgB2BqMA3o RLOu7iPNuOizsWIPlxv823gpacGDRi9aG886xMU=
X-Google-Smtp-Source: ABdhPJw+vixLkT20kpdpCTF0Oao8PvZMrTgfbZD6wZUeGUSrn2TFj00l0yWxFi3W9Ja8XQkT83c6Rgk8fwQaxz+bgWU=
X-Received: by 2002:a63:7206:: with SMTP id n6mr8166979pgc.206.1622054506343;  Wed, 26 May 2021 11:41:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com>
In-Reply-To: <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 26 May 2021 11:41:35 -0700
Message-ID: <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8319705c33ffe80"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/rJnlpInW8LxP6tVOBi6jHnwi7SQ>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 18:41:52 -0000

--000000000000a8319705c33ffe80
Content-Type: text/plain; charset="UTF-8"

On Tue, May 25, 2021 at 9:02 PM Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi David,
>
> On Tue, May 25, 2021 at 8:24 PM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
> >
> > Adding "IESG submission of IPv4 via IPv6" as a
> > milestone is fine by me, because we're about to do that
> > anyway. I've never found milestones to be useful, so
> > I'm not sure there's any benefit in doing this as opposed
> > to just submitting the draft for publication.
>
> I think milestones give an idea of what the WG has accomplished or may
> accomplish in the future. They sort of supplement the Charter. But I'm
> willing to admit that the "IESG submission of IPv4 via IPv6" doesn't
> add that much. On the other hand, it's mostly the Chairs doing the
> work to modify/track the set of milestones.
>

To clarify, I don't object to the chairs creating a
"IESG submission of IPv4 via IPv6" milestone.

> I'm supportive of Juliusz making editorial changes before
> > submitting to the IESG, I'm sure the IESG review will lead
> > to editorial changes anyway, and so will IETF last call.
>
> OK.
>
> > Regarding the "WG adoption of a Babel multicast draft"
> > milestone, I would personally like to see such a draft
> > written and discussed at a WG meeting before a
> > milestone is added. That would ensure that we have folks
> > willing to do the work for this to happen.
>
> I don't see why a milestone can't be aspirational.
>

Does the aspiration reflect WG consensus? My understanding
is that we're a very implementation-driven WG, and I'd prefer to
have aspirations reflect what implementers aspire to build.
Alternatively, hearing from someone who runs a Babel network
telling us that they have a need for multicast would also be great.

> I disagree with Donald's statement that "a routing system that
> > doesn't handle both unicast and multicast seems incomplete",
> > because I have yet to find a general-purpose use-case for
> > non-link-local multicast whereas unicast is general-purpose :-)
>
> What makes one use "general" and another "special"?
>

I'd say "general-purpose" means there are several applications using
it, whereas "special-purpose" is for a single application.


> What is a "link"? Say you have a network of Babel routers. Some
> communicate by radio where the transmission on one of its radios by a
> router may be received by zero, one, or more other routers. Some
> communicate by wire/Ethernet but some of those connections are bridged
> so those inter-router connections are more stable but can be
> bi-lateral or multilateral. What exactly is a link in this network?
>

My personal definition is: two devices are on the same link if they can
hear each other's Babel Hellos and IHUs.

I tend to think of multicast as being either discovery multicast or
> application multicast. For application multicast, generally you can
> use head end replication and unicast which is less efficient in terms
> of link utilization and generally has higher latency due to multiple
> copies being sent on a link but might be simpler; on the other hand,
> if there are lots of sources and multicast groups, these head ends
> have to all keep track of who to unicast to. For discovery, you can't
> do everything with unicast because, by definition, you want to be able
> to find nodes that you don't know about yet; but you can probably get
> away with unicast + link local multicast for some definition of link.
> So I agree you can find some way to do everything with unicast and
> link local multicast but that doesn't mean it is the best way to do
> everything.
>

In my mind, the best way to perform discovery is to combine unicast
and link-local multicast. That's what we use in DNSSD which is AFAIK
the IETF-recommended way to perform service discovery.

David


Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
> > David
> >
> > On Tue, May 25, 2021 at 11:25 AM Donald Eastlake <d3e3e3@gmail.com>
> wrote:
> >>
> >> Hi Juliusz,
> >>
> >> On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr>
> wrote:
> >> >
> >> > Hi Donald,
> >> >
> >> > > So, I plan to add the following two milestones (I believe new
> milestones need
> >> > > to be OKed by our AD):
> >> > >
> >> > >   June 2021   IESG submission of IPv4 via IPv6.
> >> >
> >> > Donald, I'd like to expand the introduction to this document before
> it is
> >> > submitted to the IESG -- no content changes, just wording.  Is it
> possible
> >> > to do that without restarting last call?
> >>
> >> Probably. The Introduction does not seem to be controversial. I
> >> suggested a change to the Introduction here
> >>
> https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
> >> and there were no complaints. You could propose a different change to
> >> the Introduction as a resolution to my comment. Since all this is
> >> getting posted to the WG mailing list, if no one speaks up in 7 or 8
> >> days and there are no technical changes to the protocol, I don't think
> >> we would need a new WG Last Call.
> >>
> >> > >   Sept 2021   WG adoption of a Babel multicast draft.
> >> >
> >> > What do you envision?
> >>
> >> Multicast is mentioned in the Babel WG Charter as something optional
> >> to work on. This is just my personal opinion but a routing system that
> >> doesn't handle both unicast and multicast seems incomplete to me.
> >>
> >> > Babeld works with PIM-SM (that's what the
> >> > "reflect-kernel-metric" option is for), but I'm not seeing a lot of
> >> > interest.
> >>
> >> Is this discussed in any of the Babel RFCs or drafts? Seems like
> >> something somewhere in the IETF Babel documentation should talk about
> >> at least a way to do multicast.
> >>
> >> Thanks,
> >> Donald
> >> ===============================
> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >>  2386 Panoramic Circle, Apopka, FL 32703 USA
> >>  d3e3e3@gmail.com
> >>
> >> > I'm not following the DNSSD/mDNS community closely, but I'm
> >> > under the impression that they're focusing on multicast-to-unicast
> proxies
> >> > instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
> >> >
> >> > There's also Sandy's BIER for Babel work, but I fear it may have been
> >> > abandoned.
> >> >
> >> > > Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
> >> > > should focus on multicast.
> >> >
> >> > My personal plans are to finish merging HMAC and v4-via-v6 into babeld
> >> > mainline, and then to get back to working on network-layer mobility:
> >> >
> >> >   https://www.irif.fr/~jch/software/sroamd.git
> >> >
> >> > -- Juliusz
> >>
> >> _______________________________________________
> >> babel mailing list
> >> babel@ietf.org
> >> https://www.ietf.org/mailman/listinfo/babel
>

--000000000000a8319705c33ffe80
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 25, 2021 at 9:02 PM Donal=
d Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi David=
,<br>
<br>
On Tue, May 25, 2021 at 8:24 PM David Schinazi &lt;<a href=3D"mailto:dschin=
azi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt; wrot=
e:<br>
&gt;<br>
&gt; Adding &quot;IESG submission of IPv4 via IPv6&quot; as a<br>
&gt; milestone is fine by me, because we&#39;re about to do that<br>
&gt; anyway. I&#39;ve never found milestones to be useful, so<br>
&gt; I&#39;m not sure there&#39;s any benefit in doing this as opposed<br>
&gt; to just submitting the draft for publication.<br>
<br>
I think milestones give an idea of what the WG has accomplished or may<br>
accomplish in the future. They sort of supplement the Charter. But I&#39;m<=
br>
willing to admit that the &quot;IESG submission of IPv4 via IPv6&quot; does=
n&#39;t<br>
add that much. On the other hand, it&#39;s mostly the Chairs doing the<br>
work to modify/track the set of milestones.<br></blockquote><div><br></div>=
<div>To clarify, I don&#39;t object to the chairs creating a</div><div>&quo=
t;IESG submission of IPv4 via IPv6&quot;  milestone.</div><div><br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">
&gt; I&#39;m supportive of Juliusz making editorial changes before<br>
&gt; submitting to the IESG, I&#39;m sure the IESG review will lead<br>
&gt; to editorial changes anyway, and so will IETF last call.<br>
<br>
OK.<br>
<br>
&gt; Regarding the &quot;WG adoption of a Babel multicast draft&quot;<br>
&gt; milestone, I would personally like to see such a draft<br>
&gt; written and discussed at a WG meeting before a<br>
&gt; milestone is added. That would ensure that we have folks<br>
&gt; willing to do the work for this to happen.<br>
<br>
I don&#39;t see why a milestone can&#39;t be aspirational.<br></blockquote>=
<div><br></div><div>Does the aspiration reflect WG consensus? My understand=
ing</div><div>is that we&#39;re a very implementation-driven WG, and I&#39;=
d prefer to</div><div>have aspirations reflect what implementers aspire to =
build.</div><div>Alternatively, hearing from someone who runs a Babel netwo=
rk</div><div>telling us that they have a need for multicast would also be g=
reat.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
&gt; I disagree with Donald&#39;s statement that &quot;a routing system tha=
t<br>
&gt; doesn&#39;t handle both unicast and multicast seems incomplete&quot;,<=
br>
&gt; because I have yet to find a general-purpose use-case for<br>
&gt; non-link-local multicast whereas unicast is general-purpose :-)<br>
<br>
What makes one use &quot;general&quot; and another &quot;special&quot;?<br>=
</blockquote><div><br></div><div>I&#39;d say &quot;general-purpose&quot; me=
ans there are several applications using</div><div>it, whereas &quot;specia=
l-purpose&quot; is for a single application.</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
What is a &quot;link&quot;? Say you have a network of Babel routers. Some<b=
r>
communicate by radio where the transmission on one of its radios by a<br>
router may be received by zero, one, or more other routers. Some<br>
communicate by wire/Ethernet but some of those connections are bridged<br>
so those inter-router connections are more stable but can be<br>
bi-lateral or multilateral. What exactly is a link in this network?<br></bl=
ockquote><div><br></div><div>My personal definition is: two devices are on =
the same link if they can</div><div>hear each other&#39;s Babel Hellos and =
IHUs.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
I tend to think of multicast as being either discovery multicast or<br>
application multicast. For application multicast, generally you can<br>
use head end replication and unicast which is less efficient in terms<br>
of link utilization and generally has higher latency due to multiple<br>
copies being sent on a link but might be simpler; on the other hand,<br>
if there are lots of sources and multicast groups, these head ends<br>
have to all keep track of who to unicast to. For discovery, you can&#39;t<b=
r>
do everything with unicast because, by definition, you want to be able<br>
to find nodes that you don&#39;t know about yet; but you can probably get<b=
r>
away with unicast + link local multicast for some definition of link.<br>
So I agree you can find some way to do everything with unicast and<br>
link local multicast but that doesn&#39;t mean it is the best way to do<br>
everything.<br></blockquote><div><br></div><div>In my mind, the best way to=
 perform discovery is to combine unicast</div><div>and link-local multicast=
. That&#39;s what we use in DNSSD which is AFAIK</div><div>the IETF-recomme=
nded way to perform service discovery.</div><div><br></div><div>David</div>=
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
Thanks,<br>
Donald<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
=C2=A0Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br>
=C2=A02386 Panoramic Circle, Apopka, FL 32703 USA<br>
=C2=A0<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.co=
m</a><br>
<br>
&gt; David<br>
&gt;<br>
&gt; On Tue, May 25, 2021 at 11:25 AM Donald Eastlake &lt;<a href=3D"mailto=
:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi Juliusz,<br>
&gt;&gt;<br>
&gt;&gt; On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek &lt;<a href=3D=
"mailto:jch@irif.fr" target=3D"_blank">jch@irif.fr</a>&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Hi Donald,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt; So, I plan to add the following two milestones (I believ=
e new milestones need<br>
&gt;&gt; &gt; &gt; to be OKed by our AD):<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0June 2021=C2=A0 =C2=A0IESG submission of IPv=
4 via IPv6.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Donald, I&#39;d like to expand the introduction to this docum=
ent before it is<br>
&gt;&gt; &gt; submitted to the IESG -- no content changes, just wording.=C2=
=A0 Is it possible<br>
&gt;&gt; &gt; to do that without restarting last call?<br>
&gt;&gt;<br>
&gt;&gt; Probably. The Introduction does not seem to be controversial. I<br=
>
&gt;&gt; suggested a change to the Introduction here<br>
&gt;&gt; <a href=3D"https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxne=
rhhq9rZcy92hjfwI/" rel=3D"noreferrer" target=3D"_blank">https://mailarchive=
.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/</a><br>
&gt;&gt; and there were no complaints. You could propose a different change=
 to<br>
&gt;&gt; the Introduction as a resolution to my comment. Since all this is<=
br>
&gt;&gt; getting posted to the WG mailing list, if no one speaks up in 7 or=
 8<br>
&gt;&gt; days and there are no technical changes to the protocol, I don&#39=
;t think<br>
&gt;&gt; we would need a new WG Last Call.<br>
&gt;&gt;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0Sept 2021=C2=A0 =C2=A0WG adoption of a Babel=
 multicast draft.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; What do you envision?<br>
&gt;&gt;<br>
&gt;&gt; Multicast is mentioned in the Babel WG Charter as something option=
al<br>
&gt;&gt; to work on. This is just my personal opinion but a routing system =
that<br>
&gt;&gt; doesn&#39;t handle both unicast and multicast seems incomplete to =
me.<br>
&gt;&gt;<br>
&gt;&gt; &gt; Babeld works with PIM-SM (that&#39;s what the<br>
&gt;&gt; &gt; &quot;reflect-kernel-metric&quot; option is for), but I&#39;m=
 not seeing a lot of<br>
&gt;&gt; &gt; interest.<br>
&gt;&gt;<br>
&gt;&gt; Is this discussed in any of the Babel RFCs or drafts? Seems like<b=
r>
&gt;&gt; something somewhere in the IETF Babel documentation should talk ab=
out<br>
&gt;&gt; at least a way to do multicast.<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Donald<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br=
>
&gt;&gt;=C2=A0 2386 Panoramic Circle, Apopka, FL 32703 USA<br>
&gt;&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3=
@gmail.com</a><br>
&gt;&gt;<br>
&gt;&gt; &gt; I&#39;m not following the DNSSD/mDNS community closely, but I=
&#39;m<br>
&gt;&gt; &gt; under the impression that they&#39;re focusing on multicast-t=
o-unicast proxies<br>
&gt;&gt; &gt; instead of site-local multicast (draft-cheshire-mdnsext-hybri=
d).<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; There&#39;s also Sandy&#39;s BIER for Babel work, but I fear =
it may have been<br>
&gt;&gt; &gt; abandoned.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt; Perhaps the Babel WG meeting at the July IETF meeting (J=
uly 26-30)<br>
&gt;&gt; &gt; &gt; should focus on multicast.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; My personal plans are to finish merging HMAC and v4-via-v6 in=
to babeld<br>
&gt;&gt; &gt; mainline, and then to get back to working on network-layer mo=
bility:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;=C2=A0 =C2=A0<a href=3D"https://www.irif.fr/~jch/software/sroa=
md.git" rel=3D"noreferrer" target=3D"_blank">https://www.irif.fr/~jch/softw=
are/sroamd.git</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; -- Juliusz<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; babel mailing list<br>
&gt;&gt; <a href=3D"mailto:babel@ietf.org" target=3D"_blank">babel@ietf.org=
</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/babel" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/babel</a><=
br>
</blockquote></div></div>

--000000000000a8319705c33ffe80--


From nobody Thu May 27 06:54:12 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAC523A0D02 for <babel@ietfa.amsl.com>; Thu, 27 May 2021 06:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 sjYQZsMX4OX5 for <babel@ietfa.amsl.com>; Thu, 27 May 2021 06:54:05 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 2D21C3A0D01 for <babel@ietf.org>; Thu, 27 May 2021 06:54:05 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id k4so316701ili.4 for <babel@ietf.org>; Thu, 27 May 2021 06:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y7SkeLiYCnXmc99iQjxXVQiVFUPt3L3bXUzYc/CvY70=; b=aoyQcyAEbLaqYR79VAagpRiTuuaPRUPucTJ3zWwyNB/qfcqWnD+LhsEpjDcM5Nb9MF b7s1NuRKRNcZYyiULVgRDEdlJxi4Y4i1lkLQkPXaBq58oA4fT5ZjuwZZBJLEvupmrJ0B 8BEo2lCcpglggXmugG26XpLajbVcII4mvccQ0z1phRJzeXA1flHgvjoZ8ODqyVj7MuRY /rFtDmXharbsp81ZVjN/TS5OquQla5aJtJIH/af1R+vf0hIePeOGxSk8geU5lQVFKVPJ UbIVfXijSy5fuTXn9NSSu8+HG6a7PnHDmrr/RWNY6yfOo7OSz+4G/sMrrY+d0Dz/PRtY L62A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y7SkeLiYCnXmc99iQjxXVQiVFUPt3L3bXUzYc/CvY70=; b=NePQ95uwhd7+3vz/RNtlgQl/X0YlZnaXzU0IrAEod2+f+lRMr8tXsZfkHdpRMbQ9le AyyNSery3YHv7/Zf2yh4HxmjswxZd8yMwRlwD9RJMmgaxUskPud+Dn7iKkcpogVxrdBX zKuap8PDYHOEC4KvmkZ4hpmZJg4mIEkuVi5DVGEgehLd4ffyl7Aa6CDJtv9Xc48PBDel 46eAnuH2k6f1qlXOqhcAy9Iol+ghUdSF28JpRXsRrGBVx3xt/QVbb0ivmTpPOpM9q6BV CttoAH0rkq0ppvKXOLvxmNJe/K47AtcSey6mnhAOQhfF8zHVWHvZBWyAKYzVlFJ9PTH0 /W8w==
X-Gm-Message-State: AOAM533mMrG/WRyuu1QSc0/fLDpysbWb3zuJsKaDyX/HvnI8Nyic/Vxq 9F/P81IOIf5AP+ui9UIqFLT2SJm6fG9pqzgPnAo=
X-Google-Smtp-Source: ABdhPJyCEkzuYGQ6Ilr0OdrS8hEq3PKRfOCCT2Cji0wqgLykCqLeEqOnigkxV7JqkqhKKyFclwfQN9K6Q5pntO0V4xA=
X-Received: by 2002:a92:6b05:: with SMTP id g5mr3093665ilc.40.1622123643536; Thu, 27 May 2021 06:54:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com> <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com>
In-Reply-To: <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 May 2021 09:53:52 -0400
Message-ID: <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/9ZU_iuR4PTAChnAAYV96azpQGCU>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 13:54:10 -0000

Hi David,

On Wed, May 26, 2021 at 2:41 PM David Schinazi <dschinazi.ietf@gmail.com> wrote:
>
> On Tue, May 25, 2021 at 9:02 PM Donald Eastlake <d3e3e3@gmail.com> wrote:
>>
>> Hi David,
>>
>> On Tue, May 25, 2021 at 8:24 PM David Schinazi <dschinazi.ietf@gmail.com> wrote:
>> >
>> > Adding "IESG submission of IPv4 via IPv6" as a
>> > milestone is fine by me, because we're about to do that
>> > anyway. I've never found milestones to be useful, so
>> > I'm not sure there's any benefit in doing this as opposed
>> > to just submitting the draft for publication.
>>
>> I think milestones give an idea of what the WG has accomplished or may
>> accomplish in the future. They sort of supplement the Charter. But I'm
>> willing to admit that the "IESG submission of IPv4 via IPv6" doesn't
>> add that much. On the other hand, it's mostly the Chairs doing the
>> work to modify/track the set of milestones.
>
> To clarify, I don't object to the chairs creating a
> "IESG submission of IPv4 via IPv6" milestone.

OK.

>> ...
>>
>> > Regarding the "WG adoption of a Babel multicast draft"
>> > milestone, I would personally like to see such a draft
>> > written and discussed at a WG meeting before a
>> > milestone is added. That would ensure that we have folks
>> > willing to do the work for this to happen.
>>
>> I don't see why a milestone can't be aspirational.
>
> Does the aspiration reflect WG consensus? My understanding
> is that we're a very implementation-driven WG, and I'd prefer to
> have aspirations reflect what implementers aspire to build.
> Alternatively, hearing from someone who runs a Babel network
> telling us that they have a need for multicast would also be great.

No consensus call has been made.

>> > I disagree with Donald's statement that "a routing system that
>> > doesn't handle both unicast and multicast seems incomplete",
>> > because I have yet to find a general-purpose use-case for
>> > non-link-local multicast whereas unicast is general-purpose :-)
>>
>> What makes one use "general" and another "special"?
>
> I'd say "general-purpose" means there are several applications using
> it, whereas "special-purpose" is for a single application.

See below for a couple of applications.

>> What is a "link"? Say you have a network of Babel routers. Some
>> communicate by radio where the transmission on one of its radios by a
>> router may be received by zero, one, or more other routers. Some
>> communicate by wire/Ethernet but some of those connections are bridged
>> so those inter-router connections are more stable but can be
>> bi-lateral or multilateral. What exactly is a link in this network?
>
> My personal definition is: two devices are on the same link if they can
> hear each other's Babel Hellos and IHUs.

Ahhh, so you meant a Babel link.

>> I tend to think of multicast as being either discovery multicast or
>> application multicast. For application multicast, generally you can
>> use head end replication and unicast which is less efficient in terms
>> of link utilization and generally has higher latency due to multiple
>> copies being sent on a link but might be simpler; on the other hand,
>> if there are lots of sources and multicast groups, these head ends
>> have to all keep track of who to unicast to. For discovery, you can't
>> do everything with unicast because, by definition, you want to be able
>> to find nodes that you don't know about yet; but you can probably get
>> away with unicast + link local multicast for some definition of link.
>> So I agree you can find some way to do everything with unicast and
>> link local multicast but that doesn't mean it is the best way to do
>> everything.
>
> In my mind, the best way to perform discovery is to combine unicast
> and link-local multicast. That's what we use in DNSSD which is AFAIK
> the IETF-recommended way to perform service discovery.

OK for discovery although I'm not aware of anything that explicitly
states that that is an IETF recommendation.

 Here are the first two application multicast uses that come to mind:

Say you have a provider network with multiple tenants attached.
Multicast packets arriving from a tenant need to be sent out to other
islands of that tenant connected to your provider network. I don't
want to get too bogged down in details of topology and optimizations
and stuff but I think that some form of tree distribution is needed to
scale. Interconnecting pieces of the same VLAN is similar. 802.1
bridging and TRILL routing are examples of complete packet forwarding
systems that handle unicast and multicast and build such distribution
trees.

Another application is streaming media. IP-TV in access networks
pretty much always uses multicast.


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

> David
>
>> Thanks,
>> Donald
>> =============================
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  2386 Panoramic Circle, Apopka, FL 32703 USA
>>  d3e3e3@gmail.com
>>
>> > David
>> >
>> > On Tue, May 25, 2021 at 11:25 AM Donald Eastlake <d3e3e3@gmail.com> wrote:
>> >>
>> >> Hi Juliusz,
>> >>
>> >> On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>> >> >
>> >> > Hi Donald,
>> >> >
>> >> > > So, I plan to add the following two milestones (I believe new milestones need
>> >> > > to be OKed by our AD):
>> >> > >
>> >> > >   June 2021   IESG submission of IPv4 via IPv6.
>> >> >
>> >> > Donald, I'd like to expand the introduction to this document before it is
>> >> > submitted to the IESG -- no content changes, just wording.  Is it possible
>> >> > to do that without restarting last call?
>> >>
>> >> Probably. The Introduction does not seem to be controversial. I
>> >> suggested a change to the Introduction here
>> >> https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
>> >> and there were no complaints. You could propose a different change to
>> >> the Introduction as a resolution to my comment. Since all this is
>> >> getting posted to the WG mailing list, if no one speaks up in 7 or 8
>> >> days and there are no technical changes to the protocol, I don't think
>> >> we would need a new WG Last Call.
>> >>
>> >> > >   Sept 2021   WG adoption of a Babel multicast draft.
>> >> >
>> >> > What do you envision?
>> >>
>> >> Multicast is mentioned in the Babel WG Charter as something optional
>> >> to work on. This is just my personal opinion but a routing system that
>> >> doesn't handle both unicast and multicast seems incomplete to me.
>> >>
>> >> > Babeld works with PIM-SM (that's what the
>> >> > "reflect-kernel-metric" option is for), but I'm not seeing a lot of
>> >> > interest.
>> >>
>> >> Is this discussed in any of the Babel RFCs or drafts? Seems like
>> >> something somewhere in the IETF Babel documentation should talk about
>> >> at least a way to do multicast.
>> >>
>> >> Thanks,
>> >> Donald
>> >> ===============================
>> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>> >>  2386 Panoramic Circle, Apopka, FL 32703 USA
>> >>  d3e3e3@gmail.com
>> >>
>> >> > I'm not following the DNSSD/mDNS community closely, but I'm
>> >> > under the impression that they're focusing on multicast-to-unicast proxies
>> >> > instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
>> >> >
>> >> > There's also Sandy's BIER for Babel work, but I fear it may have been
>> >> > abandoned.
>> >> >
>> >> > > Perhaps the Babel WG meeting at the July IETF meeting (July 26-30)
>> >> > > should focus on multicast.
>> >> >
>> >> > My personal plans are to finish merging HMAC and v4-via-v6 into babeld
>> >> > mainline, and then to get back to working on network-layer mobility:
>> >> >
>> >> >   https://www.irif.fr/~jch/software/sroamd.git
>> >> >
>> >> > -- Juliusz


From nobody Thu May 27 08:36:31 2021
Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41423A138D for <babel@ietfa.amsl.com>; Thu, 27 May 2021 08:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 gWIGTNR3aufv for <babel@ietfa.amsl.com>; Thu, 27 May 2021 08:36:22 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 A42CB3A138A for <babel@ietf.org>; Thu, 27 May 2021 08:36:22 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id f8so707592pjh.0 for <babel@ietf.org>; Thu, 27 May 2021 08:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=H/T8DMoVj2ekgphEYjv8BjpItm1DVAi8rNtbUiIM74o=; b=hIxzTLBzvATVmGdldTjejZ86bEkpVsAziV3DdaGZTamaFD0+bM2Fc0YsrM1/1lrg6H MtTbJ7rgBtyj5bLD8Ve83M4z/OpC91h7qsigO6ICQJocna0LMshe2VH9J3tLAF0MLcpR s3Bc+f0m6QptJJpoOF/Qc+0noHQBj0LssNQOQx1p8lxQCYUx6mcfDHQtAZCm56n1gEhn tcXYVu2XklkQ96RrOQRsnwhuPfb8jp7F0zPz+KOyvKt7VLh5RlynKyKRUZBWAW43oT8B L48L+yMVZFP0HG/+30/5XUTu+4Ehpx8tmpc63+g84s0CUD9WVSV7QG3wIIJok95z+b87 ODqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H/T8DMoVj2ekgphEYjv8BjpItm1DVAi8rNtbUiIM74o=; b=ZsBGGLG/cIVd6RrUC8DLodlN8F62X1BY+e6tabV6TZGBl7YfMsaVwnV2Mxqmnaefhe bGPno107vz3zl4nw9FJY0q+ltPYRpuQ1kK4qTPUYOEdYb/hBqFBFkTbi8H4z7hD2PEBx 1ZIu4f5RDFq2Y00utCaqNJ11ppyX32a6nrSetz4fEvksL3b+LdO5XAlEj0vbixU14n0j JpAjb6pw+uf6pgFq+7Ge9J/wcug6Q3rYSTHVD3YCYTmygoq/IDkPPIjlc9V9KywLNII8 fQNmMd2tZeUoDRbcyNWxyTTUF8FpXm/UmiAvTKRdNgcBe/3oUc9o52xjBMqsWHsu/BJe 4vIw==
X-Gm-Message-State: AOAM531fcV9xazeJ4hg9hYgfx0JhM8rm3jEJLs2RGwI8d4cR8XkA58A/ FUGrru/oC6vjHN1Jnqw6T0jSMcvEJ5ajxl8pWc4=
X-Google-Smtp-Source: ABdhPJzSxbrX6xjksPR9hSDOTcLkOcgfkIev571Q2U1ubxGtGgd1hyPSDPtgqr0K8/EUkJdnBKWF9Rv1ZNg+Y803oBw=
X-Received: by 2002:a17:90b:3905:: with SMTP id ob5mr9972822pjb.94.1622129781644;  Thu, 27 May 2021 08:36:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com> <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com> <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com>
In-Reply-To: <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 27 May 2021 08:36:10 -0700
Message-ID: <CAPDSy+7rnxrZDkfUzRGsyaj+RUFxBEyDubETrzx5huFSb3eUxw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a201505c3518505"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/utkvq40vkl-wYyLg6WUF-ru_asA>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 15:36:27 -0000

--0000000000006a201505c3518505
Content-Type: text/plain; charset="UTF-8"

On Thu, May 27, 2021 at 6:54 AM Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi David,
>
> On Wed, May 26, 2021 at 2:41 PM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
> >
> > On Tue, May 25, 2021 at 9:02 PM Donald Eastlake <d3e3e3@gmail.com>
> wrote:
> >>
> >> Hi David,
> >>
> >> On Tue, May 25, 2021 at 8:24 PM David Schinazi <
> dschinazi.ietf@gmail.com> wrote:
> >> >
> >> > Adding "IESG submission of IPv4 via IPv6" as a
> >> > milestone is fine by me, because we're about to do that
> >> > anyway. I've never found milestones to be useful, so
> >> > I'm not sure there's any benefit in doing this as opposed
> >> > to just submitting the draft for publication.
> >>
> >> I think milestones give an idea of what the WG has accomplished or may
> >> accomplish in the future. They sort of supplement the Charter. But I'm
> >> willing to admit that the "IESG submission of IPv4 via IPv6" doesn't
> >> add that much. On the other hand, it's mostly the Chairs doing the
> >> work to modify/track the set of milestones.
> >
> > To clarify, I don't object to the chairs creating a
> > "IESG submission of IPv4 via IPv6" milestone.
>
> OK.
>
> >> ...
> >>
> >> > Regarding the "WG adoption of a Babel multicast draft"
> >> > milestone, I would personally like to see such a draft
> >> > written and discussed at a WG meeting before a
> >> > milestone is added. That would ensure that we have folks
> >> > willing to do the work for this to happen.
> >>
> >> I don't see why a milestone can't be aspirational.
> >
> > Does the aspiration reflect WG consensus? My understanding
> > is that we're a very implementation-driven WG, and I'd prefer to
> > have aspirations reflect what implementers aspire to build.
> > Alternatively, hearing from someone who runs a Babel network
> > telling us that they have a need for multicast would also be great.
>
> No consensus call has been made.
>
> >> > I disagree with Donald's statement that "a routing system that
> >> > doesn't handle both unicast and multicast seems incomplete",
> >> > because I have yet to find a general-purpose use-case for
> >> > non-link-local multicast whereas unicast is general-purpose :-)
> >>
> >> What makes one use "general" and another "special"?
> >
> > I'd say "general-purpose" means there are several applications using
> > it, whereas "special-purpose" is for a single application.
>
> See below for a couple of applications.
>
> >> What is a "link"? Say you have a network of Babel routers. Some
> >> communicate by radio where the transmission on one of its radios by a
> >> router may be received by zero, one, or more other routers. Some
> >> communicate by wire/Ethernet but some of those connections are bridged
> >> so those inter-router connections are more stable but can be
> >> bi-lateral or multilateral. What exactly is a link in this network?
> >
> > My personal definition is: two devices are on the same link if they can
> > hear each other's Babel Hellos and IHUs.
>
> Ahhh, so you meant a Babel link.
>
> >> I tend to think of multicast as being either discovery multicast or
> >> application multicast. For application multicast, generally you can
> >> use head end replication and unicast which is less efficient in terms
> >> of link utilization and generally has higher latency due to multiple
> >> copies being sent on a link but might be simpler; on the other hand,
> >> if there are lots of sources and multicast groups, these head ends
> >> have to all keep track of who to unicast to. For discovery, you can't
> >> do everything with unicast because, by definition, you want to be able
> >> to find nodes that you don't know about yet; but you can probably get
> >> away with unicast + link local multicast for some definition of link.
> >> So I agree you can find some way to do everything with unicast and
> >> link local multicast but that doesn't mean it is the best way to do
> >> everything.
> >
> > In my mind, the best way to perform discovery is to combine unicast
> > and link-local multicast. That's what we use in DNSSD which is AFAIK
> > the IETF-recommended way to perform service discovery.
>
> OK for discovery although I'm not aware of anything that explicitly
> states that that is an IETF recommendation.
>
>  Here are the first two application multicast uses that come to mind:
>
> Say you have a provider network with multiple tenants attached.
> Multicast packets arriving from a tenant need to be sent out to other
> islands of that tenant connected to your provider network. I don't
> want to get too bogged down in details of topology and optimizations
> and stuff but I think that some form of tree distribution is needed to
> scale. Interconnecting pieces of the same VLAN is similar. 802.1
> bridging and TRILL routing are examples of complete packet forwarding
> systems that handle unicast and multicast and build such distribution
> trees.
>

In this example, what's the application? What application data are the
multicast packets arriving from a tenant carrying?

Another application is streaming media. IP-TV in access networks
> pretty much always uses multicast.
>

Definitely agree with this example, I think it's the main use of
non-link-local
multicast on the Internet today.

All this said, if you really want to add the milestone, I'll back off. I'm
just
commenting that this would be the first milestone we have that wasn't
backed by support from implementers of Babel.

Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
> > David
> >
> >> Thanks,
> >> Donald
> >> =============================
> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >>  2386 Panoramic Circle, Apopka, FL 32703 USA
> >>  d3e3e3@gmail.com
> >>
> >> > David
> >> >
> >> > On Tue, May 25, 2021 at 11:25 AM Donald Eastlake <d3e3e3@gmail.com>
> wrote:
> >> >>
> >> >> Hi Juliusz,
> >> >>
> >> >> On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek <jch@irif.fr>
> wrote:
> >> >> >
> >> >> > Hi Donald,
> >> >> >
> >> >> > > So, I plan to add the following two milestones (I believe new
> milestones need
> >> >> > > to be OKed by our AD):
> >> >> > >
> >> >> > >   June 2021   IESG submission of IPv4 via IPv6.
> >> >> >
> >> >> > Donald, I'd like to expand the introduction to this document
> before it is
> >> >> > submitted to the IESG -- no content changes, just wording.  Is it
> possible
> >> >> > to do that without restarting last call?
> >> >>
> >> >> Probably. The Introduction does not seem to be controversial. I
> >> >> suggested a change to the Introduction here
> >> >>
> https://mailarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/
> >> >> and there were no complaints. You could propose a different change to
> >> >> the Introduction as a resolution to my comment. Since all this is
> >> >> getting posted to the WG mailing list, if no one speaks up in 7 or 8
> >> >> days and there are no technical changes to the protocol, I don't
> think
> >> >> we would need a new WG Last Call.
> >> >>
> >> >> > >   Sept 2021   WG adoption of a Babel multicast draft.
> >> >> >
> >> >> > What do you envision?
> >> >>
> >> >> Multicast is mentioned in the Babel WG Charter as something optional
> >> >> to work on. This is just my personal opinion but a routing system
> that
> >> >> doesn't handle both unicast and multicast seems incomplete to me.
> >> >>
> >> >> > Babeld works with PIM-SM (that's what the
> >> >> > "reflect-kernel-metric" option is for), but I'm not seeing a lot of
> >> >> > interest.
> >> >>
> >> >> Is this discussed in any of the Babel RFCs or drafts? Seems like
> >> >> something somewhere in the IETF Babel documentation should talk about
> >> >> at least a way to do multicast.
> >> >>
> >> >> Thanks,
> >> >> Donald
> >> >> ===============================
> >> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >> >>  2386 Panoramic Circle, Apopka, FL 32703 USA
> >> >>  d3e3e3@gmail.com
> >> >>
> >> >> > I'm not following the DNSSD/mDNS community closely, but I'm
> >> >> > under the impression that they're focusing on multicast-to-unicast
> proxies
> >> >> > instead of site-local multicast (draft-cheshire-mdnsext-hybrid).
> >> >> >
> >> >> > There's also Sandy's BIER for Babel work, but I fear it may have
> been
> >> >> > abandoned.
> >> >> >
> >> >> > > Perhaps the Babel WG meeting at the July IETF meeting (July
> 26-30)
> >> >> > > should focus on multicast.
> >> >> >
> >> >> > My personal plans are to finish merging HMAC and v4-via-v6 into
> babeld
> >> >> > mainline, and then to get back to working on network-layer
> mobility:
> >> >> >
> >> >> >   https://www.irif.fr/~jch/software/sroamd.git
> >> >> >
> >> >> > -- Juliusz
>

--0000000000006a201505c3518505
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 27, 2021 at 6:54 AM Donal=
d Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi David=
,<br>
<br>
On Wed, May 26, 2021 at 2:41 PM David Schinazi &lt;<a href=3D"mailto:dschin=
azi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt; wrot=
e:<br>
&gt;<br>
&gt; On Tue, May 25, 2021 at 9:02 PM Donald Eastlake &lt;<a href=3D"mailto:=
d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi David,<br>
&gt;&gt;<br>
&gt;&gt; On Tue, May 25, 2021 at 8:24 PM David Schinazi &lt;<a href=3D"mail=
to:dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>=
&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Adding &quot;IESG submission of IPv4 via IPv6&quot; as a<br>
&gt;&gt; &gt; milestone is fine by me, because we&#39;re about to do that<b=
r>
&gt;&gt; &gt; anyway. I&#39;ve never found milestones to be useful, so<br>
&gt;&gt; &gt; I&#39;m not sure there&#39;s any benefit in doing this as opp=
osed<br>
&gt;&gt; &gt; to just submitting the draft for publication.<br>
&gt;&gt;<br>
&gt;&gt; I think milestones give an idea of what the WG has accomplished or=
 may<br>
&gt;&gt; accomplish in the future. They sort of supplement the Charter. But=
 I&#39;m<br>
&gt;&gt; willing to admit that the &quot;IESG submission of IPv4 via IPv6&q=
uot; doesn&#39;t<br>
&gt;&gt; add that much. On the other hand, it&#39;s mostly the Chairs doing=
 the<br>
&gt;&gt; work to modify/track the set of milestones.<br>
&gt;<br>
&gt; To clarify, I don&#39;t object to the chairs creating a<br>
&gt; &quot;IESG submission of IPv4 via IPv6&quot; milestone.<br>
<br>
OK.<br>
<br>
&gt;&gt; ...<br>
&gt;&gt;<br>
&gt;&gt; &gt; Regarding the &quot;WG adoption of a Babel multicast draft&qu=
ot;<br>
&gt;&gt; &gt; milestone, I would personally like to see such a draft<br>
&gt;&gt; &gt; written and discussed at a WG meeting before a<br>
&gt;&gt; &gt; milestone is added. That would ensure that we have folks<br>
&gt;&gt; &gt; willing to do the work for this to happen.<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t see why a milestone can&#39;t be aspirational.<br>
&gt;<br>
&gt; Does the aspiration reflect WG consensus? My understanding<br>
&gt; is that we&#39;re a very implementation-driven WG, and I&#39;d prefer =
to<br>
&gt; have aspirations reflect what implementers aspire to build.<br>
&gt; Alternatively, hearing from someone who runs a Babel network<br>
&gt; telling us that they have a need for multicast would also be great.<br=
>
<br>
No consensus call has been made.<br>
<br>
&gt;&gt; &gt; I disagree with Donald&#39;s statement that &quot;a routing s=
ystem that<br>
&gt;&gt; &gt; doesn&#39;t handle both unicast and multicast seems incomplet=
e&quot;,<br>
&gt;&gt; &gt; because I have yet to find a general-purpose use-case for<br>
&gt;&gt; &gt; non-link-local multicast whereas unicast is general-purpose :=
-)<br>
&gt;&gt;<br>
&gt;&gt; What makes one use &quot;general&quot; and another &quot;special&q=
uot;?<br>
&gt;<br>
&gt; I&#39;d say &quot;general-purpose&quot; means there are several applic=
ations using<br>
&gt; it, whereas &quot;special-purpose&quot; is for a single application.<b=
r>
<br>
See below for a couple of applications.<br>
<br>
&gt;&gt; What is a &quot;link&quot;? Say you have a network of Babel router=
s. Some<br>
&gt;&gt; communicate by radio where the transmission on one of its radios b=
y a<br>
&gt;&gt; router may be received by zero, one, or more other routers. Some<b=
r>
&gt;&gt; communicate by wire/Ethernet but some of those connections are bri=
dged<br>
&gt;&gt; so those inter-router connections are more stable but can be<br>
&gt;&gt; bi-lateral or multilateral. What exactly is a link in this network=
?<br>
&gt;<br>
&gt; My personal definition is: two devices are on the same link if they ca=
n<br>
&gt; hear each other&#39;s Babel Hellos and IHUs.<br>
<br>
Ahhh, so you meant a Babel link.<br>
<br>
&gt;&gt; I tend to think of multicast as being either discovery multicast o=
r<br>
&gt;&gt; application multicast. For application multicast, generally you ca=
n<br>
&gt;&gt; use head end replication and unicast which is less efficient in te=
rms<br>
&gt;&gt; of link utilization and generally has higher latency due to multip=
le<br>
&gt;&gt; copies being sent on a link but might be simpler; on the other han=
d,<br>
&gt;&gt; if there are lots of sources and multicast groups, these head ends=
<br>
&gt;&gt; have to all keep track of who to unicast to. For discovery, you ca=
n&#39;t<br>
&gt;&gt; do everything with unicast because, by definition, you want to be =
able<br>
&gt;&gt; to find nodes that you don&#39;t know about yet; but you can proba=
bly get<br>
&gt;&gt; away with unicast + link local multicast for some definition of li=
nk.<br>
&gt;&gt; So I agree you can find some way to do everything with unicast and=
<br>
&gt;&gt; link local multicast but that doesn&#39;t mean it is the best way =
to do<br>
&gt;&gt; everything.<br>
&gt;<br>
&gt; In my mind, the best way to perform discovery is to combine unicast<br=
>
&gt; and link-local multicast. That&#39;s what we use in DNSSD which is AFA=
IK<br>
&gt; the IETF-recommended way to perform service discovery.<br>
<br>
OK for discovery although I&#39;m not aware of anything that explicitly<br>
states that that is an IETF recommendation.<br>
<br>
=C2=A0Here are the first two application multicast uses that come to mind:<=
br>
<br>
Say you have a provider network with multiple tenants attached.<br>
Multicast packets arriving from a tenant need to be sent out to other<br>
islands of that tenant connected to your provider network. I don&#39;t<br>
want to get too bogged down in details of topology and optimizations<br>
and stuff but I think that some form of tree distribution is needed to<br>
scale. Interconnecting pieces of the same VLAN is similar. 802.1<br>
bridging and TRILL routing are examples of complete packet forwarding<br>
systems that handle unicast and multicast and build such distribution<br>
trees.<br></blockquote><div><br></div><div>In this example, what&#39;s the =
application? What application data are the</div><div>multicast packets arri=
ving from a tenant carrying?</div><div><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
Another application is streaming media. IP-TV in access networks<br>
pretty much always uses multicast.<br></blockquote><div><br></div><div>Defi=
nitely agree with this example, I think it&#39;s the main use of non-link-l=
ocal</div><div>multicast on the Internet today.</div><div><br></div><div>Al=
l this said, if you really want to add the milestone, I&#39;ll back off. I&=
#39;m just</div><div>commenting that this would be the first milestone we h=
ave that wasn&#39;t</div><div>backed by support from implementers=C2=A0of B=
abel.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
Thanks,<br>
Donald<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>
=C2=A0Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br>
=C2=A02386 Panoramic Circle, Apopka, FL 32703 USA<br>
=C2=A0<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.co=
m</a><br>
<br>
&gt; David<br>
&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Donald<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br=
>
&gt;&gt;=C2=A0 2386 Panoramic Circle, Apopka, FL 32703 USA<br>
&gt;&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3=
@gmail.com</a><br>
&gt;&gt;<br>
&gt;&gt; &gt; David<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; On Tue, May 25, 2021 at 11:25 AM Donald Eastlake &lt;<a href=
=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>&gt; wro=
te:<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Hi Juliusz,<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; On Tue, May 25, 2021 at 11:03 AM Juliusz Chroboczek &lt;<=
a href=3D"mailto:jch@irif.fr" target=3D"_blank">jch@irif.fr</a>&gt; wrote:<=
br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; Hi Donald,<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; &gt; So, I plan to add the following two milestones =
(I believe new milestones need<br>
&gt;&gt; &gt;&gt; &gt; &gt; to be OKed by our AD):<br>
&gt;&gt; &gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; &gt;=C2=A0 =C2=A0June 2021=C2=A0 =C2=A0IESG submissi=
on of IPv4 via IPv6.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; Donald, I&#39;d like to expand the introduction to t=
his document before it is<br>
&gt;&gt; &gt;&gt; &gt; submitted to the IESG -- no content changes, just wo=
rding.=C2=A0 Is it possible<br>
&gt;&gt; &gt;&gt; &gt; to do that without restarting last call?<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Probably. The Introduction does not seem to be controvers=
ial. I<br>
&gt;&gt; &gt;&gt; suggested a change to the Introduction here<br>
&gt;&gt; &gt;&gt; <a href=3D"https://mailarchive.ietf.org/arch/msg/babel/5H=
EAHOesxnerhhq9rZcy92hjfwI/" rel=3D"noreferrer" target=3D"_blank">https://ma=
ilarchive.ietf.org/arch/msg/babel/5HEAHOesxnerhhq9rZcy92hjfwI/</a><br>
&gt;&gt; &gt;&gt; and there were no complaints. You could propose a differe=
nt change to<br>
&gt;&gt; &gt;&gt; the Introduction as a resolution to my comment. Since all=
 this is<br>
&gt;&gt; &gt;&gt; getting posted to the WG mailing list, if no one speaks u=
p in 7 or 8<br>
&gt;&gt; &gt;&gt; days and there are no technical changes to the protocol, =
I don&#39;t think<br>
&gt;&gt; &gt;&gt; we would need a new WG Last Call.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; &gt; &gt;=C2=A0 =C2=A0Sept 2021=C2=A0 =C2=A0WG adoption o=
f a Babel multicast draft.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; What do you envision?<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Multicast is mentioned in the Babel WG Charter as somethi=
ng optional<br>
&gt;&gt; &gt;&gt; to work on. This is just my personal opinion but a routin=
g system that<br>
&gt;&gt; &gt;&gt; doesn&#39;t handle both unicast and multicast seems incom=
plete to me.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; &gt; Babeld works with PIM-SM (that&#39;s what the<br>
&gt;&gt; &gt;&gt; &gt; &quot;reflect-kernel-metric&quot; option is for), bu=
t I&#39;m not seeing a lot of<br>
&gt;&gt; &gt;&gt; &gt; interest.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Is this discussed in any of the Babel RFCs or drafts? See=
ms like<br>
&gt;&gt; &gt;&gt; something somewhere in the IETF Babel documentation shoul=
d talk about<br>
&gt;&gt; &gt;&gt; at least a way to do multicast.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Thanks,<br>
&gt;&gt; &gt;&gt; Donald<br>
&gt;&gt; &gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt; &gt;&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 =
(cell)<br>
&gt;&gt; &gt;&gt;=C2=A0 2386 Panoramic Circle, Apopka, FL 32703 USA<br>
&gt;&gt; &gt;&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blan=
k">d3e3e3@gmail.com</a><br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; &gt; I&#39;m not following the DNSSD/mDNS community close=
ly, but I&#39;m<br>
&gt;&gt; &gt;&gt; &gt; under the impression that they&#39;re focusing on mu=
lticast-to-unicast proxies<br>
&gt;&gt; &gt;&gt; &gt; instead of site-local multicast (draft-cheshire-mdns=
ext-hybrid).<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; There&#39;s also Sandy&#39;s BIER for Babel work, bu=
t I fear it may have been<br>
&gt;&gt; &gt;&gt; &gt; abandoned.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; &gt; Perhaps the Babel WG meeting at the July IETF m=
eeting (July 26-30)<br>
&gt;&gt; &gt;&gt; &gt; &gt; should focus on multicast.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; My personal plans are to finish merging HMAC and v4-=
via-v6 into babeld<br>
&gt;&gt; &gt;&gt; &gt; mainline, and then to get back to working on network=
-layer mobility:<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt;=C2=A0 =C2=A0<a href=3D"https://www.irif.fr/~jch/soft=
ware/sroamd.git" rel=3D"noreferrer" target=3D"_blank">https://www.irif.fr/~=
jch/software/sroamd.git</a><br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; -- Juliusz<br>
</blockquote></div></div>

--0000000000006a201505c3518505--


From nobody Thu May 27 09:20:52 2021
Return-Path: <toke@toke.dk>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8163A1591 for <babel@ietfa.amsl.com>; Thu, 27 May 2021 09:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=toke.dk
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 2SrJgXAhauQa for <babel@ietfa.amsl.com>; Thu, 27 May 2021 09:20:34 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDE043A158B for <babel@ietf.org>; Thu, 27 May 2021 09:20:33 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1622132425; bh=00/y1leFI4l9EVtSxUqF0ghO4q9VOn1nIHwsYCfO04k=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=LzeV2AD5eYedHRxQh+B5YKrQ3OiGijAwtMzvxMyiBJXUQ/6EYWUpy5zZHZTMEwym+ Ap/9YOx8u5n48o8h5r3vtzFUXMOE+RGYNlzz0IblcasUvRO/0WTodMHnac/zbP82So XF1Gs5/EYML8lMxT4KBkYxB7A6ot/FBu30dCeOjJkUTfCCkjsUn8xvXa7dQ88UrnT6 g5S8QgeOsNpvtyOn3j7cyv22iet3H1zooPNPT2tXa1U/0OChiXpJiux7WDJOU2EkqH NGdziGfpebJQ2aqx/VGQTpjKd6cJuRhhdz+3iMdIzi2KYnOYa/dKujKAZ0tIQnk4jq xryxahFhRITbA==
To: David Schinazi <dschinazi.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>
Cc: Babel at IETF <babel@ietf.org>, Juliusz Chroboczek <jch@irif.fr>
In-Reply-To: <CAPDSy+7rnxrZDkfUzRGsyaj+RUFxBEyDubETrzx5huFSb3eUxw@mail.gmail.com>
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com> <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com> <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com> <CAPDSy+7rnxrZDkfUzRGsyaj+RUFxBEyDubETrzx5huFSb3eUxw@mail.gmail.com>
Date: Thu, 27 May 2021 18:20:24 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87tumogncn.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/GdqQW6u2q6wFA7r5GZO-DLWEeoA>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 16:20:46 -0000

David Schinazi <dschinazi.ietf@gmail.com> writes:

> On Thu, May 27, 2021 at 6:54 AM Donald Eastlake <d3e3e3@gmail.com> wrote:
>
>> Hi David,
>>
>> On Wed, May 26, 2021 at 2:41 PM David Schinazi <dschinazi.ietf@gmail.com>
>> wrote:
>> >
>> > On Tue, May 25, 2021 at 9:02 PM Donald Eastlake <d3e3e3@gmail.com>
>> wrote:
>> >>
>> >> Hi David,
>> >>
>> >> On Tue, May 25, 2021 at 8:24 PM David Schinazi <
>> dschinazi.ietf@gmail.com> wrote:
>> >> >
>> >> > Adding "IESG submission of IPv4 via IPv6" as a
>> >> > milestone is fine by me, because we're about to do that
>> >> > anyway. I've never found milestones to be useful, so
>> >> > I'm not sure there's any benefit in doing this as opposed
>> >> > to just submitting the draft for publication.
>> >>
>> >> I think milestones give an idea of what the WG has accomplished or may
>> >> accomplish in the future. They sort of supplement the Charter. But I'm
>> >> willing to admit that the "IESG submission of IPv4 via IPv6" doesn't
>> >> add that much. On the other hand, it's mostly the Chairs doing the
>> >> work to modify/track the set of milestones.
>> >
>> > To clarify, I don't object to the chairs creating a
>> > "IESG submission of IPv4 via IPv6" milestone.
>>
>> OK.
>>
>> >> ...
>> >>
>> >> > Regarding the "WG adoption of a Babel multicast draft"
>> >> > milestone, I would personally like to see such a draft
>> >> > written and discussed at a WG meeting before a
>> >> > milestone is added. That would ensure that we have folks
>> >> > willing to do the work for this to happen.
>> >>
>> >> I don't see why a milestone can't be aspirational.
>> >
>> > Does the aspiration reflect WG consensus? My understanding
>> > is that we're a very implementation-driven WG, and I'd prefer to
>> > have aspirations reflect what implementers aspire to build.
>> > Alternatively, hearing from someone who runs a Babel network
>> > telling us that they have a need for multicast would also be great.
>>
>> No consensus call has been made.
>>
>> >> > I disagree with Donald's statement that "a routing system that
>> >> > doesn't handle both unicast and multicast seems incomplete",
>> >> > because I have yet to find a general-purpose use-case for
>> >> > non-link-local multicast whereas unicast is general-purpose :-)
>> >>
>> >> What makes one use "general" and another "special"?
>> >
>> > I'd say "general-purpose" means there are several applications using
>> > it, whereas "special-purpose" is for a single application.
>>
>> See below for a couple of applications.
>>
>> >> What is a "link"? Say you have a network of Babel routers. Some
>> >> communicate by radio where the transmission on one of its radios by a
>> >> router may be received by zero, one, or more other routers. Some
>> >> communicate by wire/Ethernet but some of those connections are bridged
>> >> so those inter-router connections are more stable but can be
>> >> bi-lateral or multilateral. What exactly is a link in this network?
>> >
>> > My personal definition is: two devices are on the same link if they can
>> > hear each other's Babel Hellos and IHUs.
>>
>> Ahhh, so you meant a Babel link.
>>
>> >> I tend to think of multicast as being either discovery multicast or
>> >> application multicast. For application multicast, generally you can
>> >> use head end replication and unicast which is less efficient in terms
>> >> of link utilization and generally has higher latency due to multiple
>> >> copies being sent on a link but might be simpler; on the other hand,
>> >> if there are lots of sources and multicast groups, these head ends
>> >> have to all keep track of who to unicast to. For discovery, you can't
>> >> do everything with unicast because, by definition, you want to be able
>> >> to find nodes that you don't know about yet; but you can probably get
>> >> away with unicast + link local multicast for some definition of link.
>> >> So I agree you can find some way to do everything with unicast and
>> >> link local multicast but that doesn't mean it is the best way to do
>> >> everything.
>> >
>> > In my mind, the best way to perform discovery is to combine unicast
>> > and link-local multicast. That's what we use in DNSSD which is AFAIK
>> > the IETF-recommended way to perform service discovery.
>>
>> OK for discovery although I'm not aware of anything that explicitly
>> states that that is an IETF recommendation.
>>
>>  Here are the first two application multicast uses that come to mind:
>>
>> Say you have a provider network with multiple tenants attached.
>> Multicast packets arriving from a tenant need to be sent out to other
>> islands of that tenant connected to your provider network. I don't
>> want to get too bogged down in details of topology and optimizations
>> and stuff but I think that some form of tree distribution is needed to
>> scale. Interconnecting pieces of the same VLAN is similar. 802.1
>> bridging and TRILL routing are examples of complete packet forwarding
>> systems that handle unicast and multicast and build such distribution
>> trees.
>>
>
> In this example, what's the application? What application data are the
> multicast packets arriving from a tenant carrying?
>
> Another application is streaming media. IP-TV in access networks
>> pretty much always uses multicast.
>>
>
> Definitely agree with this example, I think it's the main use of
> non-link-local multicast on the Internet today.
>
> All this said, if you really want to add the milestone, I'll back off.
> I'm just commenting that this would be the first milestone we have
> that wasn't backed by support from implementers of Babel.

In my view, having multicast support in Babel would be quite cool just
for this use case. I know people who do this with spanning tree today
(although the chances of them switching to Babel are slim).

However, it would very much be an aspirational "nice to have" thing for
my part at least. As in, I sadly don't think I can commit many cycles to
actually working on adding such support... :(

-Toke


From nobody Fri May 28 05:00:32 2021
Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B353A265F for <babel@ietfa.amsl.com>; Fri, 28 May 2021 05:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 BmLZ71mpdudt for <babel@ietfa.amsl.com>; Fri, 28 May 2021 05:00:27 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5461F3A2659 for <babel@ietf.org>; Fri, 28 May 2021 05:00:26 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 14SC0M2O012349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 May 2021 14:00:22 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 14SC0MR1016832; Fri, 28 May 2021 14:00:22 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 171BAD105E; Fri, 28 May 2021 14:00:22 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id arj1Ug4e_f8n; Fri, 28 May 2021 14:00:20 +0200 (CEST)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0C9B4D105C; Fri, 28 May 2021 14:00:20 +0200 (CEST)
Date: Fri, 28 May 2021 14:00:19 +0200
Message-ID: <87o8cvnk4s.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= <toke@toke.dk>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>, Babel at IETF <babel@ietf.org>
In-Reply-To: <87tumogncn.fsf@toke.dk>
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com> <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com> <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com> <CAPDSy+7rnxrZDkfUzRGsyaj+RUFxBEyDubETrzx5huFSb3eUxw@mail.gmail.com> <87tumogncn.fsf@toke.dk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/28.0 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 28 May 2021 14:00:22 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 28 May 2021 14:00:22 +0200 (CEST)
X-Miltered: at korolev with ID 60B0DB56.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 60B0DB56.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 60B0DB56.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@irif.fr>
X-j-chkmail-Enveloppe: 60B0DB56.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 60B0DB56.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 60B0DB56.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/QboMuK-Xk2LvJ9TFxEOTKAOT5EM>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2021 12:00:32 -0000

> In my view, having multicast support in Babel would be quite cool just
> for this use case. I know people who do this with spanning tree today
> (although the chances of them switching to Babel are slim).

I think it could be a lot of fun if done in collaboration with someone
actually doing large-scale video distribution.  Not so sure about
implementing multicast in isolation and hoping it gets adopted.

-- Juliusz


From nobody Fri May 28 05:36:53 2021
Return-Path: <toke@toke.dk>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A8C3A275A for <babel@ietfa.amsl.com>; Fri, 28 May 2021 05:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=toke.dk
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 29p7lpWXE7GF for <babel@ietfa.amsl.com>; Fri, 28 May 2021 05:36:46 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 452783A2759 for <babel@ietf.org>; Fri, 28 May 2021 05:36:46 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1622205403; bh=MCUCvMCXJNyamBJ2TFn6aV7RRLlZP9TDpsxbdKA0N1g=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=N8mete/1JQJr5rE/LfYHTcApQ3OaF4ALsOtVLl0z/7t7baciCrNsl7tMevrXUHck3 ClwYxxYZBKFW6ZIym6iysP1RljXSV7vrV75VBXBxgbZ0Pa4SkR/S1ILknyBv9puN/e tTXOyZacXNsY88k7/I9+EzpGb+rj94AxNRWbTlUrJIFfXA+Sdw9nLG7KQ7z/YEI1P+ ELHNQmTFuRzPGWrpTSWO7eRjEFWiJvn4kPBTX5rBM5H/lXxjga1WcRGjEVtQF+Ix4k fauIfJdi/U7ZvwlbymUy+dd7M6nRRh3HSUZRzg0OIuyMjSrLeIZUnjF/M7bh0x2yC5 Fvlcx2eX4SpaQ==
To: Juliusz Chroboczek <jch@irif.fr>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>, Babel at IETF <babel@ietf.org>
In-Reply-To: <87o8cvnk4s.wl-jch@irif.fr>
References: <CAF4+nEFuQ8zvaxKTkBTqb3q_gQWTMYJDF+GQTz-A1OPPkrj1Ag@mail.gmail.com> <87v976voss.wl-jch@irif.fr> <CAF4+nEG0rJ7ykAuoUS8VoC2XvEk5VvmHiykmGMyvyPP1OcQhJQ@mail.gmail.com> <CAPDSy+61k62heXUc4SVutKKkOVoYFj+SOyWRuE-2dybaFo62xA@mail.gmail.com> <CAF4+nEEeXhuTsDR-YFBXhGUwvfFaiLmjb0+V8LZm7Ns-7y31fA@mail.gmail.com> <CAPDSy+5kA4N32ZOjKbn7r4bs1VjDhxAj-SdBeTk2UFNUyV0cYw@mail.gmail.com> <CAF4+nEHQOUu6fk9xj71FXjwTV8tMG9ZFqZeKC=5pDjkKStdPWA@mail.gmail.com> <CAPDSy+7rnxrZDkfUzRGsyaj+RUFxBEyDubETrzx5huFSb3eUxw@mail.gmail.com> <87tumogncn.fsf@toke.dk> <87o8cvnk4s.wl-jch@irif.fr>
Date: Fri, 28 May 2021 14:36:42 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87zgwff31h.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/s9dQ_uCqqtB1NwZtNzWAEzRfkjY>
Subject: Re: [babel] Adding two babel milestones
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2021 12:36:52 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

>> In my view, having multicast support in Babel would be quite cool just
>> for this use case. I know people who do this with spanning tree today
>> (although the chances of them switching to Babel are slim).
>
> I think it could be a lot of fun if done in collaboration with someone
> actually doing large-scale video distribution.  Not so sure about
> implementing multicast in isolation and hoping it gets adopted.

Totally agreed; hence the "nice to have" classification :)

-Toke

