IETF Logo Mail Archive

Re: [solace] Notes from the SOLACE ad-hoc at IETF85

"Eggert, Lars" <lars@netapp.com> Mon, 05 November 2012 15:26 UTC

Return-Path: <lars@netapp.com>
X-Original-To: solace@ietfa.amsl.com
Delivered-To: solace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9CD21F88A9 for <solace@ietfa.amsl.com>; Mon, 5 Nov 2012 07:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.492
X-Spam-Level:
X-Spam-Status: No, score=-10.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxWqcYSDPW-X for <solace@ietfa.amsl.com>; Mon, 5 Nov 2012 07:26:16 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id C671921F8848 for <solace@ietf.org>; Mon, 5 Nov 2012 07:26:15 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.80,715,1344236400"; d="p7s'?scan'208"; a="707141528"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 05 Nov 2012 07:26:15 -0800
Received: from vmwexceht01-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id qA5FQEpf018672; Mon, 5 Nov 2012 07:26:14 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 07:26:14 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: [solace] Notes from the SOLACE ad-hoc at IETF85
Thread-Index: AQHNutarhs45Au1HOEGyiLH1vKfP75fb5DaA
Date: Mon, 05 Nov 2012 15:25:27 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9185D66DE@SACEXCMBX01-PRD.hq.netapp.com>
References: <105963F3-4106-43D4-8F63-5478B617BE36@tzi.org>
In-Reply-To: <105963F3-4106-43D4-8F63-5478B617BE36@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_EA8844F3-7A2F-41A5-8EA9-30AAF411B619"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "solace@ietf.org" <solace@ietf.org>
Subject: Re: [solace] Notes from the SOLACE ad-hoc at IETF85
X-BeenThere: solace@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "\"Smart Object Lifecycle Architecture for Constrained Environments\" discussion list" <solace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/solace>, <mailto:solace-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/solace>
List-Post: <mailto:solace@ietf.org>
List-Help: <mailto:solace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/solace>, <mailto:solace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 15:26:16 -0000

Hi,

just for the record, I'd be very supportive of seeing this under the IRTF. But it's in the end obviously the call of the folks who will do the work.

Lars

On Nov 4, 2012, at 16:52, Carsten Bormann <cabo@tzi.org> wrote:
> 1) What is the best home for SOLACE?
> 
> One approach is to find a home in IRTF.
> Several participants agreed: 
> -- this spans a couple of areas
> -- IRTF can work in a relatively "sheltered" way
> -- there may less of a need to go through an excruciating chartering
>   process before we really understand the specific shape of the
>   result that we can achieve
> 
> Other participants pointed out:
> -- an IETF activity may be more focused on directly usable results
> -- there are specific gaps such as the OLSRv2 security model that need
>   input soon
> -- there might even be a new M2M area in the IETF
> 
> Clearly, there wasn't consensus yet, but some more people leaned
> towards the IRTF approach.  This requires further discussion.
> Ulrich, Yoshihiro, and Carsten volunteered for working on a potential
> charter for a new group.

v2.23.0 | Report a Bug | By Email