13-14 October 2018
Okura Hotel
Europe/Amsterdam timezone

DNS usage in LoRaWAN

13 Oct 2018, 17:00
30m
Heian I/II (Okura Hotel)

Heian I/II

Okura Hotel

Ferdinand Bolstraat 333 1072 LH Amsterdam NL
Standard Presentation Public Workshop Joint OARC & CENTR-Tech Public Workshop

Speaker

Mr. sandoche Balakrichenan (Afnic)

Description

Afnic has been working for a while towards the objective of extending
DNS for IoT use cases. Previously, Afnic worked with the GS1 standard
organisation (Barcode/RFID registry for the supply chain industry), and
contributed to the evolution of the Object Naming Service (ONS) standard
[EPCglobal standard]. The ONS standard uses DNS as an overlay for
service discovery. The use cases are - "track and trace" and "extended
packaging information" of a consumer product. The consequence of this
experience for Afnic was that, well established industries like the
supply chain are reluctant to use open infrastructure like DNS due to
fallacious paranoia.

This pushed us to look at upcoming technologies or nascent industries in
the IoT for using DNS. This is where we stumbled upon on LoRaWAN, which
started as a fablab project some three years ago. LoRaWAN is an
ISM-based wireless technology for long-range low-power low-data-rate
applications developed by the LoRa Alliance [LoRa Alliance], a
membership consortium.

LoRaWAN networks are typically organized in a star-of-stars topology in
which Gateways relay messages between end devices and a central "network
server" in the backend. Gateways are connected to the network server
via IP links, while end devices use single-hop LoRaWAN communication
that can be received at one or more Gateways.

LoRaWAN use case are multiple; from smart meters to geo-localisation to
agriculture. Since LoraWAN uses unlicensed band, the cost of setting up
the infrastructure (approximately 3 to 4 million euros CAPEX to cover a
region similar to France) and for users using the LoRaWAN service
(approximately 1 euro per device per month) is quite low.

Due to the low cost, there are public LoraWAN operators (e.g. Bouygues
and Orange in France) and also number of private operators. This results
in a scenario, wherein it is difficult to manage the roaming
infrastructure. Hence, the current backend interface specification [LoRa
Backend Interface] for LoRa uses DNS for roaming purpose.

Similarly, for Over the Air Activation (i.e. to set the first
communication session between the device and the network server in the
Internet), the backend specification uses DNS.

This talk will include

  1. A basic introduction of the LoRa infrastructure
  2. How DNS is used by the LoRaWAN ecossytem for Roaming and Over the Air
    Activation?
  3. Afnic's involvement in the LoRa alliance as LoRa DNS operator
  4. How possibly DNS could be used for cryptographic key exchanges in the
    LoRa ecosystem?
  5. And, if there is time, how DNS could be used for exchanging the rules
    for compression/decompression?

Ref:

[EPCglobal standard]
http://www.gs1.org/gsmp/kc/epcglobal/ons/ons_2_0_1-standard-20130131.pdf
[LoRa Alliance] https://www.lora-alliance.org/
[LoRa Backend
Interface]https://lora-alliance.org/resource-hub/lorawantm-back-end-interfaces

Talk Duration 30 Minutes

Primary author

Mr. sandoche Balakrichenan (Afnic)

Presentation Materials

Your browser is out of date!

Update your browser to view this website correctly. Update my browser now

×