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

Carsten Bormann <cabo@tzi.org> Wed, 05 February 2014 21:14 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460CC1A024E for <roll@ietfa.amsl.com>; Wed, 5 Feb 2014 13:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] 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 7hZ_r41Itlbg for <roll@ietfa.amsl.com>; Wed, 5 Feb 2014 13:14:36 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0254B1A024B for <roll@ietf.org>; Wed, 5 Feb 2014 13:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s15LEFS5022646; Wed, 5 Feb 2014 22:14:15 +0100 (CET)
Received: from [192.168.217.101] (p54893DF9.dip0.t-ipconnect.de [84.137.61.249]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C93C5EFC; Wed, 5 Feb 2014 22:14:14 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8416FB771@xmb-rcd-x01.cisco.com>
Date: Wed, 05 Feb 2014 22:14:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB1485D5-FB11-4C1D-8077-A5930F1BB119@tzi.org>
References: <CAP+sJUfF-hs5+C-2F98Gaa9Sv_1fZcioUxVCaR2EN-y=5vDLwA@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD8416FB771@xmb-rcd-x01.cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1827)
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Ines Robles <mariainesrobles@googlemail.com>, "Jonathan Hui (johui)" <johui@cisco.com>
Subject: Re: [Roll] Intention for draft-thubert-roll-forwarding-frags
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
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: Wed, 05 Feb 2014 21:14:38 -0000

On 05 Feb 2014, at 19:05, Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:

> We presented the work at 6lo, but there was a mitigated reception.
> Carsten in particular opposed the work, and complained that it moved places,

Well, my complaint was not just about the fact that the same idea had been discussed in several places, but mainly that it already had received lukewarm to negative feedback in those places, but there had been little progress in the draft apparent when it turned up in the next place.

> plus has doubts about the retry mechanism

That is really the technical part of my and others’ skepticism.
Apart from the apparent redundancy with existing L2 ACK/retransmission mechanisms, one aspect was the unclear interaction of a multi-hop reliability scheme with transport timers.
More generally, there was skepticism that this approach actually yields improvements that are in line with the complexity it creates.
Having some observations from simulations or preferably real networks would be useful to dispel this impression.

But I agree with Ines, sub-IP encapsulation and reliability/performance is really outside ROLL’s scope.  6lo would actually be the right WG, but the technical question marks mentioned above would need to be addressed.

Grüße, Carsten