<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-oscore-key-limits" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-key-limits-03">
   <front>
      <title>Key Usage Limits for OSCORE</title>
      <author initials="R." surname="Höglund" fullname="Rikard Höglund">
         <organization>RISE AB</organization>
      </author>
      <author initials="M." surname="Tiloca" fullname="Marco Tiloca">
         <organization>RISE AB</organization>
      </author>
      <date month="July" day="8" year="2024" />
      <abstract>
	 <t>   Object Security for Constrained RESTful Environments (OSCORE) uses
   AEAD algorithms to ensure confidentiality and integrity of exchanged
   messages.  Due to known issues allowing forgery attacks against AEAD
   algorithms, limits should be followed on the number of times a
   specific key is used for encryption or decryption.  Among other
   reasons, approaching key usage limits requires updating the OSCORE
   keying material before communications can securely continue.  This
   document defines how two OSCORE peers can follow these key usage
   limits and what steps they should take to preserve the security of
   their communications.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-oscore-key-limits-03" />
   
</reference>
