[6lo] Mirja Kühlewind's No Objection on draft-ietf-6lo-6lobac-06: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Wed, 30 November 2016 16:07 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: 6lo@ietf.org
Delivered-To: 6lo@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 757701298D3; Wed, 30 Nov 2016 08:07:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148052202047.14046.10952186150977815778.idtracker@ietfa.amsl.com>
Date: Wed, 30 Nov 2016 08:07:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/8Wm3EuQiz0bwVs-KkBlWXY0Id8A>
Cc: 6lo-chairs@ietf.org, samitac.ietf@gmail.com, draft-ietf-6lo-6lobac@ietf.org, 6lo@ietf.org
Subject: [6lo] Mirja Kühlewind's No Objection on draft-ietf-6lo-6lobac-06: (with COMMENT)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2016 16:07:00 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-6lo-6lobac-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.)


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-6lo-6lobac/



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

1) Agree with Ben that normative wording should not be used if it just
summarizes things that are specified in a different doc.

2) Section 5: "A node implementing [RFC7400] MUST probe its peers for GHC
support before applying GHC." How?

3) Just to make sure I get the security section right: MS/TP networks are
not connected to the Internet or use something like a gateway. Maybe make
this point more clear: basically say that the reason to use IPv6 is NOT
that you want to send these packets eventually directly to the Internet!