Re: [Iotsi] New IoT effort at schema.org

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 12 September 2016 18:00 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iotsi@ietfa.amsl.com
Delivered-To: iotsi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621DA12B006; Mon, 12 Sep 2016 11:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.409
X-Spam-Level:
X-Spam-Status: No, score=-3.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 7M3i8RPyTMVG; Mon, 12 Sep 2016 11:00:31 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8FFD128E19; Mon, 12 Sep 2016 11:00:30 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 656AB203B9; Mon, 12 Sep 2016 14:13:02 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 09BF46392D; Mon, 12 Sep 2016 14:00:29 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
In-Reply-To: <a9f8286f-aa8a-b09b-b781-95b733516fd5@cisco.com>
References: <CA+9kkMCRY6eRF+FgSAm2yE_HdH3i90WYCwxVCUaWM-Drk3kvgQ@mail.gmail.com> <CACp1KyPDYkKcK0u0XZOMbCMQWtyOuR2nnv4w1HMAMTopMVyZew@mail.gmail.com> <ACC85CBE-A2A8-4813-91B5-F8E6F7D409AD@coote.org> <a574ca33-8053-ba9a-443b-fb15234f5c51@cisco.com> <HE1PR0802MB2475ED419A0DD913BCA2DD15FAEB0@HE1PR0802MB2475.eurprd08.prod.outlook.com> <56171746-364d-ec04-44b9-78068f50e6c1@cisco.com> <49919A41-7CDA-4515-8509-8A93DD11F97B@coote.org> <a1a63afe-5020-21aa-29a6-5c2c3e4c38f7@cisco.com> <HE1PR0802MB24754ED0E9D9B0B835705A85FAEB0@HE1PR0802MB2475.eurprd08.prod.outlook.com> <a9f8286f-aa8a-b09b-b781-95b733516fd5@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 12 Sep 2016 14:00:29 -0400
Message-ID: <1466.1473703229@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotsi/O8wkasan6gr1478ln0PspF9fg1I>
Cc: Ted Hardie <ted.ietf@gmail.com>, "iotsi@iab.org" <iotsi@iab.org>, Internet Architecture Board <iab@iab.org>, David Janes <davidjanes@davidjanes.com>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, Tim Coote <tim+ietf.org@coote.org>
Subject: Re: [Iotsi] New IoT effort at schema.org
X-BeenThere: iotsi@iab.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Internet of Things Semantic Interoperability Workshop <iotsi.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/iotsi>, <mailto:iotsi-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotsi/>
List-Post: <mailto:iotsi@iab.org>
List-Help: <mailto:iotsi-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/iotsi>, <mailto:iotsi-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Sep 2016 18:00:34 -0000

So I'm hearing that NEA the concept has been successful as vendor proprietary
(two-sided) systems, but as a result, NEA The Protocol, has been still born.

That's been my impression too.

Eliot Lear <lear@cisco.com>; wrote:
    > On 8/23/16 2:03 PM, Hannes Tschofenig wrote:
    >> Eliot,
    >>
    >> I would like to hear your view on why NEA has been a failure.
    >>
    > I've given this more thought.  Let us distinguish between NEA the
    > protocol and NEA the concepts.  The concepts are very well deployed,
    > mostly in the form of mobile device managers (MDNs), including the VPN
    > module I am using at this very moment.  These sorts of modules tend to
    > be two-sided vendor specific, meaning that little standardization is
    > required.  This works well when there are very few types of devices.  It
    > works less well when we don't even know how to count how many types of
    > devices there are.

    > Eliot

    >> Ciao
    >> Hannes
    >>
    >>
    >> -----Original Message-----
    >> From: Eliot Lear [mailto:lear@cisco.com]
    >> Sent: 23 August 2016 13:33
    >> To: Tim Coote
    >> Cc: Hannes Tschofenig; David Janes; iotsi@iab.org; Ted Hardie; Internet Architecture Board
    >> Subject: Re: [Iotsi] New IoT effort at schema.org
    >>
    >> Going down...
    >>
    >>
    >> On 8/23/16 1:26 PM, Tim Coote wrote:
    >>> There’s a commercial asymmetry here, which means that Thing Makers may not know what they have released (their focus is on shifting boxes) and any assertion, unless backed up by a legal contract is worth little. Whoever is dropping in hardware based Things may put in a new version or a replacement from a different supplier that claims to be the same as something else. But isn’t.
    >> I think what you are saying is that there are white label products out there.  It is true that one might simply not ask the question.  I don't find that particularly satisfying, and I know my enterprise friends are even less enthralled.  They need a way to identify what is accessing their networks.
    >>
    >>
    >>> My conclusion was that the owner of the service delivered to the customer must define automated tests and behaviour categorisations that are used to accept new components and to identify rogues in production.
    >> Sure.  That amounts to NEA, perhaps with a protocol tweak here or there.  But the challenge is getting Things to divulge ANY information in a way that doesn't actually place them on shodan.io.
    >>
    >> Eliot
    >>
    >> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
    >> _______________________________________________
    >> Iotsi mailing list
    >> Iotsi@iab.org
    >> https://www.iab.org/mailman/listinfo/iotsi


    > _______________________________________________
    > Iotsi mailing list
    > Iotsi@iab.org
    > https://www.iab.org/mailman/listinfo/iotsi

--
Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
 -= IPv6 IoT consulting =-