[icnrg] Carsten Bormann's Yes on draft-irtf-icnrg-icnlowpan-09: (with COMMENT)

Carsten Bormann via Datatracker <noreply@ietf.org> Fri, 04 December 2020 16:49 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: icnrg@irtf.org
Delivered-To: icnrg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9D13A0E09; Fri, 4 Dec 2020 08:49:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carsten Bormann via Datatracker <noreply@ietf.org>
To: "The IRSG" <irsg@irtf.org>
Cc: draft-irtf-icnrg-icnlowpan@ietf.org, icnrg-chairs@ietf.org, icnrg@irtf.org, Dirk Kutscher <ietf@dkutscher.net>, ietf@dkutscher.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Carsten Bormann <cabo@tzi.de>
Message-ID: <160710059258.13931.15555178258578483054@ietfa.amsl.com>
Date: Fri, 04 Dec 2020 08:49:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/CQ6a7Pytn_Vn85NT4jT7WUYnt9U>
Subject: [icnrg] Carsten Bormann's Yes on draft-irtf-icnrg-icnlowpan-09: (with COMMENT)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2020 16:49:53 -0000

Carsten Bormann has entered the following ballot position for
draft-irtf-icnrg-icnlowpan-09: Yes

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:


This is a good basis for running experiments with ICN in constrained node
network environments. There are a few nits left, at least one of which needs to
be addressed before moving this forward to the next process step.

The "C" flag is rather confusing for the reader (set to 0 for compression);
could this be an "U" (uncompressed) flag? Clearly, the erroneous Table 1
reflects the need for such a change.

RFC 8930 and related have been published; this puts the present specification
on somewhat firmer ground.