[babel] Shepherd Review of draft-ietf-babel-source-specific-04

Donald Eastlake <d3e3e3@gmail.com> Wed, 10 April 2019 03:12 UTC

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 C1ED912009C; Tue, 9 Apr 2019 20:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 hCbFl1tMZCiw; Tue, 9 Apr 2019 20:11:59 -0700 (PDT)
Received: from mail-it1-x129.google.com (mail-it1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 2C94F1200B3; Tue, 9 Apr 2019 20:11:59 -0700 (PDT)
Received: by mail-it1-x129.google.com with SMTP id 139so1006603ita.4; Tue, 09 Apr 2019 20:11:59 -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=e/DEdB51Ud/benR6PDhUjCOTFRagnHoOxhateZG7M9I=; b=sZBptEZY86RS8Bml+EyzN0tg5ZEMxek96NMaXv8CdEhvPmAvpK/ikOdmmZzcz2GFlc LifboZz3JUTAHxoZAesk95tovG+5TOXfM6k9wt5lUO+UQ6IWbgn9/3lCXM+yrRciiH7A qs5f1vRBFdTNqypk4ge8024WUERgufkeEuT1Fmi+9xgWiVCwsOOUk6srpvy/i+kWBMpO FK5GdCVL7MyAZoQFD2paWKe0Ea+zFZAmWWsAOqg6OSio7Khxidnxlt1sEHH5OSs0ip/j yBDMmYWYHW7XjW6b1LGUjyWLT2CFGa4oRVHjN2GHBllsxOSM/j6lwdiIrU8HzJ00IEMv b0dw==
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=e/DEdB51Ud/benR6PDhUjCOTFRagnHoOxhateZG7M9I=; b=Im8bl6MSCK6UxhyZgF5PIhC+k4M8v/NHdzpFpDFPdMnTX+8GvwzUidcfKEQlbd9RKO LYvJEhlVdU+uxVNujALAOmGHmAx7+laB4FbCQJ5oidRv91F9NxozxLWVdx+BeihJ7DaM q2XE8uLHKF6k6VmtM+xM5xH1E12anuHUGLe6U5RslDZFdsEN9kNMyHI4RiO6rh3Omar4 8XC3T7LzVBE+Fj+FYY+P0ywGMDX7xcVCoLMIhTCM/juu8M+EAMUXSVgkpmL5I3/193YR 31N2vhsv7WIOfjRkENFBmusvmESPTZhbdcvVClkSA7w94Mf+i0+baKXHMoDKnpTZ36G4 2hAw==
X-Gm-Message-State: APjAAAVNzL0OKhySClB3riCOX6PhOIgb/HpX/jqbtfK7e/Mb0HNppweN PgwyxEwflCf8o/dgHEyGcdqUCeTi8zvM1iCdhxEB+kFK
X-Google-Smtp-Source: APXvYqxKcNB9QKINRE440IQ5l1Y5uaO4hbQmlKJP5yuWBB11qU+k5cmIM+Sra2dRgslzF3/h6LNUctuGv9xRFur2HcM=
X-Received: by 2002:a24:383:: with SMTP id e125mr1435889ite.96.1554865918125; Tue, 09 Apr 2019 20:11:58 -0700 (PDT)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 09 Apr 2019 23:11:46 -0400
Message-ID: <CAF4+nEEfEvg_ktoudURqvCPshrA8SzL+TMGjQm6vUOFX65q==A@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b931a70586246ed0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/S4QVnhDZ38bsph2qOvw06qzEfoU>
Subject: [babel] Shepherd Review of draft-ietf-babel-source-specific-04
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, 10 Apr 2019 03:12:01 -0000

Hi,

Possible technical issues:
===================
Section 6, page 7, first parenthetical:
   I think instead of "and all of its extensions" it should say something a
bit more limited. How about "and all previously standardized extensions"?

Section 7, page 8, 2nd paragraph:
   Generally, cases where different routers can interpret routing protocol
messages differently make me very nervous. It is almost always possible to
construct a situation where this causes persistent looping. It seems to me
that you need to unambiguously specify what is done if there is a malformed
TLV with multiple Source Prefix sub-TLVs. Such TLVs could always be ignored
or the first or the last Source Prefix sut-TLV could be the effective
sub-TLV with other Source Prefix sub-TLVs ignored. But whatever is
specified, it needs to be mandatory unambiguous behavior.

Section 7.1, Page 9:
   What do you do when you get a malformed Source Prefix sub-TLV with a
zero Source Plen? I guess this is answered below where it says the TLV is
ignored if the sub-TLV is malformed. (I guess it could also be malformed by
Source Plen being too large.) Perhaps it should say "This MUST NOT be 0. If
it is 0, the enclosing TLV is ignored."
   For completeness, whether the Source Prefix is left-justified or
right-justified should be specified.

Section 7.3, Page 9:
   Continuing the theme of some of the comments above, what do you do with
a wildcard request that does contain a Source Prefix sub-TLV?

Typos:
=====
Section 5.2, page 7, top line:
   "that is has" -> "that it has"

Section 7.2, Page 9, third line:
   "than" -> "as"

Minor textural comments:
===================
   These are just minor cases where I think the draft would read slightly
better with a wording change.

Abstract:
OLD
source address. This document describes an extension for source-
specific routing to the Babel routing protocol.
NEW
source address. This document describes an extension to the Babel
routing protocol for source-specific routing .

Section 1, page 3, 1st paragraph, next to last line:
   "in case of equality" -> "in case of equally specific destination
addresses"

Section 5.1, page 6, last line:
    "sub-TLV" -> "source specific sub-TLV"

Section 6.2, pag 8, first line:
   ", discarding source specific" -> ", the discarding of source-specific"

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA
 d3e3e3@gmail.com