oic and iotivity - etsi...ipv6 •so ietf has worked hard to capture the requirements and align back...

18
OIC - Iotivity Open Standard and Open Source. Stephane Lejeune stlejeun at cisco.com Architect – Chief Technology and Architecture Office 2015.12.11 - ETSI M2M Workshop How can they leverage each other?

Upload: others

Post on 11-Aug-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

OIC - IotivityOpen Standard and Open Source.

Stephane Lejeune stlejeun at cisco.com

Architect – Chief Technology and Architecture Office

2015.12.11 - ETSI M2M Workshop

How can they leverage each other?

Page 2: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 2© 2013-2014 Cisco and/or its affiliates. All rights reserved.

Past Internet success is partly due to: Network layer convergence!

2

Application/Presentation

Session

Transport

LLC

MAC

Physical

Network Layer IP

IP ISO CLNSXNS

X.25DECnet

Chaosnet

Page 3: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 3© 2013-2014 Cisco and/or its affiliates. All rights reserved.

History repeats:Re-build an IoT hourglass model

3

IPv6

• So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable version of the Internet):

• IPv6/802.15.4

• IPv6/ITU-T G.9959

• IPv6/BLE

• IPv6/DECT-ule,

• IPv6/NFC, Foo, DetNet, …

Page 4: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 4© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IoT Hourglass model isn’t enough

• Many organizations are (re)defining terms for basic concepts like temperature and on/off within their own namespace, which then becomes an inseparable part of the data model.

• Different protocols are available to address different use case requirements

• Data models tied to dedicated protocols result in all-or-nothing interoperability

• Common protocols but often different application semantics and data models

4

IPv6

Page 5: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 5© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IoT technologies != Internet Technologies

PUSHING A SQUARE PEG IN A ROUND HOLE

• In IoT devices

• Bandwidth is 250 kbit/s, not 250 Mbit/s

• Program memory size is 256 kB, not 256 MB

• Requires a scale down 1000 x of:

• Protocols complexity

• Packets traffic

• IoT is not a scaled down version of the whole Internet!

5

Image source: http://www.edensunshine.com/

Page 6: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 6© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IoT still suffered of a huge fragmentation issue!

• But the richness of higher layer protocols are still at the origin of the fragmentation in IOT

• More work is needed to get to achieve higher layer interoperability and reusability.

6

IPv6 IPv6

UDP

CoAP

Data ModelProfiles

Need for SimplicityNew SDO/OSS?

Page 7: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 7© 2013-2014 Cisco and/or its affiliates. All rights reserved.

An world composed of a complex mix:

Small communities (resulting in project often quickly starting but quickly fade out too)

Fragmented solutions (many OSS projects that each solve 20% of a problem but cannot be used together)

Hidden gaps (sometimes critical functionality with too few eyes on them resulting in security flaws)

But which manages to:

Leverage a vast community

Innovating at a very fast pace

Sometimes resulting in de facto

Challenge of Open Source Software (OSS)

Page 8: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 8© 2013-2014 Cisco and/or its affiliates. All rights reserved.

• Common goal is to make

it easy for devices to

connect and

interoperate - regardless

of vendor, OS, hardware,

etc.

= Interoperability

OIC

Addressing the Challenge of Communications

Page 9: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 9© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IoT Device Interoperability

The Strategy for Building Device Interoperability

Specification Open Source Project Certification

• Broad spectrum of industry leaders providing guidance

• Common communications protocols, approaches for security and identity, and service-level protocols, object models & developer APIs

• Open specification that anyone can implement

• Provides a fast path to market for developers and manufacturers

• Open source development promotes faster innovation via community driven development

• Connectivity framework that abstracts complexity

• IP protection & branding for certified devices

• Certification = a device implementation as defined in the specification and released into the open source

OIC is a specification & open source project that delivers “just-works” interconnectivity for developers, manufacturers and end users.

Page 10: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 10© 2013-2014 Cisco and/or its affiliates. All rights reserved.

Cross pollination

Into spec:

Review loops for spec

Consistent Interpretation

Gap review

Testability

Feasibility / Prototyping

Innovative ideas from wider community innovation

Into code:

Market relevance

Wider architectural consistency

Wider adoption in other OSS

Interoperability across vendors

Certification

Test-Suite

Standards

Open Source

Page 11: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 11© 2013-2014 Cisco and/or its affiliates. All rights reserved.

OIC Intellectual Property Rights Policy

• OIC is a royalty free organisation

• Standard – RANDZ

• IP cross licensing covering “Compliant Portions” of a member company’s products

• Iotivity: Open Source – Apache 2.0

• Copyright & Patent pledge

for all contributed code

from day one

Page 12: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 12© 2013-2014 Cisco and/or its affiliates. All rights reserved.

Synchronization challenge across the two organizations

Different cultures:

OSS geeks != SDO geeks

Aristocracy vs Meritocracy

Work already done differently

Certification

Test-Suite

Standards

Open Source

Open Integration Cycles

OIC

Page 13: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 13© 2013-2014 Cisco and/or its affiliates. All rights reserved.

A challenging opportunity: Open Source Working Group

OIC

Image source: www.motortrend.com

Page 14: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 14© 2013-2014 Cisco and/or its affiliates. All rights reserved.

OSS

Cert

Open Integration Cycles

SDO

OSS

Cert

SDO

OSS

Cert

SDO

R

e

q

u

i

r

e

m

e

n

t

s

U

s

e

C

a

s

e

s

Short delivery cycles of Synced bundle:

Spec’ed, Implemented, Tested

Page 15: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 15© 2013-2014 Cisco and/or its affiliates. All rights reserved.

Participate!

• Become a member

• Membership levels:

– Gold

– Platinum

– Diamond

• http://openinterconnect.org/join

• Join the Open Source Project

– Download the code and get started

– Licensed under Apache 2.0 licence

– Contribute!http://iotivity.org

Get the Standard and Software Stack

Spec 1.0

http://openinterconnect.org/developer-resources/specs/

Iotivity 1.0.0

https://www.iotivity.org/downloads

☑O

IC

Page 16: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Thank you.

Page 18: OIC and Iotivity - ETSI...IPv6 •So IETF has worked hard to capture the requirements and align back on IPv6 (the scalable ... security flaws) But which manages to: Leverage a vast

Cisco Confidential 18© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IP Coverage best in industry

OIC Others

Reference code is open source, permissive licence. ✓ ✓

Reference code comes with a licence to use patents as long as

certification is passed.✓ ✓

Reference code comes with a licence to use patents even without

certification (forking).✓ ☒

Reimplementation of the specification can get certified and obtain

patent licensing.✓ ☒

Patents from member companies who do not contribute code are still

licensed if needed to implement the specification.✓ ☒

Patents from affiliate or parent companies of member companies are

licensed.✓ ☒