Re: [6lowapp] Proposed charter for 6LoWAPP BOF

Arjun Roychowdhury <arjun.lists@hsc.com> Thu, 29 October 2009 19:25 UTC

Return-Path: <arjunrc@gmail.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 032883A6899 for <6lowapp@core3.amsl.com>; Thu, 29 Oct 2009 12:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 oYOIdvkYFDHY for <6lowapp@core3.amsl.com>; Thu, 29 Oct 2009 12:25:38 -0700 (PDT)
Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id EE8C03A6867 for <6lowapp@ietf.org>; Thu, 29 Oct 2009 12:25:37 -0700 (PDT)
Received: by qyk41 with SMTP id 41so1392544qyk.29 for <6lowapp@ietf.org>; Thu, 29 Oct 2009 12:25:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=tAinFlQLXOc6Hm6V+MSpafU7VmVS13lvtxF0Pwbuglw=; b=v2ayqMc5Hdj5dZ7jla2IumuBVq1Q26qzhFoAVFLYVZ2W0IxoWamkpcCoWgxAr7CCFY 8ZGH4OkRnGIZ1Bg7pPYMaHsjsPnjGdEc9kA/ZhJTVVPjEJTvy4uLxrBEtSY6zi/8eim9 dN3sPYIP9AHbmG+RRtwkafFrjRqPnlB7+DlCA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=a7veFhYrfCbKG0To/JUkuvTvU8n7tn+toGvxwBbgI90obhtbrEuzptuniiUUjA98nO B6BBF8j7bYF6rvC4ENon2voQOCUgN6wrjF2a9Mb7vusXPeMPtPyM18tL0tuo2ZIj3YaI 9EvSMffC8aqZhQcbDoguP7FrGpLo/tE66LpG4=
MIME-Version: 1.0
Sender: arjunrc@gmail.com
Received: by 10.224.52.144 with SMTP id i16mr280330qag.210.1256844351354; Thu, 29 Oct 2009 12:25:51 -0700 (PDT)
In-Reply-To: <ca722a9e0910291210u3898dda6p4752b3cd5f000ba7@mail.gmail.com>
References: <B27B00F8-1A4F-4258-86FC-C02E78778E45@cisco.com> <184E130A-881A-4E1F-8408-FB03A7849A82@sensinode.com> <CE5B892A-3699-4CBF-8B6A-588F5A7DE99A@cisco.com> <EB735931-0D15-4017-94F1-3B10A0EC814D@sensinode.com> <843F0B9E-8C62-47A6-AFEC-4BE31D62CDB5@cisco.com> <2AA1E2A3-9EA9-4B94-85BA-834C66826A85@tzi.org> <C93E77B9-349F-451C-BAED-273555EEE5DE@cisco.com> <a9994e940910291111r5523e6eer581313f8fee12cba@mail.gmail.com> <ca722a9e0910291210u3898dda6p4752b3cd5f000ba7@mail.gmail.com>
From: Arjun Roychowdhury <arjun.lists@hsc.com>
Date: Thu, 29 Oct 2009 15:25:31 -0400
X-Google-Sender-Auth: 8f7ce363124b6788
Message-ID: <a9994e940910291225w1064dad4i6799a5b86fa35ea7@mail.gmail.com>
To: Lisa Dusseault <lisa.dusseault@gmail.com>
Content-Type: multipart/alternative; boundary=00c09f89999b19b779047717e164
Cc: Don Sturek <donsturek@grid2home.com>, 6lowapp@ietf.org
Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: arjun.lists@hsc.com
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: Thu, 29 Oct 2009 19:25:39 -0000

Hi Lisa, responses inlined.
regds
arjun


On Thu, Oct 29, 2009 at 3:10 PM, Lisa Dusseault <lisa.dusseault@gmail.com>wrote;wrote:

>
> focused WG charter because this isn't "the charter for low-power IP
> applications protocols" it's merely *a* charter for a subset of those
> things.  We can't boil the ocean in one WG or even come to agreement
> on forming a WG if the scope is too big.  Besides considering that
> other WGs can tackle this larger space, consider that this WG could
> always go on to more complex use cases after solving simple ones.
>

ARC> I think this comment pretty much summarizes the difference of thought
between what I thought 6lowapp vs doing vs what you are describing. The
group name itself, "6lowapp" seems to specify it is a group to to specificy
low-power IP app protocols, and not a
subset. draft-bormann-6lowpan-6lowapp-problem-01 also seems to indicate this
group is dealing with the larger set.

So my comment would be if this is not so, then it needs to be explicitly
stated, otherwise the natural understanding is 6lowapp is the application
protocol group for 6lowpan devices - and what comes out of here, would
likely be adopted going forward in deployments,

I can respond to your other comments in more detail, but then again, if the
scope is going to be limited, then so be it.

-- 
Arjun Roychowdhury