[6lowpan] Call for working group adoption (Re: making progress on fragmentation)
Carsten Bormann <cabo@tzi.org> Tue, 18 August 2009 13:26 UTC
Return-Path: <cabo@tzi.org>
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 985CA28C144 for <6lowpan@core3.amsl.com>; Tue, 18 Aug 2009 06:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.879
X-Spam-Level:
X-Spam-Status: No, score=-5.879 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 Asyxj3lYTu9c for <6lowpan@core3.amsl.com>; Tue, 18 Aug 2009 06:26:42 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 4628328C140 for <6lowpan@ietf.org>; Tue, 18 Aug 2009 06:26:41 -0700 (PDT)
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.3/8.14.3) with ESMTP id n7IDQWNs022446; Tue, 18 Aug 2009 15:26:32 +0200 (CEST)
Received: from [192.168.217.101] (p5489F20B.dip.t-dialin.net [84.137.242.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id AD319BC2E; Tue, 18 Aug 2009 15:26:31 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
To: 6lowpan <6lowpan@ietf.org>
In-Reply-To: <87ljlh2tpx.fsf@kelsey-ws.hq.ember.com>
References: <87ljlh2tpx.fsf@kelsey-ws.hq.ember.com>
Message-Id: <4186F14A-435F-4C74-9D31-31BF03A6C1A2@tzi.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 18 Aug 2009 15:26:30 +0200
X-Mailer: Apple Mail (2.936)
Subject: [6lowpan] Call for working group adoption (Re: making progress on fragmentation)
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: Tue, 18 Aug 2009 13:26:43 -0000
Richard, thank you for seconding Pascal's draft. We have had multiple discussions of the fragment recovery drafts in IETF meetings. Each time, we found some aspect some of us didn't like, and then Pascal submitted an updated version solving that problem. The only thing that got considerable push-back this time was that the draft shouldn't try to deprecate 4944's fragment headers. I think this is a statement that could easily be taken out in a working group draft submission. (Of course, any other technical wrinkles can be ironed out during the period the document is a WG draft.) So I would like to take the opportunity to ask here on the mailing list whether we should adopt http://tools.ietf.org/html/draft-thubert-6lowpan-simple-fragment-recovery-06 (with the abovementioned change) as a working group document. --> If you want to advance this draft, please indicate your support on the mailing list. If you think this is a bad idea, please say so, too. (I would like to receive responses by this Friday, Aug 21, as I'm going on vacation after that.) Note that we also have to hear from our AD on this item, as it is not formally on our charter. A year ago, Mark Townsley gave us some form of go ahead when we discussed whether we should be delaying the charter for adding this as a work item. He said that waiting wasn't necessary, and we were free to start work. http://www.mail-archive.com/6lowpan@ietf.org/msg01114.html Still, we would need to add a line item under the deliverables, and our new AD would have to concur -- which is probably easiest after the yays and nays. Gruesse, Carsten
- [6lowpan] making progress on fragmentation Richard Kelsey
- [6lowpan] Call for working group adoption (Re: ma… Carsten Bormann
- Re: [6lowpan] Call for working group adoption (Re… Ralph Droms
- Re: [6lowpan] making progress on fragmentation Carsten Bormann
- Re: [6lowpan] making progress on fragmentation Richard Kelsey
- Re: [6lowpan] making progress on fragmentation Richard Kelsey
- Re: [6lowpan] making progress on fragmentation Carsten Bormann
- Re: [6lowpan] making progress on fragmentation Pascal Thubert (pthubert)
- Re: [6lowpan] Call for working group adoption (Re… Carsten Bormann
- Re: [6lowpan] Call for working group adoption (Re… Richard Kelsey
- Re: [6lowpan] making progress on fragmentation Pascal Thubert (pthubert)
- Re: [6lowpan] making progress on fragmentation Richard Kelsey
- Re: [6lowpan] making progress on fragmentation Pascal Thubert (pthubert)
- Re: [6lowpan] making progress on fragmentation Richard Kelsey
- Re: [6lowpan] making progress on fragmentation Pascal Thubert (pthubert)