Re: Warren Kumari's No Objection on draft-ietf-bfd-vxlan-09: (with COMMENT)

Greg Mirsky <gregimirsky@gmail.com> Wed, 18 December 2019 00:31 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF9F912006F; Tue, 17 Dec 2019 16:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.597
X-Spam-Level:
X-Spam-Status: No, score=-0.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] 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 KkzwHRbcH4bN; Tue, 17 Dec 2019 16:31:08 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 84F16120033; Tue, 17 Dec 2019 16:31:07 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id m6so106318ljc.1; Tue, 17 Dec 2019 16:31:07 -0800 (PST)
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=AqiUhCUwfBkbWROk6r06ZKBpYTs0ev9uuePnwX0X+Yo=; b=imVPzoqF/gDmzF05IOZ+WdC1GgvKquqXEy213MnEI1LgAv+l4A9F5dr1xC8rGfnk4A q72q6fs+2m6k8vbB1+iXY+NNkjBymozsmWNPbPP10vyVO79U46NOIIwzulR0kaoB3B17 z7vp2nigH5mFmo3Sp7WE7vNL03hjZEPnCCs25xAAmKE/L4H7yOk4TjQ75ON0Bs/UNhHw 1HRd5TkQGDQl64YmtE6kww3FzZRp6gjfhGp4362ysXUiYUF5jYrMAVvSTzzgscm2URtu FBZA5l4/en5oGH6nSyyRL0DgoafIlwL6RF9GKF/UYpOYYCixLemVEoHLNgpnFz0UzCiu 6Jwg==
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=AqiUhCUwfBkbWROk6r06ZKBpYTs0ev9uuePnwX0X+Yo=; b=cxMzBzLRYsR12Wi9nNtFKO6ENVnX1T4QKFVb0URclc1SyFuagfVwvz+7V+ScpOgkb2 bEOZxNRWeUe0HG71nrl0DQu+249Mkq562IvEtCSI4m9eeBgbqL/WnqLPcs+UbGqjabqn Bt2exXdzzhKmqmen6Y2pBiTYSN+33vtFdLPyi0hoKqeVT3kPNmaO41cIL17KBoHrmX7F K96DACOMKwUedp17yBaXRVoVYlwJCHrw8RMNxgmzbDL6ehp5kj9OgzIL4aJ3DeGPFlQu bEfZNEPtMzcE72Sc7PaPUOgI2WrdyIn0XuxeWfjA/FJBK3q49PSz2jTWdP8QyCO/iXJ6 6DhA==
X-Gm-Message-State: APjAAAUd62irJU/eBo5T845MXSjXsX2X1fmbWQzrL+PutyIKHGqewmer R1QjsLzfzizbGrZreN5xJfrwG883ucvJ6zOIfJY=
X-Google-Smtp-Source: APXvYqyu172A9Co5NLYQ9Ziquo0uBN8GKc+dau0hezTTFFpTW72X4Jrad53ib79mY5yW+Xxrds2GtSZsPSF5Y6SjFH8=
X-Received: by 2002:a2e:b0db:: with SMTP id g27mr432969ljl.74.1576629065388; Tue, 17 Dec 2019 16:31:05 -0800 (PST)
MIME-Version: 1.0
References: <157659353960.26404.15894323280421366020.idtracker@ietfa.amsl.com>
In-Reply-To: <157659353960.26404.15894323280421366020.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 17 Dec 2019 16:30:54 -0800
Message-ID: <CA+RyBmVUVBn6G-UgR=eRy+MKB9LT0peZdL29vqOZ4Chz-o1hNw@mail.gmail.com>
Subject: Re: Warren Kumari's No Objection on draft-ietf-bfd-vxlan-09: (with COMMENT)
To: Warren Kumari <warren@kumari.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-bfd-vxlan@ietf.org, Jeffrey Haas <jhaas@pfrc.org>, bfd-chairs@ietf.org, rtg-bfd WG <rtg-bfd@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Content-Type: multipart/mixed; boundary="00000000000062b1ef0599ef8fcc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/CYmRBDNo2Iu4LDO5je0x6h5-ggg>
X-Mailman-Approved-At: Wed, 18 Dec 2019 06:31:13 -0800
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2019 00:31:12 -0000

Hi Warren,
thank you for the review. I've updated the representation of IPv6 addresses
to follow RFC 5952 and the reference to IPv4-mapped IPv4 loopback addresses
range per recommendations from Adam Roach. Attached, please find the diff
that highlights the updates made in the working version of the draft.
As to the suggestion made by Jurgen in his first review, would changing the
title of the section to Acronyms and Abbreviations make the scope of that
section more clear?

Regards,
Greg

On Tue, Dec 17, 2019 at 6:39 AM Warren Kumari via Datatracker <
noreply@ietf.org> wrote:

> Warren Kumari has entered the following ballot position for
> draft-ietf-bfd-vxlan-09: 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 IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-bfd-vxlan/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I support Benjamin and Eric's DISCUSSES - I considered holding a DISCUSS
> on the
> "loopback address" terminology and formatting (which was also noted in the
> excellent OpsDir review by Jürgen Schönwälder), but think that Eric can
> carry
> it.
>
> In addition, like Jurgen, I think it would be helpful to have pointers to
> where
> terms are defined - the "Terminology" section isn't really terminology, but
> rather just an acronym expansion section.
>
>
>