[babel] John Scudder's No Objection on draft-ietf-babel-v4viav6-07: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Thu, 17 February 2022 01:44 UTC

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 EAA0D3A0F8D; Wed, 16 Feb 2022 17:44:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-babel-v4viav6@ietf.org, babel-chairs@ietf.org, babel@ietf.org, d3e3e3@gmail.com, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <164506229993.5818.3014313795092972897@ietfa.amsl.com>
Date: Wed, 16 Feb 2022 17:44:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/aFHKLyxxB4BdsSsFAUYkINiA4rk>
Subject: [babel] John Scudder's No Objection on draft-ietf-babel-v4viav6-07: (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, 17 Feb 2022 01:45:00 -0000

John Scudder has entered the following ballot position for
draft-ietf-babel-v4viav6-07: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thanks for this highly readable and useful document.

Regarding the distaste for the dummy 192.0.0.8 address, it seems to me that
this is a case of perfect as the enemy of good. A conflict-averse pragmatist,
foreseeing the objection, might simply have left Section 3 out of the document.
I don’t think that would have been a better outcome. I note furthermore that
the 192.0.0.8 mechanism isn’t even being specified here — it’s specced in RFC
7600, and is just offered as an implementation option here.