Re: [apps-discuss] Device Classification

Bruce Nordman <bnordman@lbl.gov> Fri, 28 October 2011 22:32 UTC

Return-Path: <bnordman@lbl.gov>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A6511E807F for <apps-discuss@ietfa.amsl.com>; Fri, 28 Oct 2011 15:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.753
X-Spam-Level:
X-Spam-Status: No, score=-5.753 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 e0Y+oO6DjFhg for <apps-discuss@ietfa.amsl.com>; Fri, 28 Oct 2011 15:32:24 -0700 (PDT)
Received: from ironport4.lbl.gov (ironport4.lbl.gov [128.3.41.45]) by ietfa.amsl.com (Postfix) with ESMTP id E58131F0C4A for <apps-discuss@ietf.org>; Fri, 28 Oct 2011 15:32:10 -0700 (PDT)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoABACotq07RVaC0kGdsb2JhbAA/A4JNmAuHOgGGWXIIIgEBAQEJCQ0HFAQhgXIBAQEBAgEBAQEPAloLBQsLCw0uIgUNAQUBHAYTCRmHYAiXJgqcU4VugxUEiAaMCIo3gnw9hA8
X-IronPort-AV: E=Sophos;i="4.69,421,1315206000"; d="scan'208";a="55371769"
Received: from mail-gy0-f180.google.com ([209.85.160.180]) by ironport4.lbl.gov with ESMTP; 28 Oct 2011 15:32:08 -0700
Received: by mail-gy0-f180.google.com with SMTP id 1so5450612gyf.39 for <apps-discuss@ietf.org>; Fri, 28 Oct 2011 15:32:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.244.30 with SMTP id r30mr1054568anh.78.1319841128368; Fri, 28 Oct 2011 15:32:08 -0700 (PDT)
Received: by 10.100.225.8 with HTTP; Fri, 28 Oct 2011 15:32:08 -0700 (PDT)
In-Reply-To: <CAA1s49WkZxTf9q4Q4LbwaCK_LVq+EWMksnFnesfZQrwOjQLFqA@mail.gmail.com>
References: <CAK+eDP-sQTXE+OXrktVdREH8z_pQ7gic7oZr3EjfiR+XJtrseg@mail.gmail.com> <CAA1s49WkZxTf9q4Q4LbwaCK_LVq+EWMksnFnesfZQrwOjQLFqA@mail.gmail.com>
Date: Fri, 28 Oct 2011 15:32:08 -0700
Message-ID: <CAK+eDP-LCbJN_jEyyb5aFuRe6N4rGbyxdBYSrg9e1rMkJ79=zg@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: Bob Wyman <bob@wyman.us>
Content-Type: multipart/alternative; boundary="001636c9282f9dcadf04b0637514"
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Device Classification
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 22:32:25 -0000

The mechanism proposed below seems like a fine choice - the only part
of this I am attempting to address is the content of the classification
field ("ip-router" in the example).

I propose a numerical index, much like the registry of port numbers, or
even ASCII.  I would expect a list of 100-150 device types - not 10 and not
thousands.
This index would be used with many mechanisms.

For extending a service like Webfinger to devices, this would define
one of the fields that would be returned.

Thanks,

--Bruce

On Fri, Oct 28, 2011 at 11:58 AM, Bob Wyman <bob@wyman.us> wrote:

> Consider using a mechanism like that defined for .well-known/host-meta URLs
> as defined in http://tools.ietf.org/html/draft-hammer-hostmeta-17
> Assuming that each device had a tiny http server embedded in it, then I
> could query a device like so:
>
> GET /.well-known/host-meta HTTP/1.1
> Host: device-url.com
>
>
> And, I would get back a response containing something like the following,
> which would include a classification value as well as links to just about
> any other URLs that might be interesting.
>
>   <?xml version='1.0' encoding='UTF-8'?>
>   <XRD xmlns='http://docs.oasis-open.org/ns/xri/xrd-1.0'>
>     <Subject>http://device-url.com/xy</Subject>
>     <Property type='http://spec.example.net/ipclassification'>ip-router</Property>
>
>     <Property type='http://spec.example.net/model'>IPR 2000</Property>
>
>  <Link rel='administrator'
> href='http://example.com/john' /> <Link rel='energy-consumption' href='
> http://device-url.com/energy-consumption' />
>
>     <Link rel='manufacturer-site'
>      href='http://big-vendor.com/' />
>
> </XRD>
>
>
> The nice thing about an approach such as that described above is that it is
> easily extensible to cover whatever needs might appear in the future. it
> would also be compatible with many of the systems that other folk are
> building, such as WebFinger<http://www.ietf.org/id/draft-jones-appsawg-webfinger-00.txt>,
> that deal with discovering information about people, accounts, etc.
>
> bob wyman
>
> On Fri, Oct 28, 2011 at 2:16 PM, Bruce Nordman <bnordman@lbl.gov> wrote:
>
>> Greetings all--
>>
>>   I am new to the apps area, with my involvement in IETF to date
>> focused on energy management.
>>   I recently posted:
>>      https://datatracker.ietf.org/doc/draft-nordman-classification/
>> the goal of which is to define a very basic enumeration for
>> classifying IP devices for generic purposes.  In my case, it is
>> for a system that vacuums up energy data for all devices in a
>> building to have a basic sense of what type of device it is
>> (e.g. router, computer, printer, refrigerator, ...).
>> I do believe that many applications would also find this useful,
>> particularly as physical-world objects seek to understand what
>> other devices are in their vicinity, whether or not they want to
>> directly interact with them.
>>   I am not seeking to do anything more complex than the above.
>> This is not intended to replace detailed classification and
>> characteristics
>> schemes that exist or will be developed for narrow sets of devices -- this
>> is only for the case of covering all devices and includes no
>> characteristics.
>>   I would welcome collaborators on this.
>>   Thanks,
>>
>> --Bruce
>>
>> --
>> *Bruce Nordman*
>> Lawrence Berkeley National Laboratory
>> eetd.lbl.gov/ea/nordman
>> BNordman@LBL.gov
>> 510-486-7089
>> m: 510-501-7943
>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>


-- 
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943