Skip to main content

IETF Last Call Review of draft-ietf-hpke-hpke-04
review-ietf-hpke-hpke-04-opsdir-lc-reddyk-2026-08-13-00

Request Review of draft-ietf-hpke-hpke
Requested revision No specific revision (document currently at 05)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2026-08-03
Requested 2026-07-13
Requested by Mohamed Boucadair
Authors Richard Barnes , Karthikeyan Bhargavan , Benjamin Lipp , Christopher A. Wood
I-D last updated 2026-10-08 (Latest revision 2026-09-25)
Completed reviews Genart IETF Last Call review of -04 by Paul Kyzivat (diff)
Dnsdir IETF Last Call review of -04 by Florian Obser (diff)
Opsdir IETF Last Call review of -04 by Tirumaleswar Reddy.K (diff)
Comments
Consider assign it to Tiru or Michael P.
Assignment Reviewer Tirumaleswar Reddy.K
State Completed
Request IETF Last Call review on draft-ietf-hpke-hpke by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/HYLcMSuBmI3t_bX_so6lmeDcSus/
Reviewed revision 04 (document currently at 05)
Result Ready
Completed 2026-08-13
review-ietf-hpke-hpke-04-opsdir-lc-reddyk-2026-08-13-00
I have reviewed this document as part of the Operations directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments are written primarily for the benefit of the Operational
Area Directors. Document editors and WG chairs should treat these comments
just like any other Last Call comments.

Document: draft-ietf-hpke-hpke-04
Reviewer: Tirumaleswar Reddy
Review result: Ready

Summary:

This document specifies Hybrid Public Key Encryption (HPKE) on the IETF
Standards Track and obsoletes RFC 9180 (IRTF/CFRG, Informational). It is a
cryptographic building block, not a protocol on the wire. Section 10
explicitly leaves message encoding to the embedding application. HPKE
defines no ports, no configuration, no network-management interface, no
YANG or MIB modules, and no logging or telemetry surface. Network operators
do not deploy or manage HPKE directly; it is consumed by protocols such as
MLS, TLS Encrypted ClientHello, and Oblivious HTTP.

Accordingly the absence of an Operational Considerations section is
appropriate, and I find no operational or manageability issues.

The document is ready from an operations standpoint.

-Tiru