Iot support technologies

IoT support technologies
in IETF
IETF 미러포럼 창립총회 및 기술 워크샵
ETRI Protocol Engineering Center
홍용근(yghong@etri.re.kr)
2014.5.29.

Hong, Yong-Geun @ ETRISlide 2
2014-5-29
목 차
• 개 요
• 사물인터넷(IoT) 기술
• 인터넷 관점에서의 IoT
• IoT 지원을 위한 IETF 기술
– IETF 6LoWPAN WG
– IETF 6lo WG
– IETF 6tisch WG
– IETF ROLL WG
– IETF CoRE WG
– IETF lwig WG
• IETF 88, 89차 회의 주요 결과

2014-5-29
사물인터넷 (IoT) 개요
• 사물인터넷 (Internet of Things, IoT)
– 사람, 사물, 공간, 데이터 등 모든 것이 인터넷으로 서로 연결되어,
정보가 생성∙수집∙공유∙활용되는 초연결 인터넷
< Source: 사물인터넷 기본계획 (2014. 5. MSIP) >

2014-5-29
사물인터넷 (IoT) 전망

2014-5-29
인터넷 패러다임 변화
초고속정보통신망
전략수립(‘95)
• 인터넷포털
• 전자상거래
• 전자정부
• 인터넷뱅킹 등
광대역통합망
전략수립(‘04)
사물인터넷
전략수립(’14)
• 인터넷TV
• 스마트폰
• 모바일앱/SNS
• N스크린 등
• 웨어러블 기기
• 스마트 카/집/학교
• ICT 힐링/차, 만리안
• D.I.Y 서비스 등
< 정보화 사회 >
< 스마트 사회 >
< 초연결 사회 >
< 인터넷1.0 >
초고속인터넷
< 인터넷2.0 >
광대역/모바일인터넷
< 인터넷3.0 >
사물인터넷
구분 인터넷1.0 인터넷2.0 인터넷3.0
시장
주도
제품
H/W 컴퓨터(PC연결) 스마트폰(사람연결)
센서,웨어러블등
(모든사람-사물연결)
S/W
(기반)Windows,Linux
(응용)Explorer,Netscape
(기반)Android,iOS
(응용)페이스북,카카오톡
다양한응용S/W
등장예상
국가전략 초고속정보통신망전략(‘95) 광대역통합망전략(‘04) 사물인터넷전략(‘14)
신서비스 인터넷포털/뱅킹,전자정부등 IPTV,모바일앱,SNS등
스마트홈/카,스마트에너지,
생산공정,생활제품등
< Source: 사물인터넷 기본계획 (2014. 5. MSIP) >

2014-5-29
• 개 요
– IETF 6LoWPAN WG
– IETF 6lo WG
– IETF 6tisch WG
– IETF ROLL WG
– IETF CoRE WG
– IETF lwig WG

2014-5-29
사물인터넷 (IoT) 기술
• IoT 기술 특성 (1/2)
– M2M/RFID/USN/NFC 개념 등이 인터넷으로 연결․통합된 차세대
기술로 발전
• 물리적 환경을 넘어 디지털, 가상환경으로의 확장을 통해 사물,
데이터, 시맨틱 사이에 지식을 결합하고 통합하여 개인과 상황에
맞는 스마트서비스를 창조하기 위한 인프라 기술
구분 RFID/USN/M2M 사물인터넷
통신/네트워크 근거리망,이동망중심 ⇨ 인터넷중심
디바이스의형태 센서중심 ⇨
센서와액츄에이터의PhysicalThing과데이터와프로세스
등을포함한Virtualthing
디바이스의서비스
구동수준
단순정보수집/수동적 ⇨ 자율판단하는지능보유/자율적
서비스플랫폼 모니터링정보처리 ⇨ 의미기반모니터링및자율제어
서비스관리규모 수천만개의사물 ⇨ 수백억이상사물
서비스적응성 통시적서비스제공 즉시적스마트서비스제공
< Source: 사물인터넷 중장기 R&D 전략, MSIP >

2014-5-29
• IoT 기술 특성 (2/2)
– IoT가 실제 생활영역에 적용되면서 다양한 경제적 가치, 효율성
증대, 편의성 증대 등이 현실화될 전망
• 모든 것이 연결되는 과정에서, 방대한 비정형 데이터의 처리‧분석
(빅데이터) 및 효과적인 정보처리(클라우드) 산업도 막대한 시장 형성
– IoT 생태계는 이용기관‧기업별 개별적‧폐쇄적에서 개방형 IoT 서
비스(Everything as a Service)생태계로 전환
구분 AS-IS TO-BE
개념도 ⇨
서비스
방식
이용기관이직접개발․구축 ⇨
이용기관이서비스를구매․이용하는클라우드
방식(EverythingasaService)
SW 폐쇄형(개별플랫폼) ⇨ 개방형(공통플랫폼)
특징
초기개발‧구축비용과다
지속적인운영‧유지비용부담
⇨
개발·구축비용최소화(규모의경제)
호환성제고로데이터/서비스연계활용

2014-5-29
• IoT 기술 분류 (1/2)
IoT
응
용
서
비
스
IoT
플
랫
폼
IoT 네트워크
IoT
디
바
이
스
IoT 응용 플랫폼
IoT 서비스 프레임워크
IoT 공통 플랫폼

2014-5-29
• IoT 기술 분류 (2/2)
– IoT 서비스 프레임워크
• 산업 IoT, 개인 IoT, 공공 IoT 등 응용분야별 IoT 기반 서비스를 제공하
기 위한 기본 서비스 프레임 워크
– IoT 공통 플랫폼
• 산업 IoT, 개인 IoT, 공공 IoT 사물과 서비스에 대한 효율적 개방·공유·
활용을 지원하는 공통 플랫폼
– IoT 네트워크
• 산업 IoT, 개인 IoT, 공공 IoT 서비스 제공을 위한 고신뢰 IoT 통신 및
IoT 서비스 생성 지향 네트워크 시스템
– IoT 디바이스
• 사물을 지능화시켜 스마트 센싱 및 엑츄에이션 제공하는 플랫폼
– IoT 보안기술
• 안전하고 프라이버시 유출 위협이 없는 신뢰성 높은 IoT서비스를 제공
하기 위한 보안기술

2014-5-29
사물인터넷 (IoT) 기술 현황 및 전망
• IoT 서비스 기술
– 과거 별도 단말을 이용하는 폐쇄적 이용환경에서 스마트폰 등장으
로 누구나 쉽게 서비스를 개발·활용할 수 있는 개방형 생태계로 변
화
– 어떤 IoT가 미리 정해진 서비스를 제공하기 보다는 IoT 디바이스와
사용자 관점의 서비스가 필요에 따라 동적으로 바인딩 되고 다중의
IoT 서비스가 조합, 활용되어 사용자의 테스크를 지원하는 형태로
발전할 전망
• IoT 플랫폼 기술
– 단일 사업자별 폐쇄형 서비스 플랫폼 구조에서 글로벌 의미검색과
등록을 지원하기 위한 개방형 의미기반 협업 플랫폼 구조 및 표준
개발 추세
– 개방형 API 기반 인터페이스를 통해 전 세계 IoT 단말로부터 데이
터를 수집하여 사용자와 사물 간 정보공유를 통해 스마트서비스를
제공하기 위한 방향으로 개발 중

2014-5-29
사물인터넷 (IoT) 기술 현황 및 전망
• IoT 네트워크 기술
– 모든 사물이 인터넷에 연결되는 과정에서 트래픽 급증이 예상됨에
따라 SW기반으로 트래픽을 유연하게 처리하는 기술 등을 개발 중
– 통신환경이 열악한 산간·오지 등으로 연결이 확대됨에 따라 효과
적으로 수많은 디바이스를 연결하기 위한 저전력(배터리 수명 10
년 이상)/장거리(10Km 이상) 비면허 대역 통신 요구 증대 예상
• IoT 단말 기술
– 단순 사물 정보 수집의 단순 기능에서 다양한 네트워크 융합형 서
비스 제공을 위한 개방형 단말 기술 개발 추세
• IoT 보안 기술
– 다양한 네트워크 환경에서 공유되는 사물 및 데이터에 대한 안전한
활용과 사용자 장치의 신뢰성을 보장하기 위한 보안 기술 개발 추
세

2014-5-29
국제 IoT 표준화 현황

2014-5-29
IoT Definition
IoT
A global infrastructure for the information society,
enabling advanced services by interconnecting
(physical and virtual) things based on, existing and
evolving, interoperable information and
communication technologies [ITU-T Y.2060]
M2M (service layer)
M2M
Communication between two or more
entities that do not necessarily need
any direct human intervention
MTC
A form of data communication which
involves one or more entities that do not
necessarily need human interaction
M2M
Information exchange between a Subscriber
station and a Server in the core network
(through a base station) or between Subscriber
station, which may be carried out without any
human interaction [IEEE 802.16p]
IoT
a world-wide network of interconnected objects
uniquely addressable, based on standard
communication protocols
[draft-lee-iot-problem-statement-05.txt]
IoT
A global network infrastructure, linking
physical and virtual objects through the
exploitation of data capture and
communication capabilities
[EU FP7 CASAGRAS]

2014-5-29
• 개 요
– IETF 6LoWPAN WG
– IETF 6lo WG
– IETF 6tisch WG
– IETF ROLL WG
– IETF CoRE WG
– IETF lwig WG

2014-5-29
The Effect on Internet Standards
• Internet of Things will use current Internet protocol stack, to a
large extent
• We do not always need more research or standards!
• Expect some challenges and changes, however
– Bigger capability variations than in the current internet, no human in the
loop for most applications
• Many efforts already ongoing
– Routing (RPL), IP over Foo (6LOWPAN), COAP, …
– Link layers, specific applications, specific architectures, policy issues
discussed outside the IETF

2014-5-29
IoT in IETF Perspective
• There are tremendous cost and other advantages to using IP for
all communications
• Yet we'll have to make sure our technology scales to the
challenge
• However, there are several problems
– Objects/Things in IoT may be small size
• the limit power, the limit memory ..
– We don’t know the exact behavior of IoT and IoT service requirement
• Service model, communication model ..

2014-5-29
Intersection using IP
[Source : Interconnecting Smart Objects with IP]

2014-5-29
Why is IP layering Important for IoT
• Regarding the physical/virtual devices(smallest objects) as well
as the links interconnecting these devices
– These architectures could not support the new links without performing
protocol translation, which is a very costly and inefficient approach
3/4G mobile device
IEEE 802.11 based device
IEEE 802.15.8 device
PLC based device
Intersection = IP
[Source : Interconnecting Smart Objects with IP]

2014-5-29
IP solution for IoT
• Considerations
– Evolvability
– Scalability
– Diversity of Applications
– Diversity of Communication technologies
– Interoperability
– Potentially lossy communication technology
– Life Time
– Low-Power consumption
– Low cost

2014-5-29
Interoperability Challenges
• A capability mismatch between different devices
• Communications and processing bandwidth mismatch
• Different internetworking protocol choices
• Solutions that are only suitable for some networks

2014-5-29
Capability Differences
• MTU differences
• Simplified vs. full blown web protocol stack (CoAP/UDP vs.
HTTP/TCP)
• Single stack vs. dual stack
• Sleep schedule
• Security protocols
• Processing and communications bandwidth

2014-5-29
Challenges for IoT
• The IP architecture was arguably not designed for IoT
devices/objects and network
• IoT networks and their applications give rise to challenges both
at the node and the network level
• Therefore, need to light-weight Implementation of Internet
Protocol

2014-5-29
• 개 요
– IETF 6LoWPAN WG
– IETF 6lo WG
– IETF 6tisch WG
– IETF ROLL WG
– IETF CoRE WG
– IETF lwig WG

2014-5-29
Motivation
• Current Internet Protocol use too much
– Energy
– Spectrum
– Costs
• Wireless technology
• Problems
– Constrained nodes
• little power (~ μW), lots of sleeping
• little ROM (code space), RAM (state)
– Constrained networks
• high loss
• not an Ethernet (multicast, reliability, ...)
[Source : Carsten Bormann, Getting Started with IPv6 in 6LowPAN, 2011/3]

2014-5-29
Constrained network
• Node
– Low performance, low RAM, low ROM
– sleep a lot (vs. “always on”) due to battery operation
• Network
– ~100 kbits/s, high loss, high link variability
– May be used in an unstable radio environment
– Physical layer packet size may be limited (~100 bytes)
• LLN : Low power and Lossy Network

2014-5-29
Constrained network example: IEEE 802.15.4
• Characteristics
– popular low-power (~ 1 mW) radio
– 0.9 and 2.4 GHz bands
• 868 MHz: Europe (1 % duty cycle, 20 kbit/s)
• 900 MHz: US (40 kbit/s)
• 2.4 GHz: World (256 kbit/s)
– up to 127-byte packets

2014-5-29
Constrained node/networks in IETF
• 6LoWPAN WG
– IETF Internet area, L2/L3 interface
• 6lo WG
– IETF Internet Area, L2/L3 interface in various access technologies
• 6tisch WG
– IETF Internet Area, IPv6 over the TSCH mode of IEEE 802.15.4e
• ROLL WG
– IETF Routing area, L3 routing
• CoRE WG
– IETF Application area, L7 application
• LWIG WG
– IETF Internet area, Current practice of Light-weight Implementation

2014-5-29
6LoWPAN WG (1/4)
• IPv6 over Low-Power Area Networks (IEEE 802.15.4)
– RFC 4919 : IPv6 over Low-Power Wireless Personal Area Networks
(6LoWPANs): Overview, Assumptions, Problem Statement, and Goals
– RFC 4944 : Transmission of IPv6 Packets over IEEE 802.15.4
Networks
– RFC 6282 : Compression Format for IPv6 Datagrams over IEEE
802.15.4-Based Networks
– RFC 6568 : Design and Application Spaces for IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs)
– RFC 6606 : Problem Statement and Requirements for IPv6 over Low-
Power Wireless Personal Area Network (6LoWPAN) Routing
– RFC 6775 : Neighbor Discovery Optimization for IPv6 over Low-
Power Wireless Personal Area Networks (6LoWPANs)
– draft-ietf-6lowpan-btle-12 : Transmission of IPv6 Packets over
BLUETOOTH Low Energy

2014-5-29
6LoWPAN WG (2/4)
• RFC 4944: make 802.15.4 look like an IPv6 link
• Basic Encapsulation
– Efficient representation of packets < ~100 bytes
– First approach to stateless Header Compression
• Fragmentation (map 1280 byte MTU to < 128 bytes)
– Datagram tag/Datagram offset
• Mesh forwarding
– Identify Originator/Final Destination
• Minimal use of complex MAC layer concepts
– cf. RFC 3819 “Advice for Internet Subnetwork Designers”

2014-5-29
6LoWPAN WG (3/4)
• RFC 6282 : Header compression
• Traditional header compression (ROHC, RFC 3095 etc.) is
flow-based stateful
– exploit redundancies between packets
• RFC 4944 header compression is stateless
– exploit intra-packet redundancies only
– Can’t compress global prefix
• Header compression
– Remove redundant information across the link,
network, and transport layer
– Assume common values for header fields and
define compact forms of those value

2014-5-29
6LoWPAN WG (4/4)
• RFC 6775 : Neighbor Discovery Optimization for IPv6 over
Low-Power Wireless Personal Area Networks (6LoWPANs)
• Neighbor Discovery optimization with minimal multicast usage
– IPv6 neighbor discovery
– Address mechanism
– Duplicate address detection

2014-5-29
6lo WG (1/3)
• IPv6 over Networks of Resource-constrained Nodes

2014-5-29
6lo WG (2/3)
• IPv6-over-foo
– Transmission of IPv6 packets over ITU-T G.9959 Networks
(draft-brandt-6man-lowpanz)
• ITU-T G.9959 is the PHY&MAC of Z-Wave
– IPv6 over MS/TP Networks (draft-ietf-6man-6loba)
• Develop a low-cost wired IPv6 solutions for commercial building control
applications
• BACnet is the ISO/ANSI/ASHRAE data communication protocol for
Building Automation and Control networks
• MS/TP (Master-Slave/Token-Passing) is a widely used data link defined in
BACnet
– IPv6 over dect-ule (raft-mariager-6lowpan-v6over-dect-ule)
• DECT(Digital Enhanced Cordless Telecommunications) : A part of the
IMT-2000 family
• DECT-ULE (Ultra Low Energy) : A low power communication technology
for multi-year battery life time applications

2014-5-29
6lo WG (3/3)
• Other issues
– 6LoWPAN Simple Fragment Recovery
– Generic Header Compression
– LOWPAN-MIB

2014-5-29
6tisch WG (1/3)
• IPv6 over the TSCH mode of IEEE 802.15.4e
• Work items
– Produce "6TiSCH architecture" to describe the design of 6TiSCH
networks
– Produce an Information Model containing the management
requirements of a 6TiSCH node
– Produce "Minimal 6TiSCH Configuration" defining how to build a
6TiSCH network using the Routing Protocol for LLNs (RPL) and a
static TSCH schedule
• Non-milestone work items
– Implementers guide
– Coexistence guide

2014-5-29
6tisch WG (2/3)
• Timeslotted Channel Hopping

2014-5-29
6tisch WG (3/3)
• Working group documents
– Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e
(draft-palattella-6tisch-terminology-01)
– An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4e
(draft-thubert-6tisch-architecture-01)
– 6TiSCH Operation Sublayer (6top) Interface
(draft-ietf-6tisch-6top-interface-00)
– 6TiSCH Resource Management and Interaction using CoAP
(draft-ietf-6tisch-coap-00)

2014-5-29
ROLL WG (1/4)
• Routing Over Low power and Lossy networks
– RFC 5548 : Routing Requirements for Urban LLN
– RFC 5673 : Industrial Routing Requirements in LLN
– RFC 5826 : Home Automation Routing Requirements in LLN
– RFC 5867 : Building Automation Routing Requirements in LLN
– RFC 6206 : The Trickle Algorithm
– RFC 6550 : RPL: IPv6 Routing Protocol for LLN
– RFC 6551 : Routing Metrics Used for Path Calculation in LLN
– RFC 6552 : Objective Function Zero for the Routing Protocol for LLN
(RPL)
– RFC 6719 : The Minimum Rank with Hysteresis Objective Function
– RFC 6997 : Reactive Discovery of Point-to-Point Routes in LLN
– RFC 6998 : A Mechanism to Measure the Routing Metrics along a Point-
to-Point Route in a LLN

2014-5-29
ROLL WG (2/4)
• RPL: IPv6 Routing Protocol for LLN
– Target applications areas (requirements 분석)
• Industrial, Home Automation, Building Automation, Urban
– Routing protocol 요구 사항
• IPv6 routing architecture
• Deliberate choice of 4 main application areas
• Support of unicast/anycast/multicast
• Adaptive routing with support of different metrics (latency, reliability, …)
• Support of constrained-based routing (energy, CPU, memory)
• Support of P2MP, MP2P and P2P with asymmetrical ECMP
• Scalability
• Discovery of nodes attributes (aggregator)
• 0-config (Warning not to add too many options !)
• Performance: indicative (lesson learned from the Internet)
• Security

2014-5-29
ROLL WG (3/4)
• RPL: IPv6 Routing Protocol for LLN (cont’d)
– RPL builds Directed Acyclic Graphs (DAG)
• Tree would have been simpler but need for redundancy
• RPL supports the concept of DAG instances (a colored DAG), concept
similar to MTR
• Allows a node to join multiple colored DAG with different Objective
Functions
• And within an instance, there might be multiple DODAG (Destination
Oriented DAG)
• A node may belong to more than one RPL instance
• Packets are tagged to follow a specific instance (defined at the application
layer): no loops between instances
– RPL Control message are ICMPv6 messages
• RPL message={Base, Options}
• DIS, DIO, DAO, DAO-ACK, + The 4 secured versions

2014-5-29
ROLL WG (4/4)
• Building a DAG-Upward routing
[Source : JP Vasseur, IoT Workshop RPL Tutorial, 2011/4]

2014-5-29
CoRE WG (1/4)
• Constrained RESTful Environments
– REST(Representational State Transfer)
• WWW와 같은 hyper-media의 S/W Architecture의 한 형식
• HTTP를 활용, 네트워크 상의 여러 자원(resource)에 대해 조작
(manipulation) 서비스 를 제공
– Constrained IP network 상에서 resource-oriented application의
framework 제공
• Constrained IP networks
– 제한된 패킷 크기, 손실 위험이 상대적으로 크고, wake-up/sleeping 동작하
는 많은 수의 devices로 구성
• Devices의 resource에 대한 조작(manipulation)을 위한 Application
Protocol을 정의
– RFC 6690 : Constrained RESTful Environments (CoRE) Link Format
– draft-ietf-core-coap-18 : Constrained Application Protocol (CoAP)

2014-5-29
CoRE WG (2/4)
• CoAP 프로토콜 설계
– Devices의 resource에 대한 create, read, update, delete 기능
– Device의 resource 변화를 다른 device에게 보고
– Device group의 resource 조작을 위한 non-reliable multicast 기능
– UDP 상에서 동작, 대용량 chucks 데이터를 위해 optional TCP 사용
도 고려
– Device’s description에 대한 advertise/query를 위한 CoAP 사용 방법
정의
– Devices과 통신을 위한 HTTP REST API, translation 명세

2014-5-29
CoRE WG (3/4)
• CoRE Transaction model
– Transport
• CoAP is defined for UDP
– Messaging
• Simple message exchange between end-points
• CON, NON, ACK, RST

2014-5-29
CoRE WG (4/4)
• Working group documents
– CoAP protocol
(draft-ietf-core-coap-18 (RFC Editor Queue))
– Group Communication for CoAP
(draft-ietf-core-groupcomm-18)
– Guidelines for HTTP-CoAP Mapping Implementations
(draft-ietf-core-http-mapping-03)
– CoRE Interfaces
(draft-ietf-core-interfaces-01)
– Observation
(draft-ietf-core-observe-13)
– Representing CoRE Link Collections in JSON
(draft-ietf-core-links-json-01)
– CoRE Resource Directory
(draft-ietf-core-resource-directory-01)

2014-5-29
LWIG WG (1/4)
• Light-Weight Implementation Guidance (lwig)
• draft-ietf-lwig-cellular-00 : Building Power-Efficient CoAP
Devices for Cellular Networks
• draft-ietf-lwig-guidance-03 : Guidance for Light-Weight
Implementations of the Internet Protocol Suite
• draft-ietf-lwig-ikev2-minimal-00 : Minimal IKEv2
• draft-ietf-lwig-terminology-05 : Terminology for Constrained
Node Networks
• Charter and purpose of lwig
– focuses on helping the implementors of the smallest devices.
– The goal is to be able to build minimal yet interoperable IP-capable
devices for the most constrained environments
– Collect experiences from implementors of IP stacks in constrained devices

2014-5-29
LWIG WG (2/4)
• Guidance for Light-Weight Implementations of the Internet
Protocol Suite
– Data plane protocols
• Link adaptation layer : 6loWPAN
• Network layer : IPv4 and IPv6
• Transport layer : TCP and UDP
• Application layer : CoAP
– Control plane protocols
• Link layer support : 6loWPAN-ND
• Network layer : ICMP, ICMPv6, IGMP/MLD
• Routing : RPL, AODV/DYMO, OLSRv2
• Host configuration and lookup services : DNS, DHCPv4, DHCPv6
• Network management : SNMP, netconf

2014-5-29
LWIG WG (3/4)
• Building Power-Efficient CoAP Devices for Cellular Networks
– Link layer assumption
• Public networks
• Point-to-point link model
• Radio technology
– Scenarios
• Real-Time Reachable Devices
• Sleepy Devices
– Discovery and registration
• Manual Configuration
• Manufacturer Server
• Delegating Manufacturer Server
• Common Global Resolution Infrastructure

2014-5-29
LWIG WG (4/4)
• Terminology for Constrained Node Networks
– Classes of constrained devices
– Classes of energy limitation

2014-5-29
• 개 요
– IETF 6LoWPAN WG
– IETF 6lo WG
– IETF 6tisch WG
– IETF ROLL WG
– IETF CoRE WG
– IETF lwig WG

2014-5-29
6lo WG
• IPv6-over-foo
– Transmission of IPv6 Packets over BLUETOOTH Low Energy
(draft-ietf-6lo-btle-00)
– Bluetooth v4.1 : Dual-mode and Link-layer topology changes

2014-5-29
6tisch WG
• Presentations
– Overall Architecture and Context [15min]
• <draft-ietf-6tisch-terminology-01> (Maria-Rita Palattella)
• <draft-ietf-6tisch-architecture-01> (Pascal Thubert)
– Information and Data Models [20min]
• <draft-wang-6tisch-6top-interface-02> (Xavi Vilajosana)
• <draft-wang-6tisch-6top-sublayer-00> (Qin Wang)
– Security [20min]
• Security discussions: summary and outlook (Michael Richardson, Michael
Behringer)
– Report on plugfest [30min]
• Overview and goals (Xavi Vilajosana)
• Presentation of outcome <plugfest participants>

2014-5-29
core WG (1/2)
• Phase change
– RFC editor processing: draft-ietf-core-coap-18 (2013-07-11)
– From : Oh I have this cool idea, how about that
– To : I have a deployment with a problem to solve. Here is how we
solved it
• Issues 1 – WG documents
– Observing Resources in CoAP (draft-ietf-core-observe-12)
– Blockwise Transfer (draft-ietf-core-block-14)
– Group Communication for CoAP (draft-ietf-core-groupcomm-18)
– HTTP-CoAP Mapping (draft-ietf-core-http-mapping-03)
– CoRE Resource Discovery (draft-ietf-core-resource-directory-01)

2014-5-29
core WG (2/2)
• Issues 2 – New works
– No-response option for CoAP (draft-tcs-coap-no-response-option-05)
– CoAP Transport URIs
(dra12silverajan2core2coap2alterna9ve2transports)
– A Link-Format Attribute for Locating Things (draft-fossati-core-geo-
link-format-attribute-03)
– Alternate Transports (draft-silverajan-core-coap-alternative-transports)
– Sleepy devices
• Lots of individual drafts
– CoAP Management Interface (draft-vanderstok-core-comi-01)

2014-5-29
lwig WG
• Working document
– Minimal IKEv2 (draft-ietf-lwig-ikev2-minimal-01)
– lwig terminology (draft-ietf-lwig-terminology-07)
– Energy Efficient Implementation Guidance (draft-ietf-lwig-energy-
efficient-00)
– Building Power-Efficient CoAP Devices for Cellular Networks (draft-
ietf-lwig-cellular-01)
• Individual drafts
– draft-hong-lwig-sleepmode-control-00
– draft-hong-lwig-sleepynode-problem-statement
– draft-kovatsch-lwig-coap
– draft-ma-lwig-3gpplink-imply

2014-5-29
IRTF icnrg
• ICN based Architecture for IoT (draft-zhang-iot-icn-architecture-
00)
– Covers general IoT Requirements, current status-quo
– Proposes a ICN based framework unifying heterogenous IoT systems
– Example based on location context service based on MobilityFirst platform
• Contextualized Information-Centric HomeNets (draft-ravindran-
cibus-01.txt)
– Homenets a good ecosystem where heterogeneous systems, users, and
devices interact in context and policy sensitive manner.
– Opportunity for ICN as a homegenous platform to integrate
BAN/PAN/LAN/WAN systems.
– Proposes a CIBUS service layer for Name Management, Context
Processing/Monitoring, Service management, and Policy based
Routing/forwarding

2014-5-29
geonet bof
• Internet-wide Geo-networking bof

2014-5-29
Conclusions
[Source : Jari Arkko, Permissionless Innovation for the IoT, IoT-Week 2013]

2014-5-29
Q & A
Thank you
Yong-Geun Hong
Protocol Engineering Center
Electronics and Telecommunications Research Institute
E-mail: yghong@etri.re.kr
Tel: +82 42 860 6557, Fax: +82 42 861 5404
Contact Information

Iot support technologies

Related slideshows

More Related Content

Iot support technologies