Re: [6lowapp] HTTP and SIP

Adam Dunkels <adam@sics.se> Mon, 12 October 2009 11:14 UTC

Return-Path: <adam@sics.se>
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 8F67028C19E for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.76
X-Spam-Level:
X-Spam-Status: No, score=-0.76 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_SE=0.35]
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 zU69NYEFJ7SH for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:14:30 -0700 (PDT)
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by core3.amsl.com (Postfix) with ESMTP id 2056528C19C for <6lowapp@ietf.org>; Mon, 12 Oct 2009 04:14:30 -0700 (PDT)
Received: from [10.1.1.254] (unknown [10.1.1.254]) by letter.sics.se (Postfix) with ESMTP id BC2C440124; Mon, 12 Oct 2009 13:14:28 +0200 (CEST)
Message-ID: <4AD30F8E.3090800@sics.se>
Date: Mon, 12 Oct 2009 13:14:22 +0200
From: Adam Dunkels <adam@sics.se>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "zach@sensinode.com" <zach@sensinode.com>
References: <429b380e0910101030q25f1ad7fge7157c2e04b5d530@mail.gmail.com> <4AD105DC.3070407@sics.se> <-3576688268114842355@unknownmsgid> <429b380e0910101840r93129edmae938b4c20eba50f@mail.gmail.com> <51a935134ec43c777faff0894070d2a9@mailserver13.nebula.fi>
In-Reply-To: <51a935134ec43c777faff0894070d2a9@mailserver13.nebula.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] HTTP and SIP
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: Mon, 12 Oct 2009 11:14:31 -0000

zach@sensinode.com wrote:
> On Sat, 10 Oct 2009 21:40:41 -0400, Shidan <shidan@gmail.com> wrote: 
>> I'm pretty convinced that with the RIGHT sort of optimizations, any
> latency
>> issues can be handled without having to dictating general architectural
>> standards like using REST, SNMP, SIP, etc. which can stifle innovation
> and
>> lead to building everything with a hammer.
> 
> I think there is confusion about the word REST in the charter. This 
> is only meant to mean that if you want to proxy with HTTP and support 
> the design of web-services reusing existing techniques - then we need to 
> support GET, PUT, POST, DELETE methods. Maybe it is better to 
> remove the word REST if that implies anything more than that to people? 

Using the acronym REST may be a little difficult because many strongly 
associate it with HTTP, even if the actual architectural principles do 
not necessarily have to be implemented over HTTP.

/adam
-- 
Adam Dunkels <adam@sics.se>se>, +46707731614
http://twitter.com/adunk | http://www.sics.se/~adam/