IoT Roadmap in the IETF - LACNIC - SLIDESslides.lacnic.net/wp-content/uploads/2017/06/ietf_iot_2017_ines.pdf · IoT(Internet of Things) Everything that can be connected will be connected

IoT Roadmap in the IETF

Ines Robles - [email protected]

Agenda

IETF and IoT DefinitionsIETF IoT WGs Internet Area: 6lo, 6tisch, lpwan, lwig, ipwave Routing Area: roll Application and Real Time Area: core Security Area: ace IRTF IoT WG: t2trgConclusions

2

IoT(Internet of Things)

3


Everything that can be connected will be connected

4



Adapt the Internet to different types of networks such as constrained

networks/nodes, e.g. send temperature in a 802.15.4 packet

5



Constraints Networks

o low achievable bit rate/throughput

o high packet loss and high variability of packet loss

o highly asymmetric link characteristics,

o limits on reachability over time

Constrained Nodes:

-Limits on power

- Memory

- Processing resources



6



Adapt IPv6



7



Adapt IPv6 Modeling the routing



8



Adapt IPv6 Modeling the routing Modeling the web transfer



9



Adapt IPv6 Modeling the routing Modeling the web transfer



10

Security, Mgmt



Adapt IPv6 Modeling the routing Modeling the web transfer Security, Mgmt

11

STANDARDS



http://xkcd.com/927/

https://www.howtogeek.com/124275/how-standards-proliferate/

12

13

Internet Engineering Task Force

ORGANIZATION OF VOLUNTARY PARTICIPATION WHOSE GOAL IS….

https://ietf.org/

14

15

The goal of the The Internet Engineering Task Force (IETF) is to make the Internet work better

Data Link (MAC + LLC)

Internet

Transport

Application

TCP/IP Stack

Physical

IETF

e.g. IEEE, 3GPP

16



Internet

Transport

Application

TCP/IP Stack

Physical

IETF

Applications and Real-Time

General

Internet

Ops & Mgmt

Routing

Security

Transport

IRTF

Areas

e.g. IEEE, 3GPP

17



Internet

Transport

Application

TCP/IP Stack

Physical

IETFAreas

Applications and Real-Time

General

Internet

Ops & Mgmt

Routing

Security

Transport

IRTF

–- include IoT Wgs

e.g. IEEE, 3GPP

18

19

20

IPv6 over Low Power Wireless Personal Area Networks (6LoWPAN) aims

IPv6 header

IPv6 Payload

IPv6 header

IPv6 Payload

6LoWPAN

to compress the IPv6 header

http://www.reckorder.com/wp-content/uploads/2011/03/compressdata.jpg

21

IPv6 over Low power WPAN (6lowpan) aims to compress the IPv6 header

- RFC 4944 defines a first version (LOWPAN_HC1) => not efficient

- RFC 6282 defines IPv6 Header Compression (LOWPAN_IPHC)

IPv6 Next Header Compression (LOWPAN_NHC) e.g UDP, Extension Headers, etc.

22

LOWPAN_IPHC Header - Dispatch

Dispatch LOWPAN_IPHC In-line IPv6 Header Fields

2 or 3 bytes

Dispatch is a selector, Identifies the type of header (e.g. LOWPAN_IPHC, LOWPAN_HC1 , etc ) immediately following the Dispatch Header.

23

LOWPAN_IPHC Header

Dispatch LOWPAN_IPHC In-line IPv6 Header Fields

0 1 1 TF CIDHLIMNH SAC SAM M DAC DAM

24

TF: Traffic Class, Flow Label

NH: Next Header

HLIM: Hop Limit

CID: Context Identifier Extension

SAC: Source Address Compression

SAM: Source Address Mode

M: Multicast Compression

DAC: Destination Address Compression

DAM: Destination Address Mode

24

LOWPAN_NHC

Typical LOWPAN_IPHC/LOWPAN_NHC Header Configuration

1 1 1 1 0 C P

LOWPAN_NHC: UDP Header Compression

e.g.

ChecksumPorts

25

26

27

6LoWPAN Paging Dispatch - RFC 8025

Introduce a new context switch mechanism for 6LoWPAN compression,

- Expressed in terms of Pages

- Signaled by a new Paging Dispatch

1 1 1 1 Page Number

Paging Dispatch with Page Number Encoding

28

Integrating the New Page Column

29

30https://www.iana.org/assignments/_6lowpan-parameters/_6lowpan-parameters.xhtml#_6lowpan-parameters-1

IPv6 over Networks of Resource-constrained Nodes (6Lo) WGaims to extend 6LoWPAN to different technologies

- RFC 7428: Transmission of IPv6 Packets over ITU-T G.9959 Networks

- RFC 7668: IPv6 over BLUETOOTH(R) Low Energy

− IPv6 over Bluetooth Low Energy Mesh Networks● draft-ietf-6lo-blemesh-01

- Transmission of IPv6 Packets over Near Field Communication

− draft-ietf-6lo-nfc-07

- An Update to 6LoWPAN ND

− draft-ietf-6lo-rfc6775-update-05

Bluetooth LE Physical

Bluetooth LE Link Layer

Bluetooth LE L2CAP

6Lo for Bt LE MeshATT

GATT

IPSS

IPv6 | routing

UDP/TCP/other

Application

Activities - Digital Protocol - RF Analog

IPv6-LLCP BindingLogical Link Control Protocol (LLCP)

Adaptation Layer for IPv6 over NFC

IPv6

Upper Layer Protocol

31

Who else is playing with 6LoWPAN?

32


IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch)

33


6LoWPAN adaptation and compression (HC) 6top

IEEE802.15.4 TSCH

IPv6

UDP ICMP

COMICoAP / DTLS

(PANA)

6LoWPANND

RPL


6TiSCH Operation sublayer (6top) provides a set of commands for upper layers to set up specific schedules

Time is divided in Slots in TSCH

Channel Hopping in TSCH transmit in different channels

Industrial Networks

34



IEEE802.15.4 TSCH

IPv6

UDP ICMP

COMICoAP / DTLS

(PANA)

6LoWPANND

RPL





Industrial Networks

IPv6 over Low Power Wide-Area Networks (lpwan)

35



IEEE802.15.4 TSCH

IPv6

UDP ICMP

COMICoAP / DTLS

(PANA)

6LoWPANND

RPL





Industrial Networks

IPv6 over Low Power Wide-Area Networks (lpwan)

The Working Group will focus on enabling IPv6 connectivity over the following

selection of Low-Power Wide-Area technologies: SIGFOX, LoRa, WI-SUN and

NB-IOT.

LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP - draft-ietf-lpwan-ipv6-static-context-hc-03

36

IP Wireless Access in Vehicular Environments (ipwave)

Transmission of IPv6 Packets over IEEE 802.11 Networks in mode Outside the Context of a Basic Service Set (IPv6-over-80211ocb) -draft-ietf-ipwave-ipv6-over-80211ocb-03

http://www.extremetech.com/wp-content/uploads/2014/02/DOT-V2I-program_100349715_m.jpghttp://www.sae.org/dlymagazineimages/11029_13957_ART.jpg

37

Tutorial of 802.11p/OCB: https://www.ietf.org/proceedings/96/slides/slides-96-its-1.pdf



Adapt the Internet to different types of networks

e.g. constrained networks/nodes


6LoWPAN

ROLL ( Routing over Low-Power and Lossy

Networks)

RPL ( IPv6 Routing Protocol for Low-Power and Lossy Networks)

IPv6 over Low power WPAN

38

39

Results of draft-ietf-roll-protocols-survey

Conclusion...

40

41

ROLL WG

42

ROLL WG

RPLdeveloped

43

DAGDirected Acyclic Graph

6LN (6LowPAN Node )

6LR (6LowPAN Router)

6LBR(6LowPAN Border Router) ROLL WG

RPLdeveloped topology

root DAG

44

DODAGDirected Acyclic Graph

6LN (6LowPAN Node )




root Destination-Oriented DAG

45

How we form the topology?


6LN (6LowPAN Node )





46


Through Control Messages


6LN (6LowPAN Node )





47




How I send the messages?

6LN (6LowPAN Node )





48



RPL Control message is a ICMPv6 message



6LN (6LowPAN Node )





49





What types of messages we need?


6LN (6LowPAN Node )





50






To Request information to join the topology -

DIS


6LN (6LowPAN Node )





51







DIS

To be able to send messages upwards -

DIO


6LN (6LowPAN Node )





52







DIS


DIO

To be able to send messages downwards

DAO


6LN (6LowPAN Node )





53







DIS


DIO


DAO

To send the messages in a secure way


6LN (6LowPAN Node )





54







DIS


DIO


DAO



How a node pick up a parent

6LN (6LowPAN Node )





55







DIS


DIO


DAO



How a node pick up a parent

Objective Function (OF)

Define how RPL nodes select and optimize routes within a RPL Instance.

Define how nodes translate one or more metrics into a rank.

Define how nodes select parents

6LN (6LowPAN Node )





56






6LoWPAN


Networks)


IPv6 over Low power WPAN Core (

Constrained RESTful

Environments) 57

58

59

core WG

CoAPdeveloped

RESTful protocol:

-Client/server & Request/Response

- GET, POST, PUT, DELETE, PATCH, iPATCH, FETCH methods

URI = host + port + path + query componentThe well-know URI: GET coap://[ipv6address]/.well-know/core

Resource Discovery → Resource Directory (RD)

Application

Request/Response

Messages

UDP

4 bytes Header Ver

Token (if any, TKL bytes) ...

TKL Code Message ID

Options (if any) ...

1 1 1 1 1 1 1 1 Payload (if any) ...

T

60

core WG

CoAPdeveloped

RESTful protocol:

-Client/server & Request/Response

- GET, POST, PUT, DELETE, PATCH, iPATCH, FETCH methods

URI = host + port + path + query componentThe well-know URI: GET coap://[ipv6address]/.well-know/core

Resource Discovery → Resource Directory (RD)

Application

Request/Response

Messages

UDP

4 bytes Header Ver

Token (if any, TKL bytes) ...

TKL Code Message ID

Options (if any) ...

1 1 1 1 1 1 1 1 Payload (if any) ...

T

Messages Types: CON, NON, ACK, RESET

Confirmable (CON) Non-Confirmable (NON)

Multicast: “All CoAP Nodes" - in IPv4: 224.0.1.187 - in IPv6: FF0X::FD

- Group Communications (RFC 7390)

Pub- Sub ArchitectureObserve functionality

61






6LoWPAN


Networks)


IPv6 over Low power WPAN

Core ( Constrained

RESTful Environments)

CoAP (The Constrained Application Protocol)

DTLSComi/CoOL

62

RFC 7925: Transport Layer Security (TLS) /Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things –

SECURITY

Authentication and Authorization for Constrained Environments (ACE) – ace WG

Practical Considerations and Implementation Experiences in Securing Smart Object Networks

dice WG

ace WG

lwig WG

core WG

Object Security of CoAP (OSCOAP)

A Security Threat Analysis for the Routing Protocol for Low-Power and Lossy Networks (RPLs)

ROLL WG

63

Requirements on the Management of Networks with Constrained Devices

(RFC7547)

Implementation Requirements

Management Architecture/System Management Protocols and Data Models

Configuration Management

Monitoring Functionality

Self-Management

Security and Access ControlEnergy Management

Software Distribution

Traffic Management

Transport Layer

https://tools.ietf.org/html/draft-bormann-lwig-7228bis-01#section-364

IoT Device Management proposals

CoMI/CoOL

65

Constrained Management Interface (CoMI)

CoMI is a network management interface for constrained devices and networks, called CoAP management Interface (CoMI)

Abstract CoMI architecture

66

Light-Weight Implementation Guidance (lwig)

Energy-Efficient Features of Internet of Things Protocols

Building Power-Efficient CoAP Devices for Cellular Networks

CoAP Implementation Guidance

Practical Considerations and Implementation Experiences in Securing Smart Object

Networks

67

T2TRG- THINGS TO THINGS RESEARCH GROUP

The Constrained RESTful Application Language (CoRAL)

RESTful Design for Internet of Things Systems

Semantic Interoperability

Guidance Design of Architecture and Data Model for Internet of Things

Systems

Some Topics:

68

Other Alliances

http://www.zigbee.org/

https://github.com/openthread/openthread

https://openconnectivity.org/ 69

Takeaways

● 6lo WG works to bring IPv6 into different types of Networks

through 6LoWPAN protocol

● ROLL WG works on routing aspects, it developed a main

protocol called RPL

● core WG works on web transfer aspects through CoAP

● ace works on security aspects

● lwig provides guidelines for implementers

● T2TRG works on open items for IoT

70

References

6lo WG https://datatracker.ietf.org/wg/6;o/documents/

ROLL WG https://datatracker.ietf.org/wg/roll/documents/

Core WG https://datatracker.ietf.org/wg/core/documents/

Lwig WG https://datatracker.ietf.org/wg/lwig/documents/

ACE WG https://datatracker.ietf.org/wg/ace/documents/

IoT Summary

https://www.w3.org/2015/04/munich/bormann.pdf

T2TRG https://datatracker.ietf.org/rg/t2trg/documents/

lpwan https://datatracker.ietf.org/wg/lpwan/documents/

ipwave https://datatracker.ietf.org/wg/ipwave/documents/

71

https://datatracker.ietf.org/rg/t2trg/documents/

https://datatracker.ietf.org/rg/t2trg/documents/

Thank you very much!

72

IoT Roadmap in the IETF - LACNIC - SLIDESslides.lacnic.net/wp-content/uploads/2017/06/ietf_iot_2017_ines.pdf · IoT(Internet of Things) Everything that can be connected will be connected

Documents