[babel] Mirja Kühlewind's No Objection on draft-ietf-babel-applicability-08: (with COMMENT)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Tue, 06 August 2019 11:32 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 EB8D11200B7; Tue, 6 Aug 2019 04:32:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-babel-applicability@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, babel-chairs@ietf.org, d3e3e3@gmail.com, babel@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <156509114995.19226.16020049490173399413.idtracker@ietfa.amsl.com>
Date: Tue, 06 Aug 2019 04:32:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/bmU7pf51o3EExIzmLOGrdpyFhJU>
Subject: [babel] Mirja Kühlewind's No Objection on draft-ietf-babel-applicability-08: (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: Tue, 06 Aug 2019 11:32:30 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-babel-applicability-08: 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-babel-applicability/



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

Thanks for writing this document and the recent updates. While it is an easy
read, I agree with others that there might still be some case where maybe
benefits are overstated, e.g. sec 2.1 is not very objective and only provides
basically two anecdotes. Other examples are these sentences:

"In addition to the above, our implementation experience indicates
   that Babel tends to be robust with respect to bugs: more often than
   not, an implementation bug does not violate the properties on which
   Babel relies, and therefore slows down convergence or causes sub-
   optimal routing rather than causing the network to collapse."

or

"No other routing protocol known to us is similarly robust and
   efficient in this particular kind of topology."
(also still one "us" here)