Re: [6tisch] [Roll] Intention for draft-thubert-roll-forwarding-frags

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 07 February 2014 15:26 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A021A8033; Fri, 7 Feb 2014 07:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=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 KpkKle2aAzL0; Fri, 7 Feb 2014 07:26:07 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id F15F51A8032; Fri, 7 Feb 2014 07:26:06 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2D5BC20028; Fri, 7 Feb 2014 11:43:11 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 48D8C647C9; Fri, 7 Feb 2014 10:26:05 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2D5EC63B88; Fri, 7 Feb 2014 10:26:05 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8A3F3C1F-4C4F-4BE7-A33D-5C52BA1D0913@tzi.org>
References: <CAP+sJUfF-hs5+C-2F98Gaa9Sv_1fZcioUxVCaR2EN-y=5vDLwA@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD8416FB771@xmb-rcd-x01.cisco.com> <5466.1391705016@sandelman.ca> <E045AECD98228444A58C61C200AE1BD8416FFE75@xmb-rcd-x01.cisco.com> <8A3F3C1F-4C4F-4BE7-A33D-5C52BA1D0913@tzi.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 07 Feb 2014 10:26:05 -0500
Message-ID: <31316.1391786765@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, Ines Robles <mariainesrobles@googlemail.com>, "6tisch@ietf.org" <6tisch@ietf.org>, "Jonathan Hui (johui)" <johui@cisco.com>
Subject: Re: [6tisch] [Roll] Intention for draft-thubert-roll-forwarding-frags
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 15:26:08 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    >> And then there is the capability to retry and do flow control over
    >fragment on a multihop forwarding plane. Forwarding fragments has this
    >side effect that 1 hop ARQ in the middle of a multihop forwarding plane
    >does not let the fragment source know that a fragment was abandoned
    >somewhere on the way. Incomplete packets are a bad idea in a constrained
    >node. Whether it is a good idea to protect fragments end-to -end over
    >the multihop LLN as opposed *or* on top of every hop is
    >debatable. Carsten opposes, and there were a number of other knee-jerk
    >reactions. But we need a people who understand forwarding and transport
    >to make the decision.

    > Right now, what we have is a clash of intuitions.  Many people are
    > thinking “won’t work”, “not needed”, “doesn’t improve”.  Others are
    > thinking that the new mechanisms would help.
    > As I said before, the only way to resolve this is getting data.

Sounds like experimental track to me.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works