[Gen-art] Gen-art telechat review of draft-ietf-homenet-arch-10

Elwyn Davies <elwynd@dial.pipex.com> Sat, 07 September 2013 00:43 UTC

Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 530D021F9EFB for <gen-art@ietfa.amsl.com>; Fri, 6 Sep 2013 17:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1TjX702XIqHv for <gen-art@ietfa.amsl.com>; Fri, 6 Sep 2013 17:43:46 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 841E621F9EF6 for <gen-art@ietf.org>; Fri, 6 Sep 2013 17:43:46 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1VI6ci-0007HY-4M; Sat, 07 Sep 2013 01:43:41 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Sat, 07 Sep 2013 01:42:31 +0100
Message-Id: <1378514551.13277.25129.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -1.0
Cc: draft-ietf-homenet-arch.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-homenet-arch-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Sep 2013 00:43:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-homenet-arch-10.txt
Reviewer: Elwyn Davies
Review Date: 6 September 2013
IETF LC End Date:
IESG Telechat date: 12 September 2013

Summary:
Apologies for missing the last call review of this document.  I was up a
volcano....
Essentially ready.  A few very minor points and nits.  Generally an
excellent analysis.. but it shows there is a long way to go to get a
zero config IPv6 homenet!

Major issues:

Minor issues:
s2.4:  Should this section mention that the border router at the
connection(s) to the homenet's ISP(s) SHOULD be set up to filter packets
with ULA source/destination addresses? (diiscussed later in para 5 of
s3.4.2 - a forward ref would help).

s3.7.3, last para:  Should this mention mail services?  As I have
discovered, failing to have a reverse DNS entry for a mail source can
lead to the mail being rejected.  There might be other
protocols/applications that need reverse DNS also.

s3.3.4, last para:  May not be possible to override policies defined by
ISP at external border.

s3.7.3, para 7: dotless domains - I'm not sure exactly whether these
will really be coming?  not quite reality yet - still subject to
discussion/challenge?  In any case probably need to define 'dotless
domains'.

Nits/editorial comments:
General: s/i.e./i.e.,/g, s/e.g./e.g.,/g

s1, p5:
OLD:
   as well as a better
   result than if the IETF had not given this specific guidance.

This sounds a little patronizing.

Perhaps something along the lines of 
NEW:
   as well as aiming at a more consistent solution that addresses 
   as many of the identified requirements as possible.

s1.1: Does WPA2 need a reference?

s2.4, p2:
> Depending upon circumstances beyond the scope of homenet,....
This sounds like a reference to the homenet working group which is
probably not what was meant.  Maybe something like:
   Depending on circumstances beyond the control of the owner of the
homenet,...

s3.3.2, p2:  s/subdivide itself to/subdivide itself into/

s3.3.3 Can you give examples of relevant protocols?

s3.3.4: Grid network?  Not sure what is meant here.

s3.4.1, p4: Expand DHCP-PD and provide ref.  Also make consistent with
s3.4.3, last para.

s3.5, para 3:  Uses PHY (twice) - needs expanding/explaining or use
'physical interface' as in previous sections.

s3.5, last para: s/participate the same way/participate in the same way/

s3.6: s/direct towards them./directed towards them./

s3.7.4, last para: Expand DNSSEC and give ref.

s3.7.6: CoAP needs a ref.

s3.7.8: Should devices roaming *to* the homenet be discussed?

s3.8.1: Link QoS to Quality of Service explicitly.

s3.8.1, para 2: s/drowning/overloading/ (drowning is slang).