Re: [smartobjectdir] Charter

Fred Baker <> Sun, 09 October 2011 20:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 013AC21F8AEC for <>; Sun, 9 Oct 2011 13:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.484
X-Spam-Status: No, score=-101.484 tagged_above=-999 required=5 tests=[AWL=1.115, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KRgykS29k4yC for <>; Sun, 9 Oct 2011 13:21:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 57ABE21F8AD6 for <>; Sun, 9 Oct 2011 13:21:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2988; q=dns/txt; s=iport; t=1318191716; x=1319401316; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=SA1Vixr+1Xw/kQeGPeev5SPw6/MR63oswgT6PBcyUgw=; b=W5Qt4CM63Zaj3s+37seDUH3MSphwi8ApT5NuEr3VqLpwq+LEvM0py3lx sXLB3rOquLaIkGiC/6pgr1ePRpYJtSSDZxNxdZT6l+C5NBrzQkYhze7HR Qd+amRQ8pSzsz53i1EPxSa5SfYfAMJ1GD+qgOzm6QZ2sEKU4Ff+UFftfs w=;
X-IronPort-AV: E=Sophos;i="4.68,513,1312156800"; d="scan'208";a="6835482"
Received: from ([]) by with ESMTP; 09 Oct 2011 20:21:56 +0000
Received: from Freds-Computer.local ( []) by (8.14.3/8.14.3) with ESMTP id p99KLt9D016228; Sun, 9 Oct 2011 20:21:55 GMT
Received: from [] by Freds-Computer.local (PGP Universal service); Sun, 09 Oct 2011 16:21:56 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Sun, 09 Oct 2011 16:21:56 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <>
In-Reply-To: <>
Date: Sun, 9 Oct 2011 16:21:41 -0400
Message-Id: <>
References: <> <> <> <> <>
To: Vint Cerf <>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc:, JP Vasseur <>
Subject: Re: [smartobjectdir] Charter
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 09 Oct 2011 20:21:57 -0000

On Oct 9, 2011, at 8:23 AM, Vint Cerf wrote:

> some people might argue that "management" captures both telemetry and control...

Other people would remember that the M in SNMP stands for Management, and in that case it only means Monitoring :-)

> v
> On Sun, Oct 9, 2011 at 7:33 AM, Fred Baker <> wrote:
>> On Oct 9, 2011, at 5:27 AM, JP Vasseur wrote:
>>> There are other terms in us, 6lowpan (sometimes used to refer to IP smart object network, although it does point
>>> out to a specific set of technologies, LLN (Low power and Lossy Networks, …).
>> I'll argue that those refer to a specific category of such networks, one using IEEE 802.15.4; there are a number of other link layer technologies in use that don't necessarily have the same characteristics and for which 6lowpan isn't obviously relevant. I see tying it to a specific MAC/PHY as a trap. The important thing for us is that IP (of which 6lowpan is a compression) transcends the MAC/PHY in use and potentially connects it to networks composed of more traditional technologies such as IEEE 802.3.
>>> Thanks for updating the charter, I would just propose to replace "telemetry and control" by "sensing and actuating".
>> Willing enough, although I again see a potential trap. When we talk about industrial automation, management of water displays like the Bellagio Fountains, and so on, "actuating" is a great word in it primary meaning of "cause (a machine or device) to operate"; that goes straight back to Latin. That said, not every "action" in a network is the movement of a device; it also might change the thresholds in the sensor or do some other non-physical thing - that for which we might use the term "configuration". I talk about "control", because it includes both. Similarly, sensing to me is somewhat limited; the obvious meaning would be to somehow measure some physical thing like movement or temperature. In a building control system, it the actions might also include reporting state, such as "you announced that lamp X should change state to 'on'; lamp X is now 'on'". In space communications, the paradigm has been for some time "command and telemetry"; someone tells a satellite or space probe to do something, such as turn a camera in a specific direction, and the continuous stream of data from the satellite/probe might include the direction the camera is pointed. We observe, eventually, that the command has had a certain effect because we see the change in the telemetry it reports. Hence I use the terms "control" and "telemetry", as they include "sensing" and "actuating" but are not limited to their meanings.
>> Other opinions?
>> _______________________________________________
>> smartobjectdir mailing list