[secdir] Secdir last call review of draft-ietf-httpbis-client-cert-field-05

Loganaden Velvindron via Datatracker <noreply@ietf.org> Sun, 05 March 2023 18:51 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Loganaden Velvindron via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-httpbis-client-cert-field.all@ietf.org, ietf-http-wg@w3.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167804227023.47095.18172427609385674001@ietfa.amsl.com>
Reply-To: Loganaden Velvindron <loganaden@gmail.com>
Date: Sun, 05 Mar 2023 10:51:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/xA3ToXmgyHklh-ipGwhbqArXQ7s>
Subject: [secdir] Secdir last call review of draft-ietf-httpbis-client-cert-field-05

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 ?

[secdir] Secdir last call review of draft-ietf-ht… Loganaden Velvindron via Datatracker
Re: [secdir] Secdir last call review of draft-iet… Brian Campbell