IETF Logo Mail Archive

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

Arjun Roychowdhury <arjun.lists@hsc.com> Sun, 01 November 2009 21:12 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 3505D3A6869 for <6lowapp@core3.amsl.com>; Sun, 1 Nov 2009 13:12:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level:
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.100, 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 4sDuxB6rzcjJ for <6lowapp@core3.amsl.com>; Sun, 1 Nov 2009 13:12:47 -0800 (PST)
Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id 5E1713A682B for <6lowapp@ietf.org>; Sun, 1 Nov 2009 13:12:47 -0800 (PST)
Received: by qyk41 with SMTP id 41so2333442qyk.29 for <6lowapp@ietf.org>; Sun, 01 Nov 2009 13:13:04 -0800 (PST)
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=cIc2Uxm8TFHgyNMiXSvG+OwCyvMElRey5+DBiBzDA+0=; b=xMNAnU4HX4AxVoR9qjnY9nytBquqLKcdHjDxoEAGJK/mPooJ/k/GQmaGw08Kdf87/L P2Md8QzR/qIP0+jeoAvz9QiyEBdnq6GSTPZTSwd0qAyGpbve+YzdVcS7wF1KSkfgnPH/ H6q9cTFFY4U93y13/eHpn6zf9PiV5vD3S00E0=
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=nywpxwjrzqBu890+ErfIqb9w1gj295QsHt1x5dY2BxfzlJYNcs4J4n7ZtY2fT/7tfD wUD+S6bMlqYNfeG+4ahoqZ7I62U6Td/VnlADVpIx3HRPe86Pz7ouF5/ptbDlKEnP4wuh 6sbXk6UXzLIEdOD9iU2yTmCrXKDHojXZdiR6k=
MIME-Version: 1.0
Sender: arjunrc@gmail.com
Received: by 10.224.117.12 with SMTP id o12mr2455408qaq.57.1257109984083; Sun, 01 Nov 2009 13:13:04 -0800 (PST)
In-Reply-To: <a9994e940911011309o6287b0d5r116bcf5329a1035c@mail.gmail.com>
References: <B27B00F8-1A4F-4258-86FC-C02E78778E45@cisco.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> <a9994e940911011309o6287b0d5r116bcf5329a1035c@mail.gmail.com>
From: Arjun Roychowdhury <arjun.lists@hsc.com>
Date: Sun, 1 Nov 2009 16:12:44 -0500
X-Google-Sender-Auth: e2f46f7acce21f31
Message-ID: <a9994e940911011312g22582a3dpcbf0978755758aa@mail.gmail.com>
To: paduffy@cisco.com
Content-Type: multipart/alternative; boundary=000feaebb2ea0b7f21047755ba7d
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
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: Sun, 01 Nov 2009 21:12:48 -0000

responding from my subscribed email id incase the previous one does not make
it to this list:

On Sun, Nov 1, 2009 at 4:09 PM, Arjun Roychowdhury <arjunrc@gmail.com>wrote;wrote:

>
>>
>> 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?




-- 
Arjun Roychowdhury

v2.8.7 | Report a Bug | By Email