<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-oscore-edhoc" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-edhoc-02">
   <front>
      <title>Profiling EDHOC for CoAP and OSCORE</title>
      <author initials="F." surname="Palombini" fullname="Francesca Palombini">
         <organization>Ericsson</organization>
      </author>
      <author initials="M." surname="Tiloca" fullname="Marco Tiloca">
         <organization>RISE AB</organization>
      </author>
      <author initials="R." surname="Höglund" fullname="Rikard Höglund">
         <organization>RISE AB</organization>
      </author>
      <author initials="S." surname="Hristozov" fullname="Stefan Hristozov">
         <organization>Fraunhofer AISEC</organization>
      </author>
      <author initials="G." surname="Selander" fullname="Göran Selander">
         <organization>Ericsson</organization>
      </author>
      <date month="October" day="25" year="2021" />
      <abstract>
	 <t>   The lightweight authenticated key exchange protocol EDHOC can be run
   over CoAP and used by two peers to establish an OSCORE Security
   Context.  This document further profiles this use of the EDHOC
   protocol, by specifying a number of additional and optional
   mechanisms.  These especially include an optimization approach for
   combining the execution of EDHOC with the first subsequent OSCORE
   transaction.  This combination reduces the number of round trips
   required to set up an OSCORE Security Context and to complete an
   OSCORE transaction using that Security Context.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-oscore-edhoc-02" />
   
</reference>
