IETF Logo Mail Archive

Re: [6lowapp] HTTP and SIP

Carsten Bormann <cabo@tzi.org> Mon, 12 October 2009 11:22 UTC

Return-Path: <cabo@tzi.org>
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 61AAE28C1B6 for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 oGw+eLYtgyyT for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:22:38 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 5F08228C19C for <6lowapp@ietf.org>; Mon, 12 Oct 2009 04:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id n9CBMZqb004753; Mon, 12 Oct 2009 13:22:35 +0200 (CEST)
Received: from [10.0.1.198] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id 167A9B4C1; Mon, 12 Oct 2009 13:22:35 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
To: Adam Dunkels <adam@sics.se>
In-Reply-To: <4AD30F8E.3090800@sics.se>
References: <429b380e0910101030q25f1ad7fge7157c2e04b5d530@mail.gmail.com> <4AD105DC.3070407@sics.se> <-3576688268114842355@unknownmsgid> <429b380e0910101840r93129edmae938b4c20eba50f@mail.gmail.com> <51a935134ec43c777faff0894070d2a9@mailserver13.nebula.fi> <4AD30F8E.3090800@sics.se>
Message-Id: <10698EC2-72B2-47F4-B277-11D62DEAE7EC@tzi.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 12 Oct 2009 13:22:34 +0200
X-Mailer: Apple Mail (2.936)
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:22:39 -0000

On Oct 12, 2009, at 13:14, Adam Dunkels wrote:

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

I think that is indeed the interesting part, nicely isolated as such  
by Roy Fielding's dissertation.
So, the $64000 question:
What are the architectural principles of SIP, SNMP, XMPP, etc. that we  
are interested in for a constrained-node/-network transfer protocol?

Gruesse, Carsten

v2.8.7 | Report a Bug | By Email