Re: [Coma] Store, Carry and Forward (SCF) Technologies for Management of Constrained Networks and Devices

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Mon, 16 July 2012 12:57 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: coma@ietfa.amsl.com
Delivered-To: coma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 158A121F8813 for <coma@ietfa.amsl.com>; Mon, 16 Jul 2012 05:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level:
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 zCvEPYWoxeKF for <coma@ietfa.amsl.com>; Mon, 16 Jul 2012 05:57:54 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3F48921F8815 for <coma@ietf.org>; Mon, 16 Jul 2012 05:57:53 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q6GCwZ6k024158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 16 Jul 2012 14:58:35 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q6GCwSep002920; Mon, 16 Jul 2012 14:58:32 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 16 Jul 2012 14:58:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD6352.98470753"
Date: Mon, 16 Jul 2012 14:57:45 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A640405E7E8@DEMUEXC006.nsn-intra.net>
In-Reply-To: <F95883E2-FD43-4303-B9B9-D41E389F20D8@nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Coma] Store, Carry and Forward (SCF) Technologies for Management of Constrained Networks and Devices
Thread-Index: Ac1fZvMgGLYk9I+NQ5GOwwAzW6EUlgD6c/4w
References: <F95883E2-FD43-4303-B9B9-D41E389F20D8@nasa.gov>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov>, <coma@ietf.org>
X-OriginalArrivalTime: 16 Jul 2012 12:58:28.0603 (UTC) FILETIME=[B1DB74B0:01CD6352]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 16359
X-purgate-ID: 151667::1342443515-00002E58-893E6EE7/0-0/0-0
Cc: Wesley Eddy <weddy@grc.nasa.gov>
Subject: Re: [Coma] Store, Carry and Forward (SCF) Technologies for Management of Constrained Networks and Devices
X-BeenThere: coma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Management of Constrained Networks and Devices <coma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coma>, <mailto:coma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coma>
List-Post: <mailto:coma@ietf.org>
List-Help: <mailto:coma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coma>, <mailto:coma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 12:57:57 -0000

Dear Will,

 

thank you for the information. SCF might be a useful solution e.g. for
SW distribution in constrained networks. 

However, our main interest is to collect use cases and to define
requirements for the management of the networks of constrained devices.

 

BR, 
Mehmet 

 

From: coma-bounces@ietf.org [mailto:coma-bounces@ietf.org] On Behalf Of
ext Ivancic, William D. (GRC-RHN0)
Sent: Wednesday, July 11, 2012 3:13 PM
To: coma@ietf.org
Cc: Wesley Eddy
Subject: [Coma] Store, Carry and Forward (SCF) Technologies for
Management of Constrained Networks and Devices

 

Hello,

I became aware of this list recently and perused the archives.  I am
posting with two motives:

(1)  To see if this group sees a need for store, carry and forward (SCF)
technologies. One of the areas we see such technology helping in is
updated software to systems in challenged (Constrained) networks.  

(2)  Our approach to bounding the SCF problem and generating
requirements may be useful to COMA. After reading the threads, it
appears that documenting your scenarios and creating a bounded problem
statement may help move discussion along. As is, the problem space
appears unbounded or, at least overly large.

The following Internet Drafts have recently been posted:

http://www.ietf.org/id/draft-ivancic-scf-problem-statement-00.txt

http://www.ietf.org/id/draft-ivancic-scf-requirements-expectations-00.tx
t

 

http://www.ietf.org/id/draft-ivancic-scf-testing-requirements-00.txt





There is also a recent presentation that might help regarding the
philosophical approach to the problem.  

http://roland.grc.nasa.gov/~ivancic/papers_presentations/2012/RobustNetw
orkingWorkshop062612.pdf

 

Summarized below:

=================



1. KISS (Keep it Simple Stupid)

2. Options make interoperability hard.

3. Options are often used as a placeholder for fixing a bad design.

4. Think about terminology. - "Words make a difference. They affect how
we thing about something. The terms chosen to describe a concept are a
crucial part of any model. The right concepts with terms that give the
wrong connotation can make a problem much more difficult. The right
terms can make it much easier. Adopting the mindset of the terms may
allow you to see thing you might not otherwise see." - John Day,
Patterns in Network Architect

 

5. Don't overload the protocol. 

6. "In anything at all, perfection if finally attained, not when there
is no longer anything to add, but when there is no longer anything to
take away..." - Antonie de Saint Exupery

7. "A good engineer is a lazy degenerate. He prefers degenerate cases to
special cases and will sit around (thinking) until he finds a simple
solution, rather that immediately launch into a brute force approach. In
other words, the goal of a architect is to use the tools he has to make
things simple. (Anyone can make things more complicated)!" - John Day,
Patterns in Network Architect

- Will

 

******************************
William D. Ivancic
http://roland.grc.nasa.gov/~ivancic