Re: [smartpower-interest] Smart things in stupid networks

Pascal.Urien@gmail.com Fri, 29 July 2011 09:57 UTC

Return-Path: <Pascal.Urien@gmail.com>
X-Original-To: smartpower-interest@ietfa.amsl.com
Delivered-To: smartpower-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D4621F8B67 for <smartpower-interest@ietfa.amsl.com>; Fri, 29 Jul 2011 02:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level:
X-Spam-Status: No, score=-1.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJMggQW1yZiH for <smartpower-interest@ietfa.amsl.com>; Fri, 29 Jul 2011 02:57:27 -0700 (PDT)
Received: from mail-ww0-f70.google.com (mail-ww0-f70.google.com [74.125.82.70]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB1F21F8B46 for <smartpower-interest@ietf.org>; Fri, 29 Jul 2011 02:57:27 -0700 (PDT)
Received: by wwg11 with SMTP id 11so1268916wwg.1 for <smartpower-interest@ietf.org>; Fri, 29 Jul 2011 02:57:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.213.4.200 with SMTP id 8mr144384ebs.1.1311933445829; Fri, 29 Jul 2011 02:57:25 -0700 (PDT)
In-Reply-To: <CA573FD1.9493%d.sturek@att.net>
Message-ID: <0015174c0e3402193704a9324fa5@google.com>
Date: Fri, 29 Jul 2011 09:57:25 +0000
From: Pascal.Urien@gmail.com
To: Don Sturek <d.sturek@att.net>, Pascal.Urien@gmail.com
Content-Type: multipart/alternative; boundary=0015174c0e340218fd04a9324fa2
X-Mailman-Approved-At: Sat, 30 Jul 2011 09:34:39 -0700
Cc: 6man-chairs@tools.ietf.org, tictoc-chairs@tools.ietf.org, core-chairs@tools.ietf.org, lwig-chairs@tools.ietf.org, eman-chairs@tools.ietf.org, opsawg-chairs@tools.ietf.org, homenet-chairs@tools.ietf.org, 6lowpan-chairs@tools.ietf.org, roll-chairs@tools.ietf.org, smartpower-interest@ietf.org, netconf-chairs@tools.ietf.org
Subject: Re: [smartpower-interest] Smart things in stupid networks
X-BeenThere: smartpower-interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Smart Power Interest <smartpower-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpower-interest>
List-Post: <mailto:smartpower-interest@ietf.org>
List-Help: <mailto:smartpower-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 09:57:29 -0000

Hi Don,

In http://tools.ietf.org/html/draft-urien-hip-iot-00 there is a discussion  
about the RFID and the Internert Of Thing, and one issue is IP or not IP  
layer in the RFID.

If there is enough computing power then an IP stack may be supported

But

- An RFID has no battery
- An RFID is powered by a reader , the reader always includes an IP stack
- The primary goal of an RFID is to deliver a serial number, we want to  
protect this information.
- Some additionnal read/write operations may be available

In draft-irtf-hiprg-rfid-03.txt (  
http://www.ietf.org/proceedings/81/slides/HIPRG-1.pdf ) we use a modified  
HIP layer in the RFID and an IP stack in the reader. For read/write  
operations an ESP protocol could be used by the RFID, whose PDUs are  
transported by the reader IP packets.

The open issues are
- what protocol is running in the RFID for identity protection,
- what services are provided by the reader.

Best Regards

Pascal

Le , Don Sturek <d.sturek@att.net> a écrit :
> Hi Pascal,


> I would expect that the presence of an IP layer is the minimum bar for  
> inclusion into the IETF internet of things.


> Question for you: How would devices without an IP layer participate in an  
> IP network?


> Don






> From: Pascal.Urien@gmail.com>
> Date: Thu, 28 Jul 2011 18:08:31 +0000
> To: Fred Baker fred@cisco.com>
> Cc: 6man-chairs@tools.ietf.org>gt;, tictoc-chairs@tools.ietf.org>gt;,  
> core-chairs@tools.ietf.org>gt;, lwig-chairs@tools.ietf.org>gt;,  
> eman-chairs@tools.ietf.org>gt;, opsawg-chairs@tools.ietf.org>gt;,  
> homenet-chairs@tools.ietf.org>gt;, 6lowpan-chairs@tools.ietf.org>gt;,  
> roll-chairs@tools.ietf.org>gt;, smartpower-interest@ietf.org>gt;,  
> netconf-chairs@tools.ietf.org>
> Subject: Re: [smartpower-interest] Smart things in stupid networks



> Hi fred,



> The draft draft-irtf-hiprg-rfid-03.txt is based on two ideas



> - A "smart" thing has an identity, but not neccesary an IP layer


> - A "smart" thing needs strong privacy, eg no fix identifier such as an  
> IP address ou a hash value of some value



> more details at


> http://perso.telecom-paristech.fr/~urien/hiprfid/index.html



> Best Regards



> Pascal



> Le , Fred Baker fred@cisco.com> a écrit :


> > FYI...


> >


> >


> >


> >


> >


> > I sat down last night to categorize what work we have around that  
> directly relates (as in, *says* it relates) to sensors, the smart grid,  
> and the nebulous "internet of things". What I came up with is attached:  
> 46 documents in 8 working groups or research groups, touching on  
> everything from "here's how to build a home" to routing architectures to  
> energy management MIBs.


> >


> >


> >


> >


> >


> > I personally would be interested to have the various people involved  
> comment for the group on what their contributions are about. It looks  
> interesting, and enquiring minds want to know :-)


> >


> >


> >


> >


> >


> > Core:


> >


> >


> > draft-arkko-core-security-arch-00.txt


> >


> >


> > draft-arkko-core-sleepy-sensors-01.txt


> >


> >


> > draft-braun-core-compressed-ipfix-02.txt


> >


> >


> > draft-garcia-core-security-02.txt


> >


> >


> > draft-sarikaya-core-sbootstrapping-02.txt


> >


> >


> >


> >


> >


> > Homenet:


> >


> >


> > draft-arkko-townsley-homenet-arch-00.txt


> >


> >


> > draft-baker-fun-multi-router-00.txt


> >


> >


> >


> >


> >


> > lwig:


> >


> >


> > draft-bormann-lwig-guidance-00.txt


> >


> >


> > draft-williams-lwig-api-considerations-00.txt


> >


> >


> >


> >


> >


> > Crypto:


> >


> >


> > draft-campagna-suitee-01.txt


> >


> >


> >


> >


> >


> > 6man:


> >


> >


> > draft-chakrabarti-nordmark-energy-aware-nd-00.txt


> >


> >


> > draft-oreirdan-rosenwald-ipv6mail-transition-00.txt


> >


> >


> >


> >


> >


> > eman:


> >


> >


> > draft-claise-energy-monitoring-mib-09.txt


> >


> >


> > draft-ietf-eman-energy-aware-mib-02.txt


> >


> >


> > draft-ietf-eman-framework-02.txt


> >


> >


> > draft-jennings-energy-pricing-01.txt


> >


> >


> > draft-nordman-eman-energy-perspective-01.txt


> >


> >


> > draft-tychon-eman-applicability-statement-02.txt


> >


> >


> > draft-verges-eman-separate-modules-mib-00.txt


> >


> >


> >


> >


> >


> > 6lowpan:


> >


> >


> > draft-daniel-6lowpan-security-analysis-05.txt


> >


> >


> > draft-ietf-6lowpan-btle-01.txt


> >


> >


> > draft-ietf-6lowpan-hc-15.txt


> >


> >


> > draft-ietf-6lowpan-routing-requirements-09.txt


> >


> >


> > draft-ietf-6lowpan-usecases-10.txt


> >


> >


> > draft-wang-6lowpan-scheduling-requirements-00.txt


> >


> >


> >


> >


> >


> > roll:


> >


> >


> > draft-goyal-roll-metrics-direction-00.txt


> >


> >


> > draft-ietf-roll-applicability-ami-01.txt


> >


> >


> > draft-ietf-roll-security-framework-06.txt


> >


> >


> > draft-ietf-roll-terminology-05.txt


> >


> >


> > draft-popa-roll-applicability-ami-00.txt


> >


> >


> > draft-qiu-roll-kemp-00.txt


> >


> >


> >


> >


> >


> > opsawg:


> >


> >


> > draft-ietf-opsawg-management-stds-01.txt


> >


> >


> >


> >


> >


> > tictoc:


> >


> >


> > draft-ietf-tictoc-requirements-01.txt


> >


> >


> >


> >


> >


> > dtnrg:


> >


> >


> > draft-irtf-dtnrg-prophet-09.txt


> >


> >


> >


> >


> >


> > tsvwg:


> >


> >


> > draft-wood-tsvwg-saratoga-09.txt


> >


> >


> >


> >


> >


> > netconf:


> >


> >


> > draft-schoenw-netconf-light-00.txt


> >


> >


> >


> >


> >


> > hip/hiprg:


> >


> >


> > draft-irtf-hip-experiment-13.txt


> >


> >


> > draft-irtf-hiprg-rfid-03.txt


> >


> >


> > draft-moskowitz-hip-rg-dex-05.txt


> >


> >


> >


> >


> >


> > iot:


> >


> >


> > draft-iab-smart-object-workshop-01.txt


> >


> >


> > draft-lee-iot-problem-statement-02.txt


> >


> >


> > draft-routing-architecture-iot-00.txt


> >


> >


> > draft-song-iot-emergency-network-00.txt


> >


> >


> > draft-walewski-iot-use-case-00.txt


> >


> >


> >


> >


> >


> > Mentions Sensor Networks, Internet of Things, or Smart Grid, but  
> not "about" it:


> >


> >


> > draft-cui-softwire-host-4over6-06.txt


> >


> >


> > draft-oreirdan-mody-bot-remediation-13.txt


> >


> >


> >


> >


> >


> >


> >


> >


> >_______________________________________________

> smartpower-interest mailing list

> smartpower-interest@ietf.org

> https://www.ietf.org/mailman/listinfo/smartpower-interest