IETF Logo Mail Archive

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

Arjun Roychowdhury <arjunrc@gmail.com> Sun, 01 November 2009 21:09 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 6A75228C11A for <6lowapp@core3.amsl.com>; Sun, 1 Nov 2009 13:09:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 A03MClz8sNEN for <6lowapp@core3.amsl.com>; Sun, 1 Nov 2009 13:09:53 -0800 (PST)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id 7E3583A682B for <6lowapp@ietf.org>; Sun, 1 Nov 2009 13:09:53 -0800 (PST)
Received: by qw-out-2122.google.com with SMTP id 9so1167564qwb.31 for <6lowapp@ietf.org>; Sun, 01 Nov 2009 13:10:09 -0800 (PST)
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 :from:date:message-id:subject:to:cc:content-type; bh=UiRrPzbXCSg61cjCgDIw8B/gcCchtOHkv/wHEXMs4sc=; b=dtO5yG09jhGkfJZ7OSPaJaZwV2QBTHewuTt6OPDtNcIPEi/c+b0S8X2kaYEwWiydNv t6uiy/4ev/qtZ7lwMgjSLi0gfTvyL7hXtTo2y0W30EjsdYEUQ84S8D09S/tPNQh80EuP fiEMPUfDbDfjw/cPfufCj2c5eIYawXdBJirm0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=gTOykkEBjHvEBQNr+j5/jojErapu+YTeDHv3+Ireyehy1tqXOMHJPRrFQs0cNSffYW xakvz2cn8kKjjJoRKF/wcIXZxz71Kz5nhKcr5eW5TKQnw3Wsk+p0dq6mXwQ/9PmaW3Qf MQnuXE0Myhf3T5TzcUTMD3YrItJhp6iXBKro8=
MIME-Version: 1.0
Received: by 10.224.48.4 with SMTP id p4mr2426061qaf.231.1257109809255; Sun, 01 Nov 2009 13:10:09 -0800 (PST)
In-Reply-To: <4AEDC3FD.3040801@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> <A4C590B945EF374AB02BB6A2EAA4485808B4C76271@EXMBX01.apps4rent.net> <6C14D98B-4B4D-44B8-B8A5-1BEA5A8F443C@cisco.com> <4AEDC3FD.3040801@cisco.com>
From: Arjun Roychowdhury <arjunrc@gmail.com>
Date: Sun, 1 Nov 2009 16:09:49 -0500
Message-ID: <a9994e940911011309o6287b0d5r116bcf5329a1035c@mail.gmail.com>
To: paduffy@cisco.com
Content-Type: multipart/alternative; boundary=000fea892bfb9fd72c047755af61
X-Mailman-Approved-At: Mon, 02 Nov 2009 02:50:28 -0800
Cc: 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: Sun, 01 Nov 2009 21:09:54 -0000

On Sun, Nov 1, 2009 at 12:23 PM, Paul Duffy <paduffy@cisco.com> wrote:

> Hi Donn,
>
>
>  We welcome other suggestions like XMPP and SIP but we did look at those
>> and
>> ruled them out for reasons like:
>> 1)  Verboseness (using text string exchanges for devices with very small
>> transmit/receive packet sizes)
>> 2)  Session management overhead
>>
>>
>
>
> SIP in the Smart Grid HAN seems a fundamental misfit to SIPs chartered
> intent.
>
> But XMPP gives me pause...
>
>
ARC> Why is that so? SIP is a protocol to communicate between one or more
entities. The fact that it was originally designed to communicate between
users is much less important compared to the benefits its architecture
brings in. If people use SIP to create a recvonly session with an IP camera
in their house to monitor security from their IMS (SIP) enabled cell phone,
how is that different from controlling any other device?

v2.8.7 | Report a Bug | By Email