[6lowpan] piggybacked fragment ACKs
Richard Kelsey <richard.kelsey@ember.com> Wed, 24 June 2009 20:20 UTC
Return-Path: <richard.kelsey@ember.com>
X-Original-To: 6lowpan@core3.amsl.com
Delivered-To: 6lowpan@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0EC13A6CE6 for <6lowpan@core3.amsl.com>; Wed, 24 Jun 2009 13:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3paWAesGqz17 for <6lowpan@core3.amsl.com>; Wed, 24 Jun 2009 13:20:52 -0700 (PDT)
Received: from EMPIRE.hq.ember.com (mail.ember.com [74.10.175.227]) by core3.amsl.com (Postfix) with ESMTP id 06CD33A6ABF for <6lowpan@ietf.org>; Wed, 24 Jun 2009 13:20:51 -0700 (PDT)
Received: from kelsey-ws.hq.ember.com ([192.168.81.60]) by EMPIRE.hq.ember.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Jun 2009 16:18:57 -0400
Date: Wed, 24 Jun 2009 16:19:11 -0400
Message-Id: <87prctxu4g.fsf@kelsey-ws.hq.ember.com>
To: pthubert@cisco.com
From: Richard Kelsey <richard.kelsey@ember.com>
X-OriginalArrivalTime: 24 Jun 2009 20:18:57.0480 (UTC) FILETIME=[00DD8C80:01C9F509]
Cc: 6lowpan@ietf.org
Subject: [6lowpan] piggybacked fragment ACKs
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2009 20:20:52 -0000
Pascal,
In the past I have found it very useful to be able to
piggyback ACKs on other traffic. From reading RFC4944 and
draft-thubert-6lowpan-simple-fragment-recovery-05 it looks
like there should be no problem prepending an RFRAG-ACK
header at the beginning of a LoWPAN datagram, as RFC4944
does with various other headers. On the other hand, I can't
find anything that explictly allows this. Do you see any
difficulty with piggybacking RFRAG-ACKs on other packets?
-Richard Kelsey
- [6lowpan] piggybacked fragment ACKs Richard Kelsey
- Re: [6lowpan] piggybacked fragment ACKs Carsten Bormann
- Re: [6lowpan] piggybacked fragment ACKs Pascal Thubert (pthubert)
- Re: [6lowpan] piggybacked fragment ACKs Pascal Thubert (pthubert)
- Re: [6lowpan] piggybacked fragment ACKs Richard Kelsey
- Re: [6lowpan] piggybacked fragment ACKs Richard Kelsey
- Re: [6lowpan] piggybacked fragment ACKs Pascal Thubert (pthubert)