[Roll] AD review of draft-ietf-roll-applicability-home-building

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 04 March 2015 21:39 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECFBE1A8966 for <roll@ietfa.amsl.com>; Wed, 4 Mar 2015 13:39:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] autolearn=ham
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 g8gZaWZf4PC2 for <roll@ietfa.amsl.com>; Wed, 4 Mar 2015 13:39:02 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F6171A8965 for <roll@ietf.org>; Wed, 4 Mar 2015 13:39:02 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t24Lcm0s030003; Wed, 4 Mar 2015 21:38:49 GMT
Received: from 950129200 (089144230044.atnat0039.highway.a1.net [89.144.230.44]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t24LcjYi029994 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 4 Mar 2015 21:38:46 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: consultancy@vanderstok.org, robert.cragie@gridmerge.com, Emmanuel.Baccelli@inria.fr, abr@sdesigns.dk
Date: Wed, 04 Mar 2015 21:38:46 -0000
Message-ID: <02ee01d056c3$9ad9f090$d08dd1b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBWw5DfyPmk4H9ZRQmdTE1K1htzlQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21376.000
X-TM-AS-Result: No--6.150-10.0-31-10
X-imss-scan-details: No--6.150-10.0-31-10
X-TMASE-MatchedRID: mVGzGnVbja4Qaipp+dGzb3BRIrj8R47F7yWPaQc4INTIs4CjQ/C5uTVk axwyOBfMQbOFXEEclEFLrzGOL1BrhG0AffdZMVlDW7gz/Gbgpl4ZbpN+hw0Ke9zOQo7mTgA+DFU +SD6gXjHbpOUT6D/xyGZjopFngc7Obx+xmQHMNIMIVoCLGbl5Ty7LAGznNYRea0TOsL14A2lzLi ypTPAGO91y2r32DMbvJu6v9wN0CtiYGUZbgkFG0h3EEAbn+GRbGYkyyELuGKTXLn2SCFOsbzWQZ YhfbX7wNJnt9TW/xwarqZpeZNqTSFbXOr5vDtxCr3X9gdfSLWV9LQinZ4QefL6qvLNjDYTwfY9h sM0xN70qtq5d3cxkNaCnS+on7MKrDondZn2uDw0Lrh67G9dQ0uPC4O8YJ2A/6eKEkY40QtbAvpL E+mvX8g==
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/FuB8DL9jrgPpaR0I9oj5KYNlTqE>
Cc: roll@ietf.org, roll-chairs@tools.ietf.org
Subject: [Roll] AD review of draft-ietf-roll-applicability-home-building
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk, Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 21:39:05 -0000

Thanks for this really nice document. I found it an easy read.

I have done my usual AD review to catch issues before IETF last call and
IESG evaluation.

I only have a handful of small issues, but I think it would be worth
resolving them with a new revision before we go to last call. I have 
marked the datatracker to show "Revised I-D needed" and I'll wait to
see you post a new version.

Thanks for the work,
Adrian

===

The chairs and I have discussed moving this document onto the Standards
Track in accordance with the description of an Applicability Statement in
Section 32 of RFC 2026. The only thing you need to do is update the 
"Intended status" to say "Proposed Standard".

The Shepherd will also need to update the write-up and flip the field in
the datatracker.

---

In 1.1. you have 

   The ROLL working group has specified a set of routing protocols for
   Lossy and Low- resource Networks (LLN) [RFC6550]

Yet 6550 defines

   Low-Power and Lossy Networks (LLNs)

---

Section 1.2 seems to only be necessary for a use of "MUST" in section
7. I am comfortable with you having used normal case ("must", "should",
"recommended") in the text. Could Section 7 also drop this to "must" 
and then you could remove Section 1.2?

---

2.2.7 mentions AODV without expanding the abbreviation and without a 
reference.

---

A few abbreviations need to be expanded on first use:
DIO
DAG
MPL
DAO
RA
ULA
DODAG
ETX

---

4.1.7 has...

   Repetition of the message can be inhibited by a small
   value of k.

I think this is lacking a little context. What is k?

---

Please mark Section 11 "To be deleted by the RFC Editor before 
publication."