<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ohba-6tsch-security" target="https://datatracker.ietf.org/doc/html/draft-ohba-6tsch-security-01">
   <front>
      <title>Security Framework and Key Management Protocol Requirements for 6TSCH</title>
      <author initials="S." surname="Chasko" fullname="Stephen Chasko">
         </author>
      <author initials="S." surname="Das" fullname="Subir Das">
         <organization>ACS</organization>
      </author>
      <author initials="R." surname="Marin-Lopez" fullname="Rafael Marin-Lopez">
         <organization>University of Murcia</organization>
      </author>
      <author initials="Y." surname="Ohba" fullname="Yoshihiro Ohba">
         <organization>Toshiba</organization>
      </author>
      <author initials="P." surname="Thubert" fullname="Pascal Thubert">
         <organization>cisco</organization>
      </author>
      <author initials="A. E." surname="Yegin" fullname="Alper E. Yegin">
         <organization>Samsung</organization>
      </author>
      <date month="July" day="12" year="2013" />
      <abstract>
	 <t>   Since 6TSCH forms layer 3 meshes over IPv6, use of key management
   protocols defined at layer 3 or above matches the target architecture
   so they can apply for the process by a new device of joining the mesh
   to extend it.  This document details that particular operation within
   the whole 6TSCH architecture.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ohba-6tsch-security-01" />
   
</reference>
