Re: [6lowapp] Revised Charter Proposal

"Stuber, Michael" <Michael.Stuber@itron.com> Wed, 27 January 2010 17:58 UTC

Return-Path: <Michael.Stuber@itron.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64ECB3A6869 for <6lowapp@core3.amsl.com>; Wed, 27 Jan 2010 09:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 poZawTRc1fDc for <6lowapp@core3.amsl.com>; Wed, 27 Jan 2010 09:58:19 -0800 (PST)
Received: from mailer-1.itron.com (mailer-1.itron.com [198.182.8.123]) by core3.amsl.com (Postfix) with ESMTP id 968283A690D for <6lowapp@ietf.org>; Wed, 27 Jan 2010 09:58:19 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Jan 2010 09:58:33 -0800
Message-ID: <05C6A38D732F1144A8C4016BA4416BFE02759CFB@SPO-EXVS-02.itron.com>
In-Reply-To: <3fe58b591001251042h3c8ef221hdb1716405fd10d91@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [6lowapp] Revised Charter Proposal
Thread-Index: Acqd7jqy9+83l3hbRCmbFtQ4zKGQKQBjA8zA
References: <0C0AF10C-85F8-4401-BFB0-441CD08F067E@cisco.com><8CFA798E-123D-4A10-8961-8D47B3EE3A34@cisco.com> <3fe58b591001251042h3c8ef221hdb1716405fd10d91@mail.gmail.com>
From: "Stuber, Michael" <Michael.Stuber@itron.com>
To: 6lowapp@ietf.org
Subject: Re: [6lowapp] Revised Charter Proposal
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2010 17:58:20 -0000

Absolutely agree.  +1

-----Original Message-----
From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On
Behalf Of Kerry Lynn
Sent: Monday, January 25, 2010 10:43 AM
To: Cullen Jennings
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Revised Charter Proposal

Cullen,

I, for one, am nervous about deferring a naming and discovery approach
and feel that this is important to interoperable implementations.  Not
sure I see the value of creating a framework for defining new profiles
and interface objects, if there's no consistent way to name and discover
them.

Regards, -K-

On Mon, Jan 25, 2010 at 12:38 PM, Cullen Jennings <fluffy@cisco.com>
wrote:
>
> I think I made one (or at least one) big mistake in this charter
update. At the end of the BOF, there was clear consensus to make the
initial charter thorough out everything but the minimal approach.
(Basically Ted Hardie's proposal). I thought I had done this but realize
in going back and listening to the BOF recording that this included
leaving the discovery stuff to a later time. I think I need to update
the charter to move the discovery work to not be in the initial scope of
work.
>
_______________________________________________
6lowapp mailing list
6lowapp@ietf.org
https://www.ietf.org/mailman/listinfo/6lowapp