[Roll] Spencer Dawkins' No Objection on charter-ietf-roll-04-06: (with COMMENT)

"Spencer Dawkins" <spencerdawkins.ietf@gmail.com> Wed, 14 December 2016 03:06 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: roll@ietf.org
Delivered-To: roll@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 97BD212896F; Tue, 13 Dec 2016 19:06:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148168476058.10753.14596151426652360789.idtracker@ietfa.amsl.com>
Date: Tue, 13 Dec 2016 19:06:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/EoSyJj2TqqZin71qToaNOO1gQ3k>
Cc: roll-chairs@ietf.org, roll@ietf.org
Subject: [Roll] Spencer Dawkins' No Objection on charter-ietf-roll-04-06: (with COMMENT)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 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: <https://mailarchive.ietf.org/arch/browse/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, 14 Dec 2016 03:06:00 -0000

Spencer Dawkins has entered the following ballot position for
charter-ietf-roll-04-06: 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.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-roll/



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

This charter looks fine to me, modulo a few nits I wondered about.

Perhaps "self routing configuration" might be clearer as "routing
self-configuration"? 

I was expecting "It will also need to consider the transport
characteristic the routing protocol messages will experience" to refer to
characteristics, plural. But I wonder if the sentence would be clearer as
"The workng group will consider the transport characteristics routing
protocol 
messages will experience". 

I'm sure "Additional protocol elements to reduce packet size" is correct,
but it seems counter-intuitive. Is there a better way to say what you
mean?

Is "the draft about when to use RFC6553, RFC6554, and IPv6-in-IPv6
encapsulation Draft-ietf-roll-useofrplinfo" an Applicability Statement,
or did this mean something else? But I see that Mirja had a question
about the use of draft names that haven't been adopted. Perhaps it's
worth a pass substituting clearer descriptions for draft names?