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

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Mon, 21 October 2019 13:53 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 32B61120814 for <6lo@ietfa.amsl.com>; Mon, 21 Oct 2019 06:53:26 -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 7xpSFKhlNElo for <6lo@ietfa.amsl.com>; Mon, 21 Oct 2019 06:53:23 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (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 76F8D12011A for <6lo@ietf.org>; Mon, 21 Oct 2019 06:53:22 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x9LDrHCi028316; Mon, 21 Oct 2019 15:53:17 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 38AF01D53C1; Mon, 21 Oct 2019 15:53:16 +0200 (CEST)
Received: from 10.192.52.66 by webmail.entel.upc.edu with HTTP; Mon, 21 Oct 2019 15:53:17 +0200
Message-ID: <a33d540a2bf56ca7225cb5a72bda0166.squirrel@webmail.entel.upc.edu>
In-Reply-To: <MN2PR11MB3565FF40E4B1817CFC54C1F3D8690@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <0cf67636415db934b7b49ed02ee85887.squirrel@webmail.entel.upc.edu> <MN2PR11MB3565FF40E4B1817CFC54C1F3D8690@MN2PR11MB3565.namprd11.prod.outlook.com>
Date: Mon, 21 Oct 2019 15:53:17 +0200
From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: "6lo@ietf.org" <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 dash
X-Virus-Status: Clean
X-Greylist: Delayed for 22:38:17 by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Mon, 21 Oct 2019 15:53:17 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/nDiKjqWYjCircWn2QwlJ1Df1Xa4>
Subject: Re: [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: Mon, 21 Oct 2019 13:53:32 -0000

Dear Pascal,

Thanks for the new draft version.

Your update looks good to me!

Cheers,

Carles



> Dear Carles:
>
> I pushed an 06 that passes the doc to xml2rfc v3, and moves the ref to the
> LWIG implementation to informational.
> Please note that the main reason of the text about it is to indicate that
> it is non-compatible with this draft.
> For that reason it was actually strange to make it a normative reference,
> many thanks for spotting it..
>
> All the best;
>
> Pascal
>
> -----Original Message-----
> From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>;
> Sent: dimanche 20 octobre 2019 17:15
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>;
> Cc: 6lo@ietf.org
> Subject: Fragment recovery, shepherd writeup: one minor point
>
> 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)
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>