Re: [6lowapp] Architecture Sketch in Charter

Carsten Bormann <cabo@tzi.org> Tue, 03 November 2009 22:19 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 9FEBA3A6822 for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 14:19:02 -0800 (PST)
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=[AWL=-0.000, 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 N6A5HMnq8HSV for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 14:19:01 -0800 (PST)
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 868733A67A2 for <6lowapp@ietf.org>; Tue, 3 Nov 2009 14:19:01 -0800 (PST)
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 nA3MIUbU008623; Tue, 3 Nov 2009 23:18:31 +0100 (CET)
Received: from [192.168.217.101] (p5489FD7F.dip.t-dialin.net [84.137.253.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id CCA0CB194; Tue, 3 Nov 2009 23:18:29 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <429b380e0911031348x4c9985a8sd554f5c322836c24@mail.gmail.com>
Date: Tue, 3 Nov 2009 23:18:27 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <F4612C4F-98F4-4D1C-B81E-E683FAA0448C@tzi.org>
References: <D53A5549-FE08-460B-91D9-673DB9C81720@cisco.com> <429b380e0910311541ve2666fcjdc27d63aaddb696@mail.gmail.com> <DBFDAD96-5F5D-41DE-9BA0-B0326BFDFF73@cisco.com> <429b380e0911031348x4c9985a8sd554f5c322836c24@mail.gmail.com>
To: Shidan <shidan@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Architecture Sketch in Charter
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: Tue, 03 Nov 2009 22:19:02 -0000

On Nov 3, 2009, at 22:48, Shidan wrote:

> Everything

The idea behind CoAP (Constrained-node/network Application Protocol)  
is to have something very simple, very basic, that can be used to run  
applications that involve constrained IP nodes on constrained  
networks.  "Everything" is not the first word that comes to my mind  
here.  I'd prefer "Do the simplest thing that could possibly work".   
(That is actually a googleable phrase.)

Gruesse, Carsten