<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.amsuess-core-repeat-request-tag" target="https://datatracker.ietf.org/doc/html/draft-amsuess-core-repeat-request-tag-00">
   <front>
      <title>Repeat And Request-Tag</title>
      <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
         <organization>Energy Harvesting Solutions</organization>
      </author>
      <author initials="J. P." surname="Mattsson" fullname="John Preuß Mattsson">
         <organization>Ericsson AB</organization>
      </author>
      <author initials="G." surname="Selander" fullname="Göran Selander">
         <organization>Ericsson AB</organization>
      </author>
      <date month="July" day="1" year="2017" />
      <abstract>
	 <t>   This document defines two optional extensions to the Constrained
   Application Protocol (CoAP): the Repeat option and the Request-Tag
   option.  Each of these options when integrity protected, such as with
   DTLS or OSCOAP, protects against certain attacks on CoAP message
   exchanges.

   The Repeat option enables a CoAP server to verify the freshness of a
   request by requiring the CoAP client to make another request and
   include a server-provided challenge.  The Request-Tag option allows
   the CoAP server to match message fragments belonging to the same
   request message, fragmented using the CoAP Block-Wise Transfer
   mechanism.  This document also specifies additional processing
   requirements on Block1 and Block2 options.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-amsuess-core-repeat-request-tag-00" />
   
</reference>
