[6lo] Fragment recovery, shepherd writeup: one minor point

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Sun, 20 October 2019 15:15 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE891200EC for <6lo@ietfa.amsl.com>; Sun, 20 Oct 2019 08:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 fEBahyi_ucrs for <6lo@ietfa.amsl.com>; Sun, 20 Oct 2019 08:15:07 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E70A6120090 for <6lo@ietf.org>; Sun, 20 Oct 2019 08:15:06 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x9KFF0IF033334; Sun, 20 Oct 2019 17:15:00 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id EB1171D53C1; Sun, 20 Oct 2019 17:14:59 +0200 (CEST)
Received: from 193.153.132.124 by webmail.entel.upc.edu with HTTP; Sun, 20 Oct 2019 17:14:59 +0200
Message-ID: <0cf67636415db934b7b49ed02ee85887.squirrel@webmail.entel.upc.edu>
Date: Sun, 20 Oct 2019 17:14:59 +0200
From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu>
To: pthubert@cisco.com
Cc: 6lo@ietf.org
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at violet
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Sun, 20 Oct 2019 17:15:00 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/E3w739BQ6wUWmsgziwN-puFO8TM>
Subject: [6lo] Fragment recovery, shepherd writeup: one minor point
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sun, 20 Oct 2019 15:15:09 -0000

Hello Pascal,

While preparing my shepherd write-up for the 6lo fragment recovery draft, 
 I noticed one minor detail that I would like to bring to your attention.

In -05, draft-ietf-lwig-6lowpan-virtual-reassembly was added as a
reference. I think it is a bit odd that this document is mentioned for the
first time only at the end of the Security considerations section (note
that this reference is in fact a normative reference).

My proposal is updating the second paragraph of Section 1, and the last
paragraph of Section 2.4, so that
draft-ietf-lwig-6lowpan-virtual-reassembly is also introduced there.

For example, for Section 2.4, it could be something along the lines of:

CURRENT:
   "LLN Minimal Fragment Forwarding" [I-D.ietf-6lo-minimal-fragment]
   introduces the concept of a Virtual Reassembly Buffer (VRB) and an
   associated technique to forward fragments as they come, using the
   datagram_tag as a label in a fashion similar to MPLS.  This
   specification reuses that technique with slightly modified controls.

NEW:
   "LLN Minimal Fragment Forwarding" [I-D.ietf-6lo-minimal-fragment]
   introduces the concept of a Virtual Reassembly Buffer (VRB) and an
   associated technique to forward fragments as they come, using the
   datagram_tag as a label in a fashion similar to MPLS. The technique is
   described in [I-D.ietf-lwig-6lowpan-virtual-reassembly].  This
   specification reuses that technique with slightly modified controls.

... and something similar might work also for Section 1.

What do you think?

Thanks,

Carles (as the document shepherd)