Re: [recipe] Application layer

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 12 February 2010 19:30 UTC

Return-Path: <hgs@cs.columbia.edu>
X-Original-To: recipe@core3.amsl.com
Delivered-To: recipe@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D2243A7852 for <recipe@core3.amsl.com>; Fri, 12 Feb 2010 11:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gPi+OwCljyxK for <recipe@core3.amsl.com>; Fri, 12 Feb 2010 11:30:11 -0800 (PST)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 1A3A83A7736 for <recipe@ietf.org>; Fri, 12 Feb 2010 11:30:10 -0800 (PST)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o1CJVHM2023701 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 12 Feb 2010 14:31:17 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <E6ECE1AC-1573-42A6-94D0-EDD8DD1B32F1@cisco.com>
Date: Fri, 12 Feb 2010 14:31:17 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <F00404F5-9A41-427C-A60D-264ED1547F48@cs.columbia.edu>
References: <968747.90846.qm@web51302.mail.re2.yahoo.com> <E6ECE1AC-1573-42A6-94D0-EDD8DD1B32F1@cisco.com>
To: JP Vasseur <jvasseur@cisco.com>
X-Mailer: Apple Mail (2.1077)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: recipe@ietf.org
Subject: Re: [recipe] Application layer
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/recipe>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2010 19:30:12 -0000

Who defines/defined "SE 2.0"?

On Feb 12, 2010, at 1:54 PM, JP Vasseur wrote:

> Hi,
> 
> On Feb 12, 2010, at 9:25 AM, Tom Herbst wrote:
> 
>> Not sure I understand Zigbee vs v6/lowpan since all of the
>> work being done on Smart Energy 2.0 is v6/6lowpan and
>> either tcp/http or COAP provided RESTful api.
>> 
>> Several of the people defining this will be in Anaheim.
>> 
> 
> +1. SE 2.0 brings the convergence that we were looking for.
> SE 2.0 is using IP.
> 
> JP.
> 
>> tom
>> 
>> --- On Thu, 2/11/10, Henning Schulzrinne <hgs@cs.columbia.edu>; wrote:
>> 
>>> From: Henning Schulzrinne <hgs@cs.columbia.edu>;
>>> Subject: [recipe] Application layer
>>> To: recipe@ietf.org
>>> Date: Thursday, February 11, 2010, 7:55 PM
>>> Bruce Nordman and I have been
>>> discussing whether we should re-convene a Bar BOF in
>>> Anaheim, focusing on topics beyond the usual Zigbee-vs.-IPv6
>>> or LowPAN discussions. In particular, I think that the
>>> current stovepipe application layers (e.g., in BACS and the
>>> other control-oriented building networks) are not very
>>> helpful as a long-term architecture. We also might want to
>>> think about the interfaces that need to be exposed - we
>>> don't want our architecture to look like the 3GPP diagram...
>>> (If you've taken a look at the NIST interface diagram for
>>> the smart grid, this comparison is not purely theoretical,
>>> although obviously the protocols are completely different.)
>>> 
>>> Does this sound like something of interest?
>>> 
>>> (There is some work in the SIP Forum context, but this is
>>> not [just] about a particular protocol.)
>>> 
>>> Henning
>>> _______________________________________________
>>> recipe mailing list
>>> recipe@ietf.org
>>> https://www.ietf.org/mailman/listinfo/recipe
>>> 
>> _______________________________________________
>> recipe mailing list
>> recipe@ietf.org
>> https://www.ietf.org/mailman/listinfo/recipe
> 
>