Removed `app_info` field from HPKE key protobufs.

Guidance from latest HPKE draft clarifies that single-shot APIs should not
allow users to set both per-context and per-message auxiliary authenticated
application information.

https://github.com/cfrg/draft-irtf-cfrg-hpke/pull/231

PiperOrigin-RevId: 383494777

1 files changed, 0 insertions, 16 deletions

diff --git a/proto/hpke.proto b/proto/hpke.proto
index 55f6a385a..d33a6e47c 100644
--- a/proto/hpke.proto
+++ b/proto/hpke.proto
@@ -51,14 +51,6 @@ message HpkePublicKey {
   // KEM-encoding of public key (i.e., SerializePublicKey() ) as described in
   // https://www.ietf.org/archive/id/draft-irtf-cfrg-hpke-09.html#name-cryptographic-dependencies.
   bytes public_key = 3;
-  // `app_info` is an optional parameter that binds the derived key material
-  // to application-specific information as described in Section 5.1 of
-  // https://www.ietf.org/archive/id/draft-irtf-cfrg-hpke-09.html.
-  //
-  // NOTE: This API sets a constant 'app_info' parameter for each key, but the
-  // HPKE standard itself does not impose this restriction.  For per-context
-  // 'app_info' parameters, this API is not suitable.
-  bytes app_info = 4;
 }
 
 message HpkePrivateKey {
@@ -71,12 +63,4 @@ message HpkePrivateKey {
 
 message HpkeKeyFormat {
   HpkeParams params = 1;
-  // `app_info` is an optional parameter that binds the derived key material
-  // to application-specific information as described in Section 5.1 of
-  // https://www.ietf.org/archive/id/draft-irtf-cfrg-hpke-09.html.
-  //
-  // NOTE: This API sets a constant 'app_info' parameter for each key, but the
-  // HPKE standard itself does not impose this restriction.  For per-context
-  // 'app_info' parameters, this API is not suitable.
-  bytes app_info = 2;
 }