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

Shidan <shidan@gmail.com> Sat, 31 October 2009 18:33 UTC

Return-Path: <shidan@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 B71913A6782 for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 11:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level:
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, 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 dTcoKsPf9eNt for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 11:33:22 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by core3.amsl.com (Postfix) with ESMTP id 941753A67F1 for <6lowapp@ietf.org>; Sat, 31 Oct 2009 11:33:21 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 25so193675eya.51 for <6lowapp@ietf.org>; Sat, 31 Oct 2009 11:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hXmeEQuH8KhzXnG40gG8dlsN4a/aeTmZt8yidTwCRjw=; b=Z/pfIFguAyvj1jEk3UxcPQMRg87epZIt3y4Uy4IkErFM3Yh2Dap/gN3yV9AViNG6sb nLV0VC1u8ovi0rejuP6VHkL2t+mJhxRp9TZC239y2jzeBEArWwJ3nGM6aJw+q3eZWg7z sT0+X7VAhVC+eKiWshZCuzcSHaMNfqIiP/1vI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GIEalxq1L6kz67Mvoml2bOK6Q++ftqaMMVWyKxmoxgPcYvDEvPOSuKxKOciY27OUsH wgx7Xl6qQ7B0ql6JBdvxhAyisQqaANZb32QfZmA1SeVpII2OI3gKZW6AEJY0LxJhvEtn N8PBrGf3D227ZJYNDOP/HbYLKQs61h8SKb38I=
MIME-Version: 1.0
Received: by 10.216.93.12 with SMTP id k12mr2046308wef.195.1257014016241; Sat, 31 Oct 2009 11:33:36 -0700 (PDT)
In-Reply-To: <71DDE42E-E6D4-49D7-8F2E-699FBBDBAC12@cisco.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> <71DDE42E-E6D4-49D7-8F2E-699FBBDBAC12@cisco.com>
Date: Sat, 31 Oct 2009 14:33:36 -0400
Message-ID: <429b380e0910311133k784f8fe8w878f81560fc28800@mail.gmail.com>
From: Shidan <shidan@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=0016e6d99f38ea709d04773f613b
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
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: Sat, 31 Oct 2009 18:33:22 -0000

Hi Cullen, I would check the motivational draft Arjun and I submitted for
SIP.


> OK - The way I want to try and derive us towards a decision here is get a
> list of candidate protocols then for each one ask the yes/no is the their
> agreement that we should do a mapping to that protocol.  The protocols I
> have heard so far are HTTP, SNMP,  SMTP. So two questions
>

1) what other protocols mapping should we do?
>

In general there are many practical applications which are using SIP and
XMPP for M2M communications. This should be a consideration.


>
> 2) Given some people want HTTP, can you live with the answer to HTTP being
> yes and understanding that just because we said yes to HTTP does not mean we
> are saying no to everything else?
>
>
Personally, I think HTTP is the most important and minimum protocol to
support.