Secdir last call review of draft-ietf-httpbis-client-cert-field-05 from Loganaden Velvindron via Datatracker on 2023-03-05 (ietf-http-wg@w3.org from January to March 2023)

From: Loganaden Velvindron via Datatracker <noreply@ietf.org>
Date: Sun, 05 Mar 2023 10:51:10 -0800
To: <secdir@ietf.org>
Cc: draft-ietf-httpbis-client-cert-field.all@ietf.org, ietf-http-wg@w3.org, last-call@ietf.org
Message-ID: <167804227023.47095.18172427609385674001@ietfa.amsl.com>

Reviewer: Loganaden Velvindron
Review result: Has Nits

The I-D looks good.

However, I'm slightly confused about the terminology used in section 3.1
3.1.  Header Field Compression

"If the connection between the TTRP and origin is capable of field
   compression (e.g., HPACK [HPACK] or QPACK [QPACK]), and the TTRP
   multiplexes more than one client's requests into that connection, the
   size and variation of Client-Cert and Client-Cert-Chain field values
   can reduce compression efficiency significantly."

Do the authors mean origin server ?

Received on Sunday, 5 March 2023 18:51:22 UTC