[Int-dir] INTDIR review of draft-ietf-mif-happy-eyeballs-extension-09

Ralph Droms <rdroms.ietf@gmail.com> Tue, 03 May 2016 21:19 UTC

Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 351D312D90C; Tue, 3 May 2016 14:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 Wg8sEZckt9aL; Tue, 3 May 2016 14:19:53 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 25A2C12D8ED; Tue, 3 May 2016 14:19:51 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id w36so14503442qge.3; Tue, 03 May 2016 14:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:date:message-id:cc:to:mime-version; bh=YrPM0ZRwJADr/7QQydCwnXPWQ8DTv2+t5FqJ5tRDNPo=; b=hiA5rG4zQ23I+/ZmY2REJEb88pTconxqQYysCKRuNOoZ7W5mpJ2clYYl6o8YAyrEyC sR5KmE5adIrJ6i/+mxAasshBRmRlE11CjrMrbGYGEIxO9SbO0pC6dkvv7pEaxDmIN1iu 8buv0UzawLXJVN0tb914poJeM548OzCA44PsvRE10k0cDdEARVcJxc0aVqmTqkoQpDEv 7kLRHWkqeI3PYk8j72cOOVfWtBbZN01lpJuLvxdmEBwHo76NhNIPizQOXfl6hUbt497v L2qJ0H5GBI1zqCT7zl2NPGXCR7xv7O28p82zvWOeQCOnTunh48sagM7zZG1LtJSM+EqZ WwKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:date:message-id:cc:to:mime-version; bh=YrPM0ZRwJADr/7QQydCwnXPWQ8DTv2+t5FqJ5tRDNPo=; b=N6os8+DOyYuiQqGlqITup49aVaN3uoEjXSGruzGpPxPYMz63aMzowQU+tKsVHwZAto 0Y7G0GBdeC/4TRvXtHd1umQKftYTX4zytM6nIFRxgalj2vWw7BWJsnxs5q3W77SM09Sf Avy9FR6tN8YvGqjmquescwtktZVBS5ysoDqzYfN3hwzQvwT0c1yJcebP+RjZSmWShltZ +JRPaxJ09NGB5Yau6DWKs7OCsaPRxY9QALr2qiWnMBuRQHkj0BYYCCZIn+7YNze65wUy 8fCJjxnqrIJyOxfRcQPVTI5DmVGqPUSu2ezPjcwpg2bYO1PSLhtuX77lI/5xXN6Pizec ljUg==
X-Gm-Message-State: AOPr4FWxi5CQPUNdNLXGXhNoqncZAm4ePsEem8aJFFzDSS7QhEg7/97jd1+w3xB0QaAmZA==
X-Received: by 10.140.235.14 with SMTP id g14mr5096730qhc.86.1462310391153; Tue, 03 May 2016 14:19:51 -0700 (PDT)
Received: from [192.168.1.114] (c-24-62-230-192.hsd1.ma.comcast.net. [24.62.230.192]) by smtp.gmail.com with ESMTPSA id 23sm132513qkd.8.2016.05.03.14.19.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 03 May 2016 14:19:50 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_F0F97785-5018-4FF4-BAD9-38CF3A8C1481"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Date: Tue, 03 May 2016 17:15:36 -0400
Message-Id: <AEDAB45F-255C-4AD1-A17D-8E0F141006B3@gmail.com>
To: "<int-dir@ietf.org>" <int-dir@ietf.org>, int-ads@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-dir/-t-F0qvRpYSGMO8_hWZqHhQW9Ro>
Cc: draft-ietf-mif-happy-eyeballs-extension.all@tools.ietf.org
Subject: [Int-dir] INTDIR review of draft-ietf-mif-happy-eyeballs-extension-09
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 21:19:55 -0000

I am an assigned INT directorate reviewer for
draft-ietf-mif-happy-eyeballs-extension-09. These comments were
written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these
comments just like they would treat comments from any other IETF
contributors and resolve them along with any other Last Call comments
that have been received. For more details on the INT Directorate, see
http://www.ietf.org/iesg/directorate.html.

In my opinion, the documents lacks - and needs - a clear statement of
purpose.  What result is the document trying to achieve?  Who is the
audience?  How would the audience put the contents of the document to
use?

The document must be edited carefully for english language usage
before publication.  I would consider this issue to be worthy of a
"Discuss" on the document.  I found that the document is unclear in
several areas, which prevented me from understanding the meaning of
that text.  For example, in section 2, does "within a single home."
mean a device in one home or a device with just one interface?  In
section 5.1, does:

 users may dedicatedly prefer a 3GPP
 network interface to seek high-reliability or security benefits even
 to manually turn off WiFi interface.

mean:

 users may turn off a device's WiFi interface to guarantee use of a
 3GPP network interface to assure higher reliability or security.

Some sections seem to make observations about conditions that might
have an influence on an implementation of MIF-HE, but don't have any
actionable guidance for implementors.  This lack of clarity is related
to the lack of a clear statement of purpose for the document.  For
example, in section 5.1:

 The decision on mergence of
 policies may be made by implementations, by node administrators, even
 by other standards investigating customer behavior.  However, it's
 worth to note that a demand from users should be normally considered
 higher priority than from other actors.

I don't see anything in this text that I would consider actionable as
an implementor.

It is unclear where the document explicitly choosing one interface as
"faster".  Section 5.2 includes text about "the outcome of each
connection attempt"; does this text refer to recording the connection
time and using that time as the basis for future interface selection?

How does HE-MIF interact with HE for selecting between IPv4 and IPv6?