Re: Getting on with Things

Medel Ramirez <mgramirez@globe.com.ph> Wed, 09 March 2016 23:17 UTC

Return-Path: <mgramirez@globe.com.ph>
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 433A912DB54 for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 15:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=globe-com-ph.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OInR-lWNfmP for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 15:17:21 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE5F312DB08 for <ietf@ietf.org>; Wed, 9 Mar 2016 15:17:20 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id p65so6401515wmp.0 for <ietf@ietf.org>; Wed, 09 Mar 2016 15:17:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=globe-com-ph.20150623.gappssmtp.com; s=20150623; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=YeQ9xPMkwSPe6ZMqR+m6n3TnpW6wtvFcT9kT8d1ESbA=; b=KJxo99pzNyrJ4XYtjweMYD7s4xBzoOZ7kc0v7lwS+UOPskifVXFBIJLszAdDC4WthN oOokfxYoXeifj2V3wWLhsQBki7/cDirFALU9RmxWgYSCFI5gEpBNOB0IAnTT3MjaQXJy zc0r36OhjmrlQeXIo3glInAquMrkBE3X2rYj3Bai63ghbmVl/R/QrYnj5anRErHtu6XC hcCf5tDPnaM2y1RmEVH+3VF/HcFEgJN031LpJF/dVJcp/mdFNZR4S+roptXkcAho0+iw wVDYVz+C45o3IQHDp5sK37+22LsDu9afvBKTuiZW5vsggNTs1Esh8fUoAopT0pf/zRGm xRSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=YeQ9xPMkwSPe6ZMqR+m6n3TnpW6wtvFcT9kT8d1ESbA=; b=jEztz9AvX8Z4s9iJrtf4m2LM3L7V2lbLNXF9N/JOBYMwWiVn/dRFW6xZ0VcgtJUggz /J1z/F14q6E/7scRbhAKd8NP5ZAgZPa4jEsERD2g5D2l0MfhFgucWYueCnPAYSBtsFJD xynBr/QhaNpzZ/tG+nB3QgCyKUNdFo67B4c+KDD8J+Ehd0q8iMnt9KLhC3r1+yKeLTYg BdUUhm+Ygjp7oq7mFOXtX9hGQ/Ps/29RLIaQBjLACVpPBVBkfLgYK2Q1ZX0NM7WAwcm9 fkatAy3SUIqb5hp12A09psoknP4wRz9/jcKc+ycjnCn5fVOxFYMTuxYvq5l2mYfV7Eth KIEQ==
X-Gm-Message-State: AD7BkJI3F7Z5T6ZOoQQ+7aCPs0E8+AV8avPs5XV0QaoqzXkscH5fJmQYjXQqpUM9nRBWVukGe0RISeZMfPojsDYKa+Xjk1Z/21d1dLh8guA8gu05OOEA4vfHDgqW/JGP6efgWFBp
X-Received: by 10.28.60.84 with SMTP id j81mr226156wma.91.1457565438665; Wed, 09 Mar 2016 15:17:18 -0800 (PST)
From: Medel Ramirez <mgramirez@globe.com.ph>
Mime-Version: 1.0 (1.0)
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> <00e301d17a24$2d48eba0$87dac2e0$@olddog.co.uk> <56E05818.20605@gmail.com>
In-Reply-To: <56E05818.20605@gmail.com>
Date: Thu, 10 Mar 2016 07:14:32 +0800
Message-ID: <1307678330187229438@unknownmsgid>
Subject: Re: Getting on with Things
To: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RZYg8f80vX4DJChA_UfTnGR6AEA>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Michael Richardson <mcr@sandelman.ca>, Rich Kulawiec <rsk@gsp.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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 23:17:23 -0000

Adrian,
I can *attest* to that 😉

Have a nice day
Medel
+++++*+++

Sent from my V6 Engine!
メデル ラミレズ

> On Mar 10, 2016, at 1:10 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>
>
>
>> On 09/03/2016 16:53, Adrian Farrel wrote:
>> 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
>>
>
> Indeed, and too often manufactures already  do this as part of their business model.
>
> A classic example is where performance is throttled, or features are enabled only by
> licence.
>
> It is but a short step to application specific restriction, although if an application has
> third party IPR there can be a liability that rests with the manufacturer, in which
> case you can understand the concern.
>
> As distasteful and frustrating as this is, restriction of application may be an unfortunate necessity.
>
> - Stewart
>
>

-- 
This e-mail message (including attachments, if any) is intended for the use 
of the individual or the entity to whom it is addressed and may contain 
information that is privileged, proprietary, confidential and exempt from 
disclosure. If you are not the intended recipient, you are notified that 
any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, 
please notify the sender and delete this E-mail message immediately.