W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2017

Genart last call review of draft-ietf-httpbis-encryption-encoding-08

From: Pete Resnick <presnick@qti.qualcomm.com>
Date: Wed, 05 Apr 2017 22:52:48 -0700
To: <gen-art@ietf.org>
Cc: draft-ietf-httpbis-encryption-encoding.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Message-ID: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
Reviewer: Pete Resnick
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-httpbis-encryption-encoding-??
Reviewer: Pete Resnick
Review Date: 2017-04-05
IETF LC End Date: 2017-04-06
IESG Telechat date: 2017-04-13

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: Looks fine from a non-security-expert's
perspective. It is my duty to ask about keyid in section 2.1:

      A "keyid" parameter SHOULD be a UTF-8
      [RFC3629] encoded string, particularly where the identifier
might
      need to appear in a textual form.

I presume that simply means "might need to be rendered" and does not
include "might need to be typed in by someone", correct? The former is
easy; the latter probably requires a bit more text.
Received on Thursday, 6 April 2017 05:53:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:03 UTC