http:// Sensor Node: Very Small Devices on the Internet Nobuo Okabe InternetNode Inc., Yokogawa Electric Crop.

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

The Internet in Japan (2000/2) Users 19 million people Connectivity Analog Telephone : 48.1% ISDN : 25.3% Dedicated (CATV 、 ADSL 、 etc.) : 20.8% Applications Mail : 50.9% Web : 37.2% © Impress Corporation

Future of the Internet in Japan Internet (IPv6) TV, PDA, Mobile phone, PC Host Enterprises Home Hub TV1.taro.i-node.jp Always-on Network (IPv6) x 30millon (2005)

Future of the Internet in Japan 30 million households will have broadband access to the Internet by Goverment IT Policy: Changes: Diverse/innumerable devices on the Internet New services Influence upon business: New applications and services Marketing Security

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

New Requirements for Users Network device must be “ easy-to use ” if people of 30 million home use the Internet practically: User can use the devices w/o special knowledge about PC, OS and network. The devices must be non-PC (=specific purposed) network appliances. The devices must work under limited resouces (power consumption, performance, size, etc … ). Every single user can have number of devices. The devices can have end-end communication.

Micronode has network functionality Plug & play is non-PC device No need OS and PC knowledge Small and/or simple Specific purposed Limited H/W and S/W resources PC is not a enemy, but a friend

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

Will IPv6 be necessary? YES ！ Requirements To connect 30 million households (infrastructure) End-end communication （ business ） Easy to connect the network （ user ） The value of IPv6 Vast address space (40billion ^ 4) Good-by NAT Plug & play (Security)

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

Reality of the micronode Multiple vendors supplies IPv6 embedded systems: InternetNode Inc., ACCESS CO. LTD. CHUO ELECTRONICS CO.,LTD. CENTURY SYSTEMS

Example: Demo. in Interop. Tokyo (1/3) Prototype thermo sensor: 100 sensors in Interop Tokyo Monitoring the nodes, gathering data by IPv6 Power On Ethernet

Example Demo. in Interop. Tokyo (2/3) Networked Thermo sensor ×100 IPv6 Network Server Monitoring the nodes Gathering data

Example: Demo. in Interop. Tokyo (3/3) Hall 1Hall 2Hall 8Hall3Hall 4Hall 5Hall 6Hall 7 POD Catwalk POD Catwalk Thermo Sensors

Spec. of the thermo sensor CPU: Intel8051Compatible 、 40MHz 、 24bits Address Mode Memory: (512KB - ) １ MB FLASH (512KB - )1MB SRAM I/O: Ethernet 10Base-T （ x1 ） Power: Power on Ether OS: Homemade JavaVM: JDK (subset)

IPv6 Engine ： Coverage (1/2) Internet Protocol, Version 6 (IPv6) Specification (RFC 2460) Neighbor Discovery for IP Version 6 (IPv6) (RFC 2461) IPv6 Stateless Address Autoconfiguration (RFC 2462) Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (RFC 2463) IP Version 6 Addressing Architecture (RFC 2373) DNS Extensions to support IP version 6 (RFC 1886) Transmission of IPv6 Packets over Ethernet Networks (RFC 2464) IPv6 Node Information Queries (draft-ietf-ipngwg-icmp- name-lookups-05)

IPv6 Engine: Coverage (2/2) Detail of our IPv6 minimum host spec.

IPv6 Engine ： Overview (1/2) System for embedded use JAVA for application program Various I/Os (serial, parallel, 1-wire) IPv4/IPv6 Ready httpd/telnetd/ftpd Ready

IPv6 Engine: Overview (2/2) IPv6/ICMPv6ARP/IPv4/ICMPv4 TCP/UDP IPv6 Java VM Java Applications IPv6 Ethernet Driver Written in assembler Written in Java

IPv6 Engine ： Size Kernel 200KB (OS ＋ JVM ＋ Network) IPv4 : 7KB 、 IPv6 : 21KB JAVA （ Classes ＋ httpd ＋ telnetd ＋ ftpd ） 300KB Kernel work area 11KB Kernel buffers （ mbuf like ） 23KB

IPv6 Engine: Performance Data transfer by FTP (on-link) IPv6 : 28KB/s IPv4 : 28KB/s

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

Possibility of the micronode Our micronode can combine with CCD device Microphone/Speaker IR controller Environmental monitor (ex. air pollution, temperature) Bio-monitor (ex. heartbeat, breathing) IR Controller Environ. Monitor Inter- net Server

Outline: When broadband access is deployed What will happen? What will be new requirements? Will IPv6 be necessary? Will micronode w/ IPv6 have reality? What micronode can be possible? What is issues/challenge?

Issues/Challenges (1/6) Managing huge number of nodes Some application need servers to manage micronodes. More than 10^5 micronodes (1% of the government ’ s goal) Servers can not gather data from huge number of nodes by real-time fashion. Every single micronode have to be smart for rate limitation.

Issues/Challenges (2/6) IPv6 Minimum host spec. Entire IPv6 spec. can not be implemented under limited resouces. What part of spec. is mandate? Harmless to other IPv6 nodes Reasonable to the future of the Internet

Issues/Challenges (3/6) Security bottom line IPsec is too heavy for our micronode because of limited resources (especially performance). Authentication is mandate. Encryption may NOT be mandate. From business point of view, NAT and IPv4/IPv6 translator should not be ignorable. It also discourages use of IPsec. Current solution: Security functionality in application layer

Issues/Challenges (4/6) Updating firmware from remote site There are many reasons to update firmware. Bug fix, new function, new service, …… Legacy way of support (on-site or send- back) will not match cost because of huge number of micronodes.

Issues/Challenges (5/6) Updating firmware from remote site (Continued) To be considered Low impact against the network Recovery from update fails Scalable Re-using/combining existing technologies We do not see right answer yet.

Issues/Challenges (6/6) To be implemented DNS Discovery NTP