[saag] Pre-Draft Comments on SP 800-38F (Methods for Key Wra pping)
John Mattsson <[email protected]> Tue, 2 Jun 2026 14:53:04 +0000
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <AS4PR07MB88252B1136A93399A7E3218F89122@AS4PR07MB8825.eurprd07.prod.outlook.com> |
--===============3176453269394027146== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_AS4PR07MB88252B1136A93399A7E3218F89122AS4PR07MB8825eurp_" --_000_AS4PR07MB88252B1136A93399A7E3218F89122AS4PR07MB8825eurp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, NIST recently asked for pre-draft comments on SP 800-38F (Methods for Key W= rapping) as well as more general questions on the 800-38 series. The public= comment period is open through July 10, 2026. https://csrc.nist.gov/pubs/sp/800/38/f/r1/iprd Ericsson provided the following comments https://emanjon.github.io/NIST-comments/2026%20SP%20800-38F.pdf SP 800-38F specifies AES-KW and AES-KWP, which are also defined in RFC 3394= and RFC 5649, making this relevant to the IETF. In addition, the question = of which compositions of encryption and integrity mechanisms are used, need= ed, and should be approved is also highly relevant to IETF protocols. https://www.rfc-editor.org/rfc/rfc3394.html https://www.rfc-editor.org/rfc/rfc5649.html Cheers John Preu=DF Mattsson --_000_AS4PR07MB88252B1136A93399A7E3218F89122AS4PR07MB8825eurp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> </head> <body> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt;"> <span style=3D"color: rgba(0, 0, 0, 0.87); text-transform: none;">Hi,</span= ><span style=3D"color: rgb(0, 0, 0);"><br> <br> </span><span style=3D"color: rgba(0, 0, 0, 0.87); text-transform: none;">NI= ST recently asked for pre-draft comments on SP 800-38F (Methods for Key Wra= pping) as well as more general questions on the 800-38 series. The pub= lic comment period is open through July 10, 2026.</span><span style=3D"color: rgb(0, 0, 0);"><br> </span><span style=3D"color: rgb(26, 115, 232); text-transform: none;"><a h= ref=3D"https://csrc.nist.gov/pubs/sp/800/38/f/r1/iprd" target=3D"_blank" re= l=3D"nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&a= mp;q=3Dhttps://csrc.nist.gov/pubs/sp/800/38/f/r1/iprd&source=3Dgmail&am= p;ust=3D1780497578776000&usg=3DAOvVaw0YB0LUOSqGhXfrxKSikVIO" data-outlo= ok-id=3D"67ed9178-19a0-4de0-8dc2-1998d6708a67" style=3D"color: rgb(26, 115,= 232); text-decoration: none; text-align: left;">https://csrc.nist.gov/pubs= /sp/800/38/f/r1/iprd</a></span></div> <div style=3D"text-align: left; text-indent: 0px; text-transform: none; fon= t-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt;"> <span style=3D"color: rgba(0, 0, 0, 0.87);"><br> Ericsson provided the following comments<br> </span><span style=3D"color: rgb(26, 115, 232);"><a href=3D"https://emanjon= .github.io/NIST-comments/2026%20SP%20800-38F.pdf" target=3D"_blank" rel=3D"= nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q= =3Dhttps://emanjon.github.io/NIST-comments/2026%2520SP%2520800-38F.pdf&= source=3Dgmail&ust=3D1780497578776000&usg=3DAOvVaw3Vu1ogzVvuah-Y43K= s31V_" data-outlook-id=3D"3c5cef74-1572-45cb-98c2-52c569ec32ac" style=3D"co= lor: rgb(26, 115, 232); text-decoration: none;">https://emanjon.github.io/N= IST-comments/2026%20SP%20800-38F.pdf</a></span></div> <div style=3D"direction: ltr; text-align: left; text-indent: 0px; text-tran= sform: none; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 1= 2pt; color: rgba(0, 0, 0, 0.87);"> <br> </div> <div style=3D"direction: ltr; text-align: left; text-indent: 0px; text-tran= sform: none; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 1= 2pt; color: rgba(0, 0, 0, 0.87);"> SP 800-38F specifies AES-KW and AES-KWP, which are also defined in RFC 3394= and RFC 5649, making this relevant to the IETF. In addition, the question = of which compositions of encryption and integrity mechanisms are used, need= ed, and should be approved is also highly relevant to IETF protocols.</div> <div style=3D"direction: ltr; text-align: left; text-indent: 0px; text-tran= sform: none; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 1= 2pt; color: rgb(0, 0, 0);"> <a href=3D"https://www.rfc-editor.org/rfc/rfc3394.html" data-outlook-id=3D"= a61819cc-4494-45c8-aba1-2ff8a6dd9b75">https://www.rfc-editor.org/rfc/rfc339= 4.html</a></div> <div style=3D"direction: ltr; text-align: left; text-indent: 0px; text-tran= sform: none; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 1= 2pt; color: rgb(0, 0, 0);"> <a href=3D"https://www.rfc-editor.org/rfc/rfc5649.html" data-outlook-id=3D"= 83d5d4a0-0048-4521-8676-38bf3982d07c">https://www.rfc-editor.org/rfc/rfc564= 9.html</a></div> <div style=3D"direction: ltr; text-align: left; text-indent: 0px; text-tran= sform: none; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 1= 2pt; color: rgba(0, 0, 0, 0.87);"> <br> </div> <div style=3D"text-align: left; text-indent: 0px; text-transform: none; fon= t-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgba= (0, 0, 0, 0.87);"> Cheers<br> John Preu=DF Mattsson</div> </body> </html> --_000_AS4PR07MB88252B1136A93399A7E3218F89122AS4PR07MB8825eurp_-- --===============3176453269394027146== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc2FhZyBtYWls aW5nIGxpc3QgLS0gc2FhZ0BpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IHNhYWctbGVhdmVAaWV0Zi5vcmcK --===============3176453269394027146==--