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

"Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov> Wed, 11 July 2012 13:12 UTC

Return-Path: <william.d.ivancic@nasa.gov>
X-Original-To: coma@ietfa.amsl.com
Delivered-To: coma@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DDD7321F8694 for <coma@ietfa.amsl.com>; Wed, 11 Jul 2012 06:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.697
X-Spam-Status: No, score=-5.697 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id tOrZW+njxoAP for <coma@ietfa.amsl.com>; Wed, 11 Jul 2012 06:12:56 -0700 (PDT)
Received: from ndjsnpf01.ndc.nasa.gov (ndjsnpf01.ndc.nasa.gov []) by ietfa.amsl.com (Postfix) with ESMTP id A0CDD21F869D for <coma@ietf.org>; Wed, 11 Jul 2012 06:12:55 -0700 (PDT)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt05.ndc.nasa.gov []) by ndjsnpf01.ndc.nasa.gov (Postfix) with ESMTP id E60B7D1913; Wed, 11 Jul 2012 08:13:25 -0500 (CDT)
Received: from ndjshub06.ndc.nasa.gov (ndjshub06.ndc.nasa.gov []) by ndjsppt05.ndc.nasa.gov (8.14.5/8.14.5) with ESMTP id q6BDDOcV024432; Wed, 11 Jul 2012 08:13:24 -0500
Received: from NDJSSCC07.ndc.nasa.gov ([]) by ndjshub06.ndc.nasa.gov ([]) with mapi; Wed, 11 Jul 2012 08:13:23 -0500
From: "Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov>
To: "coma@ietf.org" <coma@ietf.org>
Date: Wed, 11 Jul 2012 08:13:22 -0500
Thread-Topic: Store, Carry and Forward (SCF) Technologies for Management of Constrained Networks and Devices
Thread-Index: Ac1fZvMgGLYk9I+NQ5GOwwAzW6EUlg==
Message-ID: <F95883E2-FD43-4303-B9B9-D41E389F20D8@nasa.gov>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F95883E2FD434303B9B9D41E389F20D8nasagov_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-07-11_02:2012-07-11, 2012-07-11, 1970-01-01 signatures=0
Cc: Wesley Eddy <weddy@grc.nasa.gov>
Subject: [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: Wed, 11 Jul 2012 13:12:57 -0000

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:


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

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