why dns should be the naming service for iot? · • identifier • unique way of identifying a...
TRANSCRIPT
Why DNS should be the naming service for IoT?
Some terminology
2
• Identity • Definable and recognizable (.e.g. My name is “Sandoche” ) • Need not be unique and does not need to follow any particular “naming
convention” (.e.g. Name could be “John Paul II” )
• Identifier • Unique way of identifying a physical or virtual object. Should follow a
particular naming convention ( e.g. Passport Number)
• Addressing • Unique way of identifying a physical or virtual object in the scope of
communication • Need to follow a particular “naming convention” ( E.g. Postal Address,
IPv4/IPv6, MAC Address)
• Naming Service • Mapping the unique identifier to its appropriate unique service/
information
Preamble with the Internet
3
www.afnic.fr
Identifiers Naming Service
DNS
Naming Authority
Resolution
Provisioning (Hierarchical)
Application
Naming convention for the Identifiers IETF
- Domain names, URI
Making the things identifiable in IoT
4
IoT applications – Example of a private naming Service
5
Identifier
Naming convention = EUI-48 and EUI-64
MAC address Provisioning
- 00-17-4F-08-5D-69 - assigned to vendors by the IEEE - assigned by the vendor from its block
00-17-4F-08-5D-69
Identifier Naming Service
SaaS
Resolution Application
IoT SDOs and Alliances landscape
6
IoT - Consumer Industry provisioning
7
EPC Provisioning (Hierarchical)
GS1 Prefix (Country Code)
Company Code
Product ID
Serial number
Naming Authority
IoT - Consumer Industry without DNS
8
RFID
Naming Service
GEPIR
Resolution
Application
Naming Convention = EPC
Barcode
Extended Packaging
Track & Trace
Need = I(Internet)oT
9
IoT - Consumer Industry using DNS
10
RFID
Naming Service
ONS
Resolution Application
Naming Convention = EPC
Barcode
Extended Packaging
Track & Trace
11
IoT - Consumer Industry FQDN
IoT - LPWAN Industry eco-system
12
Radio IP
Detailed view of the LoRa network
Gateway “A” Operator “A”
Operator “B” Gateway “B”
Application Server “A”
Application Server “B”
“A” Network “B” Network
Portability issues in LoRaWAN
14
Operator B
Operator A
Home Network is Operator A
But, the GW forwards the join request to Operator B
How does 'B' know the home network (i.e. operator ‘A’)?
1
2
End-device Gateway
Application
Possible solution for portability using DNS
15
Operator B
Operator A
Home Network is Operator A
But, the GW forwards the join request to Operator B
1
2
DNS
3 4
5
6
MAC.iotreg. IN CNAME Operator
Naming service requirements for IoT
16
ü Must be scalable
ü Must work for legacy and new naming conventions
ü Should work for hierarchical and flat identifiers
Naming service in different standard organisations
17
ü Domain names (IETF) – DNS
ü Electronic Product Code (GS1) – ONS which uses DNS
ü Object Identifier (ISO, ITU-T) – ORS which uses DNS
ü Digital Object Identifier (ISO) – For initial resolution uses
DNS
Vision
18
DNS
