From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [babel] John Scudder's No Objection on draft-ietf-babel-v4viav6-07: (with COMMENT)
Date: Wed, 16 Feb 2022 17:47:18 -0800 [thread overview]
Message-ID: <CAA93jw4VDPC8MZovP0QtqHpxik+ZpoCCQHu=rZ-LWNxsz0=qOg@mail.gmail.com> (raw)
In-Reply-To: <164506229993.5818.3014313795092972897@ietfa.amsl.com>
I'm not really sure what else babel needs but this extension looks good.
---------- Forwarded message ---------
From: John Scudder via Datatracker <noreply@ietf.org>
Date: Wed, Feb 16, 2022 at 5:45 PM
Subject: [babel] John Scudder's No Objection on
draft-ietf-babel-v4viav6-07: (with COMMENT)
To: The IESG <iesg@ietf.org>
Cc: <babel-chairs@ietf.org>, <draft-ietf-babel-v4viav6@ietf.org>,
<d3e3e3@gmail.com>, <babel@ietf.org>
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.
_______________________________________________
babel mailing list
babel@ietf.org
https://www.ietf.org/mailman/listinfo/babel
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-02-17 1:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <164506229993.5818.3014313795092972897@ietfa.amsl.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4VDPC8MZovP0QtqHpxik+ZpoCCQHu=rZ-LWNxsz0=qOg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox