IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-17-0017-00-0000 Title: Report on ECHONET Lite for 2017-03 Date Submitted: March 16, 2017 Presented at IEEE 802.21 session #79 in Vancouver, BC, Canada Authors or Source(s):  Yoshikazu Hanatani (Toshiba) and Tomoki Takazoe (Panasonic) Abstract: This reports current status of ECHONET Lite System Architecture Working Group. 21-17-0017-00-0000

IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual <http://standards.ieee.org/guides/opman/sect6.html#6.3> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>  IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf>  21-17-0017-00-0000

What is ECHONET Cons.? The ECHONET consortium was established in 1997 to expand the market of home networking devices by standardizing the technology and assuring its interoperability. As of 2016, the consortium is made up of more than 160 companies across the industry and over 25 universities and research institutions. The System Architecture Working Group in the ECHONET consortium has been developing DA specification whish is a security specification for ECHONET Lite protocol. 21-17-0017-00-0000

Organization of ECHONET Cons. New DA Conformance WG DA認証構築検討WG 21-17-0017-00-0000

Outline of Device Authentication spec. If unknown devices are connected to a home area network (HAN), it may cause an attack. To prevent it, we have to authenticate devices. Each device has a certificate issued by Trusted Authority. An authenticated device can receive a device key and group keys. HAN is protected by a group key. 21-17-0017-00-0000

Current Status Device authentication (DA) specification Multicast security mechanism in IEEE 802.21m/D07 and HEMS use case in IEEE 802.21.1/D05 are applied. Waiting for the publication of IEEE 802.21-2017 and operation specification. Test specification Define a check list for certifying an implementation of DA specification. Operating specification DA conformance WG is established. Create license scheme and trust infrastructure. Ex. Who should be an operator of Root CA server, CA server, CRL server? 21-17-0017-00-0000