Re: [6lowpan] A suggestion ... With regards to re-chartering

Geoff Mulligan <ietf08@mulligan.org> Fri, 30 May 2008 19:18 UTC

Return-Path: <6lowpan-bounces@ietf.org>
X-Original-To: 6lowpan-archive@megatron.ietf.org
Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083343A6891; Fri, 30 May 2008 12:18:21 -0700 (PDT)
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 E61E63A687B for <6lowpan@core3.amsl.com>; Fri, 30 May 2008 12:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.105
X-Spam-Level:
X-Spam-Status: No, score=0.105 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, RDNS_NONE=0.1]
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 vJRjGW-DkVmJ for <6lowpan@core3.amsl.com>; Fri, 30 May 2008 12:18:18 -0700 (PDT)
Received: from grab.coslabs.com (unknown [199.233.92.34]) by core3.amsl.com (Postfix) with ESMTP id 97DF73A6891 for <6lowpan@ietf.org>; Fri, 30 May 2008 12:18:18 -0700 (PDT)
Received: from [199.233.92.20] (dev20.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.13.6/8.13.6) with ESMTP id m4UJIBPP020836; Fri, 30 May 2008 13:18:11 -0600 (MDT)
From: Geoff Mulligan <ietf08@mulligan.org>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC05C0E73A@xmb-ams-337.emea.cisco.com>
References: <C465321D.3E894%jvasseur@cisco.com> <7892795E1A87F04CADFCCF41FADD00FC05C0E73A@xmb-ams-337.emea.cisco.com>
Date: Fri, 30 May 2008 13:18:06 -0600
Message-Id: <1212175086.9165.6.camel@dellx1>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1.1
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] A suggestion ... With regards to re-chartering
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 6lowpan-bounces@ietf.org
Errors-To: 6lowpan-bounces@ietf.org

I basically agree with Pascal.  I think that we have a good start on
items 1, 3 and 5.  As for security we have a commitment from Shouichi
and Robert to take the draft from Daniel and complete it.

I think that we should move forward with HC1g as part of the 4944
improvement and maintenance.

	geoff


On Fri, 2008-05-30 at 14:48 +0200, Pascal Thubert (pthubert) wrote:
> Hi JP
> 
> Works with me. I went through the published work and the recent thread "
> New charter for 6lowpan".
> My conclusion is as follows:
> 
> >From the reworked charter, we should keep Work Items 1, 3, and 5 which
> appear of foremost importance, drop 2 and 4 because pragmatically we are
> not advanced enough in these areas.
> 
> For 1) we have draft-chakrabarti-6lowpan-ipv6-nd that we can couple with
> draft-thubert-6lowpan-backbone-router and we have most of the content we
> need to make a standard track doc.
> 
> For 3) we have draft-culler-6lowpan-architecture. It needs improvement
> in particular in explaining route over vs. mesh under in details as we
> currently discuss in the ML. Also mobility, backbone... but we have
> people interested in the discussion (see current threads) so we should
> work it out.
> 
> For 5) we have draft-daniel-6lowpan-security-analysis. We need to make
> sure we have people committed to the effort but the current draft looks
> good already.
> 
> To those 3, I'd add:
> 
> Explore requirements and usages.
> ---------------------------------
> We have a draft, draft-ekim-6lowpan-scenarios that we can leverage. I'd
> add to it some words on existing standards that need or use 6LowPAN. In
> particular, we need to place ISA100 requirements in there to be able to
> better serve them later.
> 
> RFC 4944 maintenance and improvements
> -------------------------------------
> This should cover at least 6lowpan HC and fragment recovery efforts. We
> can discuss if we want ECN in that work item as well. 
> 
> What do you think?
> 
> Pascal
> ________________________________________
> From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On
> Behalf Of Jean Philippe Vasseur (jvasseur)
> Sent: vendredi 30 mai 2008 04:25
> To: 6lowpan@ietf.org
> Subject: [6lowpan] A suggestion ... With regards to re-chartering
> 
> Hi,
> 
> Just a suggestion for the chairs and the WG. 
> 
> We have discussed many important items for 6lowpan. 
> 
> For several of them, all important, I think that there was a clear
> agreement: stateful header compression, security, Architecture ID,
> fragmentation, ..... For other ones such as the "Mesh-under" and "Route
> over" discussion, there are diverging point of views.
> 
> So why not trying to quickly re-charter adding the items for which there
> is a consensus and continue the discussion on the open issues in the
> meantime until we have an agreement at which point the WG may re-charter
> ?
> 
> As we all know, the WG has been fairly slow in term of progress and it
> is I think now urgent to move on.
> 
> Thoughts ?
> 
> Thanks.
> 
> JP. 
> _______________________________________________
> 6lowpan mailing list
> 6lowpan@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowpan

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan