[core] Fw: New Version Notification for draft-hoeglund-core-oscore-key-limits-00.txt

[Rikard Höglund <[e-mail]>]

Hello CoRE,

We have recently submitted a new draft "AEAD Key Usage Limits in OSCORE".

https://tools.ietf.org/html/draft-hoeglund-core-oscore-key-limits-00

This document considers the CFRG draft at [1], and accordingly defines how two peers using OSCORE must take limits of the used AEAD algorithm into account, and what steps to take in order to preserve the security of their communications. This includes details on the limits for key usage, instructions for messages processing and a brief overview of existing mechanisms to rekey OSCORE.

This work follows a discussion started around IETF 109 [2][3] and recently continued with a broader scope [4].

Any feedback, questions or comments are welcome.

Best wishes
Rikard Höglund

[1] https://tools.ietf.org/html/draft-irtf-cfrg-aead-limits-02
[2] https://mailarchive.ietf.org/arch/msg/core/bbzZCt6ZZn4ysR7yLujPNscBF3g/
[3] https://datatracker.ietf.org/meeting/109/materials/slides-109-core-sessb-ietf-109-core-aead-limits-oscore-00
[4] https://mailarchive.ietf.org/arch/msg/core/h5JHgX5wTBkJtrKl_ezswiCdUBI/

________________________________
From: [e-mail] <[e-mail]>
Sent: Friday, February 19, 2021 18:43
To: Marco Tiloca <[e-mail]>; Rikard Höglund <[e-mail]>
Subject: New Version Notification for draft-hoeglund-core-oscore-key-limits-00.txt


A new version of I-D, draft-hoeglund-core-oscore-key-limits-00.txt
has been successfully submitted by Rikard Hoeglund and posted to the
IETF repository.

Name:           draft-hoeglund-core-oscore-key-limits
Revision:       00
Title:          AEAD Key Usage Limits in OSCORE
Document date:  2021-02-19
Group:          Individual Submission
Pages:          9
URL:            https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-hoeglund-core-oscore-key-limits-00.txt&amp;data=04%7C01%7Crikard.hoglund%40ri.se%7Ce6b2a6a03fa3468b3f3108d8d4fe1fc3%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637493535236581866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=idqLof2Nf7U%2BsHyoO%2F0Pt%2FY7iazBHmn2jBTZwSvzDzc%3D&amp;reserved=0
Status:         https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-hoeglund-core-oscore-key-limits%2F&amp;data=04%7C01%7Crikard.hoglund%40ri.se%7Ce6b2a6a03fa3468b3f3108d8d4fe1fc3%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637493535236581866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=dEkYUUM7AN%2FAUpsEQ7SgaRHeMJBQA%2BekjZlZTwteSvE%3D&amp;reserved=0
Htmlized:       https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-hoeglund-core-oscore-key-limits&amp;data=04%7C01%7Crikard.hoglund%40ri.se%7Ce6b2a6a03fa3468b3f3108d8d4fe1fc3%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637493535236581866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=pzoPc0ARBCQmxFqoPUXcm1nXSzSteZMfnLf7Wlg%2Fqkg%3D&amp;reserved=0
Htmlized:       https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-hoeglund-core-oscore-key-limits-00&amp;data=04%7C01%7Crikard.hoglund%40ri.se%7Ce6b2a6a03fa3468b3f3108d8d4fe1fc3%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637493535236581866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Yit87j47zLL99nUJCWEywfgRgBHyCJMBYS%2BNQxLfIpE%3D&amp;reserved=0


Abstract:
   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.  This document
   defines how two peers using OSCORE must take these limits into
   account and what steps they must take to preserve the security of
   their communications.  Therefore, this document updates RFC8613.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat