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

Mirja Kühlewind via Datatracker <noreply@ietf.org> Wed, 13 March 2019 13:49 UTC

Return-Path: <noreply@ietf.org>
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 31A4D1240D3; Wed, 13 Mar 2019 06:49:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-6lo-nfc@ietf.org, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, 6lo-chairs@ietf.org, carlesgo@entel.upc.edu, 6lo@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155248496919.27828.10433234865223953092.idtracker@ietfa.amsl.com>
Date: Wed, 13 Mar 2019 06:49:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/EMsByCd4EOvGO6e3XDH-NgJkPzw>
Subject: [6lo] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-6lo-nfc-13=3A_=28with_COMMENT=29?=
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 13:49:29 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-6lo-nfc-13: 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-nfc/



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

1) I agree with Benjamin's discuss point on sec 3.4: there seems to be a
mismatch between the text and the figure that needs to be resolved or clarified
before publication.

2)Use of normative language doesn't always seem quite appropriate, especially
SHALL. Benjamin already identified some cases in section 3.3.

Here is an additional one in sec 4.1:
"The adaptation layer for IPv6 over NFC SHALL support neighbor
   discovery, stateless address auto-configuration, header compression,
   and fragmentation & reassembly."

Also this MAY in sec 5.2:
"In an isolated NFC-enabled device network,
   when two or more LRs MAY be connected with each other, and then they
   are acting like routers, the 6LR MUST ensure address collisions do
   not occur."

Please also check other occurrences.

3) I would have expected to see some discussion about the ability to
potentially connect devices over an IP-gateway device to the Internet that were
previously not designed to be connected to the Internet. However, maybe that's
asked too much as that is certainly something that needs to be addressed by
either a higher layer or the device system architecture as a whole.