Re: [smartobjectdir] Charter

Vint Cerf <vint@google.com> Sun, 09 October 2011 12:23 UTC

Return-Path: <vint@google.com>
X-Original-To: smartobjectdir@ietfa.amsl.com
Delivered-To: smartobjectdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F27F821F8B03 for <smartobjectdir@ietfa.amsl.com>; Sun, 9 Oct 2011 05:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 2VwLRtF94m0K for <smartobjectdir@ietfa.amsl.com>; Sun, 9 Oct 2011 05:23:35 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1798921F8AC9 for <smartobjectdir@ietf.org>; Sun, 9 Oct 2011 05:23:31 -0700 (PDT)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id p99CNUpH032508 for <smartobjectdir@ietf.org>; Sun, 9 Oct 2011 05:23:30 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1318163011; bh=VwxCL3dQtDskUfRD4FWVlL0vIRg=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=JvGVplgQAoLKRZmAfGihk5OF58DMoRuGu1EwpL25/s1ASlLeBdtdjZ0+0iaTvqk4j T/hY2kiF2gwBvnNAIAsHA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=grCpalyXeRA3JzQjaTEU6f+EtGAZLdXs6DPuKtQ4BXVIYfWYkf3CE+TmclsJI2OXc UEmdTmCZlnAwN3uUHJDhA==
Received: from iaen33 (iaen33.prod.google.com [10.12.165.33]) by wpaz17.hot.corp.google.com with ESMTP id p99CNEOD028213 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <smartobjectdir@ietf.org>; Sun, 9 Oct 2011 05:23:29 -0700
Received: by iaen33 with SMTP id n33so7987055iae.2 for <smartobjectdir@ietf.org>; Sun, 09 Oct 2011 05:23:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ug97KCoDxM7o1xgpRWas8fahan02AlFre31Bt5z2lhw=; b=c4y9VpeklHxOTv4WYGKbtskLZaPeM9PX9v7nclP72FIE2yolNcG41VjPC551rKcLZK zq9UmzyX4esyYtQIC3zA==
Received: by 10.42.136.196 with SMTP id v4mr9231153ict.3.1318163009241; Sun, 09 Oct 2011 05:23:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.136.196 with SMTP id v4mr9231146ict.3.1318163009141; Sun, 09 Oct 2011 05:23:29 -0700 (PDT)
Received: by 10.231.30.202 with HTTP; Sun, 9 Oct 2011 05:23:29 -0700 (PDT)
In-Reply-To: <DC512462-0FD5-40F0-B6A4-9F580133E3DE@cisco.com>
References: <B6C7A935-C40D-4E3E-B6C9-7179EDE0C99C@vigilsec.com> <8BE7D920-176C-4A16-AEB3-D525B6396060@cisco.com> <95201571-B862-4FAA-B3BA-76FE0E62F608@cisco.com> <DC512462-0FD5-40F0-B6A4-9F580133E3DE@cisco.com>
Date: Sun, 9 Oct 2011 08:23:29 -0400
Message-ID: <CAHxHggf53Veca_Sso3fy3o60URNb5eM1p2VqCa+3iiCgW=UjGw@mail.gmail.com>
From: Vint Cerf <vint@google.com>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: smartobjectdir@ietf.org, JP Vasseur <jpv@cisco.com>
Subject: Re: [smartobjectdir] Charter
X-BeenThere: smartobjectdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <smartobjectdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smartobjectdir>, <mailto:smartobjectdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartobjectdir>
List-Post: <mailto:smartobjectdir@ietf.org>
List-Help: <mailto:smartobjectdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartobjectdir>, <mailto:smartobjectdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2011 12:23:36 -0000

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

v


On Sun, Oct 9, 2011 at 7:33 AM, Fred Baker <fred@cisco.com> 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
> smartobjectdir@ietf.org
> https://www.ietf.org/mailman/listinfo/smartobjectdir
>