Minutes of the 1st F2F meeting of IDoT DG in Munich on 12th May 2014

Owned by Former user (Deleted)
Last updated: May 20, 2014
2 min read

Colin Wallis, Nat Sakimura, Jeff Stollmann, Frank Mildner, Ingo Friese

During the Kantara Plenary Ingo gave an update on what the group is currently doing. I used the presentation that can be found at our web site: http://kantarainitiative.org/confluence/download/attachments/64389214/20140217_IDoT_WF2014seoul_v1.0.pdf?version=1&modificationDate=1393341197000&api=v2

Among the white spots, unsolved und unstandardized problems in IoT IdM we have discovered a rather urgent one. Before it comes to authentication, communication or security Things have to find each other. We took the “Farming Example”:

Every morning the cabin-harvester meets other trucks. The harvester uses “serial no.”. Trucks use the IMEI of their GSM-module other use the License plate number. DNS does not work here. How these machines find each other’s IP-addresses when they use different identifier? There is an urgent need for something like “Object – DNS”.

Object Name Service                                          

In order to design a DNS for Things or an Object Name Service we have to consider several technologies including the advantages / disadvantages / challenges etc:

-          GS1 (incl. the step back of France because of Privacy Issues with Neustar)

-          XRI as a syntax allowing for putting different name spaces in one string (now maintained in XDI)

-          A static namespace like RFC 4350 (New Zealand URN) describing how to construct a namespace

-          DNS – Why is DNS not sufficient for IoT

-          “WhoIs” lookup

-          IETF Web link according to RFC 5988

-          Why is IPv6 alone not sufficient

-          Is there a role for Ontologies

-          Resolution/indirection (first step e.g. results in personal cloud / a second step accesses the personal cloud …incl access control)

  • What about SNMP? (remark added afterwards)

Colin raised another important question we have to consider in such a system:
How to ensure that the identifier is unique?

Once we have an abstract model there should be a translation to low power protocols to IEEE ; for TCP/IP protocols to IETF

Action point:

We will assign sub-topics from above to persons in the group. (If you read this and you want to volunteer you are highly welcome ;-)

 

Governance model for IoT data

Ingo discussed a very basic model to govern data in the IoT.

Action point:

Ingo describes the “governance model for IoT data” in a more detailed way as a concept /document combined with slides and pictures.  Then ask for feedback in Kantara:

  1. Information Sharing  Group (Remark: getting Feedback is not critical later on we have to check the implications of their RAND policy)
  2. User Managed Access Group

 

Terminology

When we write our papers we should re-use and check for terminology / concepts of other standard groups like:

-          IETF

-          IEEE

-          ITU-T

-          Cisco

-          IBM

LC reminds us to keep in touch with IEEE SA