Re: [solace] Slides posted for SAAG heads-up

"Keoh, Sye Loong" <sye.loong.keoh@philips.com> Thu, 08 November 2012 02:35 UTC

Return-Path: <sye.loong.keoh@philips.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 9EF6F21F8A7E for <solace@ietfa.amsl.com>; Wed, 7 Nov 2012 18:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.348
X-Spam-Level:
X-Spam-Status: No, score=-4.348 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 0y0TArE0cCYS for <solace@ietfa.amsl.com>; Wed, 7 Nov 2012 18:35:34 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id E3C4121F8A78 for <solace@ietf.org>; Wed, 7 Nov 2012 18:35:33 -0800 (PST)
Received: from mail67-co1-R.bigfish.com (10.243.78.227) by CO1EHSOBE008.bigfish.com (10.243.66.71) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 02:35:33 +0000
Received: from mail67-co1 (localhost [127.0.0.1]) by mail67-co1-R.bigfish.com (Postfix) with ESMTP id 2DBEB801D7 for <solace@ietf.org>; Thu, 8 Nov 2012 02:35:33 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -30
X-BigFish: VPS-30(zzbb2dI217bI98dI15d6O9371I9251Jc89bhc85dh1418Izz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0l1155h)
Received: from mail67-co1 (localhost.localdomain [127.0.0.1]) by mail67-co1 (MessageSwitch) id 1352342131822916_11907; Thu, 8 Nov 2012 02:35:31 +0000 (UTC)
Received: from CO1EHSMHS005.bigfish.com (unknown [10.243.78.230]) by mail67-co1.bigfish.com (Postfix) with ESMTP id BD89280005D for <solace@ietf.org>; Thu, 8 Nov 2012 02:35:31 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by CO1EHSMHS005.bigfish.com (10.243.66.15) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 8 Nov 2012 02:35:31 +0000
Received: from 011-DB3MMR1-015.MGDPHG.emi.philips.com (10.128.28.99) by 011-DB3MMR1-005.MGDPHG.emi.philips.com (10.128.28.55) with Microsoft SMTP Server (TLS) id 14.2.318.3; Thu, 8 Nov 2012 02:35:25 +0000
Received: from 011-DB3MPN1-032.MGDPHG.emi.philips.com ([169.254.2.110]) by 011-DB3MMR1-015.MGDPHG.emi.philips.com ([10.128.28.99]) with mapi id 14.02.0318.003; Thu, 8 Nov 2012 02:35:21 +0000
From: "Keoh, Sye Loong" <sye.loong.keoh@philips.com>
To: "solace@ietf.org" <solace@ietf.org>
Thread-Topic: [solace] Slides posted for SAAG heads-up
Thread-Index: AQHNvQ/Ls8VpsIxeDEOdmSbm18t0JZfe1ASAgAASbQCAAAjlAIAAFgwAgAAB5gCAABAegIAAIPAg
Date: Thu, 08 Nov 2012 02:35:21 +0000
Message-ID: <EAE29B174013F643B5245BA11953A1BE223043FC@011-DB3MPN1-032.MGDPHG.emi.philips.com>
References: <17F77EDC-3726-4AF2-9848-1C98E3F98B7E@tzi.org> <509AC579.3090301@gmail.com> <30433E6B-C9B9-4EDC-B2D5-1D042F8199AD@tzi.org> <509ADC64.2040902@gridmerge.com> <509AEEE2.6000102@gmail.com> <1706388E-C26A-4665-B9EF-E502CC71B6CF@tzi.org> <509AFDFF.5030505@gridmerge.com>
In-Reply-To: <509AFDFF.5030505@gridmerge.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.129.69.29]
Content-Type: multipart/alternative; boundary="_000_EAE29B174013F643B5245BA11953A1BE223043FC011DB3MPN1032MG_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: Re: [solace] Slides posted for SAAG heads-up
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, 08 Nov 2012 02:35:35 -0000

Rob's suggestion sounds good to me. We need a starting point and then we can build on it later on.

Cheers
Sye Loong

From: solace-bounces@ietf.org [mailto:solace-bounces@ietf.org] On Behalf Of Robert Cragie
Sent: donderdag 8 november 2012 1:34
To: solace@ietf.org
Subject: Re: [solace] Slides posted for SAAG heads-up

I think the point is you could choose any number of scenarios and providing they are well-researched and understood, any of them would serve as a starting point. Where it starts to go wrong IMHO is trying to start with a number of disparate scenarios and in the first analysis phase trying to distil some common understanding and architecture from all of them. I think it makes more sense to start with one and I think that Carsten's suggestion is more representative of the challenges facing device lifecycle and is therefore a good starting point.

I would then move forward in an incremental fashion whereby at each increment we:

  1.  Introduce a new scenarios
  2.  Aim to describe it using the architectural concepts developed for the previous scenarios
  3.  Refine the architectural concepts
Robert
On 07/11/2012 11:36 PM, Carsten Bormann wrote:

On Nov 7, 2012, at 18:29, Rene Struik <rstruik.ext@gmail.com><mailto:rstruik.ext@gmail.com> wrote:



industrial control



Too easy.



This is usually a highly controlled environment, where there already are defined business relationships.



Try a home occupied with a family with a 13-year old son, where the lifecycle later involves, say, a divorce and a foreclosure.



(I like the industrial scenario, but I think we should do that later.)



Grüße, Carsten



_______________________________________________

solace mailing list

solace@ietf.org<mailto:solace@ietf.org>

https://www.ietf.org/mailman/listinfo/solace




________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.