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

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 20 July 2017 07:45 UTC

Return-Path: <sarikaya2012@gmail.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 BD406131A7C for <6lo@ietfa.amsl.com>; Thu, 20 Jul 2017 00:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aDdQbqLj1ZiR for <6lo@ietfa.amsl.com>; Thu, 20 Jul 2017 00:45:55 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 9C8B7126557 for <6lo@ietf.org>; Thu, 20 Jul 2017 00:45:54 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id f21so10673386wrf.5 for <6lo@ietf.org>; Thu, 20 Jul 2017 00:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=GfkeDD/AgumEWD4x892lkSOF2trSuSC35purawXbF0c=; b=hSnNKIEdyG2rUcfBpYQWxIQDUZLICXxzcwWUpRgmQS8qO8PdxXNDMCRX58MZTNQ77T wNRgi1sHhfjV/UqFRlOMvlmsj8dU76dXkiVzwZeVW1fa0YaFWgP9Piy1jqTN5DtRacAQ 1KTLjwBPXXzVCzB4L1yObhvhrBUb3GPK+H6yUnKL4cCAOoMnpMJ7Z27EwZpb5MTfjsNd mtrOuD7u3ioDGJKi6gv2BXmmKHj51upuSHaYbgoHDVwbH4eJqjby/ke2Dx75tX1EG25T vwpiCf3Fu58kHelAGY502I104tf70I5BS8c8d8FdaaWb9pNO2omunt7lPh1+otZPQGKs tWyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=GfkeDD/AgumEWD4x892lkSOF2trSuSC35purawXbF0c=; b=mYpfIyQdBhO9NjSjVSkXrKcffwQQUYSTWNhVthyLcSwVcT3sXdO4kESGTYqd3cW8L1 o6snrptUDzyqQZqVuSBHLZj2mXX4lIrUmxaYLnTQ9Vqxjf5l+B2drgQtTVHjDZVJJQOA 5qrSeLKc73hKSfix+laPLIz3sZ9kkQmFFTVBGz9NqNvmoihVP+HOAiVUQd8fzJjgaJSc RKD8VEzzwelYlJiuKPd6umhVrzu89eItknWfy/KDiZ46Uq7nfS9SsAZgP7bW1vZaaJEe wYiFG+h+GsEeiAu8rn5p/rzosY9xWFkIy0cN1Vva542fo0CbJ6FnqhgCwNcKY886yPh+ F/yQ==
X-Gm-Message-State: AIVw112Rbf/WlWQAflpV8r4ExTf9V/yLQamkUaUXrvle9+0oc8sApHO3 9mEhQmyybZXTMxiA+eplxAGH4eCN9g==
X-Received: by 10.223.128.177 with SMTP id 46mr6065306wrl.150.1500536753199; Thu, 20 Jul 2017 00:45:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.212 with HTTP; Thu, 20 Jul 2017 00:45:52 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <7DA7530E-A090-48B3-9DD4-679FB8B8D1E4@tzi.org>
References: <CAKmdBpcXJcWH3x2EE+FmM7sVJvo5ahpg-RHS5oyrdLsnA9Ck-g@mail.gmail.com> <7DA7530E-A090-48B3-9DD4-679FB8B8D1E4@tzi.org>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 20 Jul 2017 02:45:52 -0500
Message-ID: <CAC8QAcdeGkYm2FxeiWkWKo4utA6Zgcq0P3a-mGCv4SWwKhQDPg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: Samita Chakrabarti <samitac.ietf@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, lo <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c09874225a0c80554baf058"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/YMpPZFZvLsXk3k9_puhfB9oZFck>
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:45:57 -0000

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> 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>
> 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
> > https://www.ietf.org/mailman/listinfo/6lo
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>