Re: [6lo] 6lowpan Fragmentation design team interest?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 20 July 2017 07:51 UTC

Return-Path: <pthubert@cisco.com>
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 EDFA8127869 for <6lo@ietfa.amsl.com>; Thu, 20 Jul 2017 00:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 2uxf2zJaxNHq for <6lo@ietfa.amsl.com>; Thu, 20 Jul 2017 00:51:40 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A12DA126557 for <6lo@ietf.org>; Thu, 20 Jul 2017 00:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18136; q=dns/txt; s=iport; t=1500537100; x=1501746700; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gauBzu//rVgrHIGvOoUx1FaV4Y1kLvj+7eTNOz6f/lY=; b=Bwa33GdWAX2/iOtPwwUImogMvIqQMVggAnGZiV8NdR3Pz4UwOa5sJlP4 ilW03ypFgK97WAOs4A+v+qGbW+ZV42JEWHhkfSKa8Bv0AZZNk+EmxyIqY JP5dY3KSPsbQV4/aMgX1bLX65rKgV1+JWoUEBW9evMzWwyaR+xPWZg2C+ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CaAAC/YHBZ/5JdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm9rZIEUB44EkWaIL4gqhSyCESEBDoUXAhqDVT8YAQIBAQEBAQEBayiFGAEBAQEBAQEBASEKQQsFCwIBBgIRBAEBAScDAgICHwYLFAkIAgQBDQUIE4kwTAMNCBCTFJ1kgiaHMw2DXwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgyiDTYFhgySCV4JJgl2CYQWfAzsCixOEFYRnghWFUIpYjA2JUAEfOIEKdRVJhxZ2AYhrgQ4BAQE
X-IronPort-AV: E=Sophos;i="5.40,382,1496102400"; d="scan'208,217";a="458440013"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2017 07:51:39 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v6K7pdhS019922 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jul 2017 07:51:39 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 02:51:38 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Thu, 20 Jul 2017 02:51:38 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Carsten Bormann <cabo@tzi.org>
CC: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Samita Chakrabarti <samitac.ietf@gmail.com>, lo <6lo@ietf.org>
Thread-Topic: [6lo] 6lowpan Fragmentation design team interest?
Thread-Index: AQHTASw1Qn1ZaVSBbEKnRx43FR7qtKJcVnzQ
Date: Thu, 20 Jul 2017 07:51:21 +0000
Deferred-Delivery: Thu, 20 Jul 2017 07:51:04 +0000
Message-ID: <40de33a9a3f841528ffa25ad84d698b5@XCH-RCD-001.cisco.com>
References: <CAKmdBpcXJcWH3x2EE+FmM7sVJvo5ahpg-RHS5oyrdLsnA9Ck-g@mail.gmail.com> <7DA7530E-A090-48B3-9DD4-679FB8B8D1E4@tzi.org> <CAC8QAcdeGkYm2FxeiWkWKo4utA6Zgcq0P3a-mGCv4SWwKhQDPg@mail.gmail.com>
In-Reply-To: <CAC8QAcdeGkYm2FxeiWkWKo4utA6Zgcq0P3a-mGCv4SWwKhQDPg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.103.181]
Content-Type: multipart/alternative; boundary="_000_40de33a9a3f841528ffa25ad84d698b5XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/iFVXQ-fzkEIcEg4TW8Dh0S93NRo>
Subject: Re: [6lo] 6lowpan Fragmentation design team interest?
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 07:51:43 -0000

Hello Behcet :

The LPWAN solution is part of the SCHC document and is now very close to last call.
The basis of bitmap ack is common but there are also differences in the problem space du to frame size and meshing.
So the commonality only goes so far…

Take care;

Pascal



From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: jeudi 20 juillet 2017 09:46
To: Carsten Bormann <cabo@tzi.org>; Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>; Samita Chakrabarti <samitac.ietf@gmail.com>; lo <6lo@ietf.org>
Subject: Re: [6lo] 6lowpan Fragmentation design team interest?

Hi Pascal,
Is fragmentation an issue in lpwan also?
If yes, maybe a joint DT can be formed.
Another question: I think we are talking about 802.15.4 maximum frame size of 127 limitation here, is that right?
Regards,
Behcet

On Wed, Jul 19, 2017 at 8:53 AM, Carsten Bormann <cabo@tzi.org<mailto:cabo@tzi.org>> wrote:
We need to do at least the first two of three things:

(1) Write up how fragment forwarding works today (those implementation techniques are currently not documented in a way that is very accessible to new implementers).

(2) Look at the timing considerations governing burst packet transmission to a forwarder and paced fragment forwarding.  Can we derive guidelines for implementers or even standardize something (BCP or PS level)?  This requires finding (and possibly conducting) pertinent research.

(3) Look at the use cases that would benefit from multi-hop fragment retransmission (we have fragment retransmission today, but only single-hop, and only for unicast).  If we find any such use cases, document their characteristics, and try to find solutions that have ways to resolve interactions with (2) and with transport-layer retransmission timers.  This requires way more research.

We also could look at better supporting ECN and other issues that come up in tunneling-like environments.

Grüße, Carsten


> On Jul 18, 2017, at 18:34, Samita Chakrabarti <samitac.ietf@gmail.com<mailto:samitac.ietf@gmail.com>> wrote:
>
> Dear all:
>
> At IETF99 6lo wg meeting 6lo-chairs discussed a few questions in order to sense WG interests for further work on fragmentation - especially for route-over topology.
> The details charter for the design team will be finalized soon.
> However, the 6lo-chairs are collecting names for the interested individuals for the design team. We might need 4-5 person design team and prior experience on packet forwarding is helpful.
>
> We are requesting the following :
> * Send your ideas to the list on what you want to see resolved by the fragmentation design team
>
> * If you have any prior experience on 6lowpan fragmentation work on router-over or mesh-under please send information about it
>
> Thanks,
> Gabriel & Samita
>
> Reference slides from today's session:
>
> https://www.ietf.org/proceedings/99/slides/slides-99-6lo-wg-discussion-questions-on-6lo-fragmentation-work-and-scoping-01.pdf
>
> https://www.ietf.org/proceedings/99/slides/slides-99-6lo-6lowpan-fragment-forwarding-in-route-over-multi-hop-topology-00.pdf
>
>
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org<mailto:6lo@ietf.org>
> https://www.ietf.org/mailman/listinfo/6lo

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