Re: [Roll] New Version Notification for draft-thubert-roll-forwarding-frags-01.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 25 February 2013 16:15 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0BC21F94EC for <roll@ietfa.amsl.com>; Mon, 25 Feb 2013 08:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.192
X-Spam-Level:
X-Spam-Status: No, score=-10.192 tagged_above=-999 required=5 tests=[AWL=0.406, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OZ9X1gSKW95Q for <roll@ietfa.amsl.com>; Mon, 25 Feb 2013 08:15:21 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 18A9521F94ED for <roll@ietf.org>; Mon, 25 Feb 2013 08:15:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14216; q=dns/txt; s=iport; t=1361808913; x=1363018513; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eySyP4BS6AsQ0Vh9xsRWzIEnpVx1fy8YiU/dx9DpsPY=; b=W1VwZJ/4IvSDdOuqR/YZd4/oRu05t56UKecdfyBDxMG8zxGEUSDsyTn7 afJzUf88p2p3IZuAiJ0F5W1CDEQDGt6UMkCGnnJYkQnabFyxELTMGysDw wVK3pc5hIoHT6pAw816LfljTz7WMGTvdTmHafo+7vdsZHtw2FIMrHYQOb A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AucFAOWMK1GtJXHB/2dsb2JhbABFgkOBNawUiSUBhliBS4EFFnOCHwEBAQQBAQEqQQkCDAQCAQgRBAEBCx0HIQYLFAkIAQEEDgUIAYd4Aw8HBbYXDYhxjDeBEAaBEA8XBwQGAQaCWWEDiDOKSYFkgnqKMYUXgTAigTWBaQIHFwYY
X-IronPort-AV: E=Sophos; i="4.84,735,1355097600"; d="scan'208,217"; a="180874663"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 25 Feb 2013 16:15:07 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1PGF6YW005967 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Feb 2013 16:15:06 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.89]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 10:15:06 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [Roll] New Version Notification for draft-thubert-roll-forwarding-frags-01.txt
Thread-Index: Ac4TRt1lRn7yWP4fSC6poc/BQIBG4gAVKzQAAAouHuA=
Date: Mon, 25 Feb 2013 16:15:05 +0000
Deferred-Delivery: Mon, 25 Feb 2013 16:15:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD835CCEAD8@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD835CCE70A@xmb-rcd-x01.cisco.com> <CADnDZ89BKM0y88SycGzt77B4_bBt5bBqFJJKq_HaKbVw5spgHw@mail.gmail.com>
In-Reply-To: <CADnDZ89BKM0y88SycGzt77B4_bBt5bBqFJJKq_HaKbVw5spgHw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.88.253]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD835CCEAD8xmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] New Version Notification for draft-thubert-roll-forwarding-frags-01.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 16:15:29 -0000

Hello Abdussalam,

This used to be 6LoWPAN but the work never took off there (see the mail exchange with Carsten).
The goal of the draft is to streamline fragments and retry individual frag loss.

It is useful if:
- you have route over
- but lack the 802.15.4g PHY.

Cheers,

Pascal

From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
Sent: lundi 25 février 2013 16:03
To: Pascal Thubert (pthubert)
Cc: roll@ietf.org
Subject: Re: [Roll] New Version Notification for draft-thubert-roll-forwarding-frags-01.txt

Hi Pascal,

I may need to discuss to know my interest, or to understand. Does this protocol have interact with RPL or its information? The title is LLN forwarding but the content is about 6LowPan, is this work better fitted in 6LoWPAN WG than ROLL?

AB
On Mon, Feb 25, 2013 at 10:58 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Dear WG:

As you know well, 6LoWPAN will fragment packets that are too wide for the MTU, which is likely to happen in a number of cases, unless the 802.15.4g MAC is used.

As a consequence, in a route-over RPL subnet, a large packet must be reassembled at each hop to be routed and fragmented again.

Streamlining the fragments will improve latency, and will save memory and CPU in the intermediate nodes.

This draft enables the forwarding of fragments, which selective acknowledgement and flow control capabilities, end to end over the LLN.

Upon a private request, I resubmitted the draft with a simplification, that is the removal of en encoding that would compress the acknowledgement bitmap.

I also restored some text about Congestion notification, in order to validate the need with the group.

Please let the authors know if you have interest in pursuing this work,

Pascal


-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>]
Sent: lundi 25 février 2013 11:42
To: Pascal Thubert (pthubert)
Cc: Jonathan Hui (johui)
Subject: New Version Notification for draft-thubert-roll-forwarding-frags-01.txt


A new version of I-D, draft-thubert-roll-forwarding-frags-01.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Filename:        draft-thubert-roll-forwarding-frags
Revision:        01
Title:           LLN Fragment Forwarding and Recovery
Creation date:   2013-02-25
Group:           Individual Submission
Number of pages: 16
URL:             http://www.ietf.org/internet-drafts/draft-thubert-roll-forwarding-frags-01.txt
Status:          http://datatracker.ietf.org/doc/draft-thubert-roll-forwarding-frags
Htmlized:        http://tools.ietf.org/html/draft-thubert-roll-forwarding-frags-01
Diff:            http://www.ietf.org/rfcdiff?url2=draft-thubert-roll-forwarding-frags-01

Abstract:
   In order to be routed, a fragmented packet must be reassembled at
   every hop of a multihop link where lower layer fragmentation occurs.
   Considering that the IPv6 minimum MTU is 1280 bytes and that an an
   802.15.4 frame can have a payload limited to 74 bytes in the worst
   case, a packet might end up fragmented into as many as 18 fragments
   at the 6LoWPAN shim layer.  If a single one of those fragments is
   lost in transmission, all fragments must be resent, further
   contributing to the congestion that might have caused the initial
   packet loss.  This draft introduces a simple protocol to forward and
   recover individual fragments that might be lost over multiple hops
   between 6LoWPAN endpoints.




The IETF Secretariat

_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll