<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-object-security" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-object-security-16">
   <front>
      <title>Object Security for Constrained RESTful Environments (OSCORE)</title>
      <author initials="G." surname="Selander" fullname="Göran Selander">
         <organization>Ericsson AB</organization>
      </author>
      <author initials="J. P." surname="Mattsson" fullname="John Preuß Mattsson">
         <organization>Ericsson AB</organization>
      </author>
      <author initials="F." surname="Palombini" fullname="Francesca Palombini">
         <organization>Ericsson AB</organization>
      </author>
      <author initials="L." surname="Seitz" fullname="Ludwig Seitz">
         <organization>RISE SICS</organization>
      </author>
      <date month="March" day="6" year="2019" />
      <abstract>
	 <t>This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE). OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols.

 Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration. Therefore, this document updates RFC 7252.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-object-security-16" />
   
</reference>
