IETF Logo Mail Archive

RE: Getting on with Things

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 09 March 2016 16:53 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1CB12DFEB for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 08:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Level:
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fzb_QWjXkj2y for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 08:53:52 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AA5B12DDBA for <ietf@ietf.org>; Wed, 9 Mar 2016 08:53:40 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u29GrECa026352; Wed, 9 Mar 2016 16:53:14 GMT
Received: from 950129200 ([79.141.128.249]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u29Gr03Z026030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 9 Mar 2016 16:53:14 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eliot Lear' <lear@cisco.com>, 'Michael Richardson' <mcr@sandelman.ca>, 'Phillip Hallam-Baker' <phill@hallambaker.com>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net> <4A95BA014132FF49AE685FAB4B9F17F657DF2330@dfweml701-chm> <EDFB7D0B-2A49-46BD-A84C-0E1FA07793FA@piuha.net> <20160307133944.GB25576@gsp.org> <56DD876C.6050008@cs.tcd.ie> <CAMm+LwiBT9S-twGVzC-7yVBZ9dHA3+8f4ffPv3LyoZ_8+kdqmw@mail.gmail.com> <9059.1457534150@obiwan.sandelman.ca> <56E043FA.5060205@cisco.com>
In-Reply-To: <56E043FA.5060205@cisco.com>
Subject: RE: Getting on with Things
Date: Wed, 09 Mar 2016 16:53:01 -0000
Message-ID: <00e301d17a24$2d48eba0$87dac2e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGhgxqXYG63e7RGVllMOFy0inZeNgFhbnDfAZcRvcUB+3sIUwKkF34TAXv4YIICkRDplwIUoXzDn0NzQ5A=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22182.000
X-TM-AS-Result: No-1.876-10.0-31-10
X-imss-scan-details: No-1.876-10.0-31-10
X-TMASE-MatchedRID: u1zqiMeMcrpBOSn32xXE3Jmug812qIbzVBDQSDMig9GqvcIF1TcLYJlr QU062on1u7YkEMhTLNHLdkSYFsf1L6eM1IOL++RXGuE3UyUHG1d9LQinZ4QefDuUMbK1NdLP+gt Hj7OwNO2OhzOa6g8KrUmkW+231SK543/j3fROvkf+86imPUyTW8LuwEky8F1r6JGDekIVw97kP2 yapUEP3KKWedUMQI938fsC+xPFkxvsNp90fT4EjnOW414THrIC
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MX0qSV633k_x7IORIUWFyFvpRKg>
Cc: 'IETF' <ietf@ietf.org>, 'Rich Kulawiec' <rsk@gsp.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2016 16:53:54 -0000

Eliot,

Picking one piece out of your MUD...

> I've floated an idea in draft-lear-mud-framework-00.txt which talks a
> little about this.  The idea is to learn what the Thing is and then have
> its manufacturer communicate to a deployment how the thing is intended
> to be used.

This approach worries me. While the manufacturer might not object to this, the user and the system integrator should. The fact that a device was manufactured for foo should not stop it being used for bar. 

Adrian

v2.26.15 | Report a Bug | By Email | System Status