Re: [solace] Will this IRTF group proceed?

Carsten Bormann <cabo@tzi.org> Thu, 14 March 2013 16:26 UTC

Return-Path: <cabo@tzi.org>
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 4AC1C11E8103 for <solace@ietfa.amsl.com>; Thu, 14 Mar 2013 09:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.45
X-Spam-Level:
X-Spam-Status: No, score=-105.45 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3KTu4ncgQWf for <solace@ietfa.amsl.com>; Thu, 14 Mar 2013 09:26:33 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 214EC21F8F81 for <solace@ietf.org>; Thu, 14 Mar 2013 09:26:32 -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.4/8.14.4) with ESMTP id r2EGQROv022312; Thu, 14 Mar 2013 17:26:27 +0100 (CET)
Received: from dhcp-9032.meeting.ietf.org (dhcp-9032.meeting.ietf.org [130.129.8.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 64A4E35F6; Thu, 14 Mar 2013 17:26:27 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7047.1363231468@sandelman.ca>
Date: Thu, 14 Mar 2013 17:26:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF0F7B1-C84D-403D-918B-10C7EF18FC31@tzi.org>
References: <7047.1363231468@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1499)
Cc: solace@ietf.org
Subject: Re: [solace] Will this IRTF group proceed?
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: Thu, 14 Mar 2013 16:26:34 -0000

On Mar 14, 2013, at 04:24, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> 
> We are now at the second meeting after we concluded that we needed
> something like SOLACE.  Are we any closer to forming a specific group?

I don't think we want a "SOLACE" IRTF group.

I spent this morning in the LWIG meeting.
This felt a lot like an IRTF meeting usually feels.
Some of it was about security, but of course more about the implementation of security.
There is a DTLS-based draft that might address the multicast security problem.

Right now I'm at the COMAN lunch meeting.
10 people are here, and we are discussing things that are also related to lifecycle issues.

Yesterday, we had a CORE meeting, where we said we wanted to pick up something like the "Mothership" work.  (We also said that we don't want to second-guess the ZigBee IP work.)

> While many of us have been focused on security, I think that there may
> be some other things that could benefit from a a clearer lifetime
> process.   I am thinking in particular of various phases outlined by the
> ROLL industrial applicability may mandate rekeying of the network
> between phases.

Right, another one.

> I'm not sure that I'm satisfied with an IRTF group.

Nobody would be satisfied with just an IRTF group.
What the IRTF RG should do is keep an eye on the wider issues in this space.
We also need to do engineering work, and it now seems there are some items we can pick up immediately.

Grüße, Carsten