Re: [secdir] Secdir last call review of draft-ietf-httpbis-early-hints-03

Kazuho Oku <kazuhooku@gmail.com> Fri, 07 July 2017 04:40 UTC

Return-Path: <kazuhooku@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7098F12EC1C; Thu, 6 Jul 2017 21:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PxALMlTBQ74Y; Thu, 6 Jul 2017 21:40:07 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 901AF124D85; Thu, 6 Jul 2017 21:40:07 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id t186so11204891pgb.1; Thu, 06 Jul 2017 21:40:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h3TGgKimQqBFyGHcd9y1oiGbpFwHsWNBlN9QXv6g2Uc=; b=JrANn2ACo6aoni6iXhcQDwOOpBOepnPDHCn2c6WOAvzaOLaWOFvEg4JFkDX37VN0k1 yPIfwbUw/OciwVimUfAhFZq1Jih9embei5F933MytcW0oP06wY/SDebvueYyD6EAgrfI IOHLQBz27hZqX6o7Kgm+r6+oyxq31YHsLs263Yw+keoGznKYvGpWYA/8j4LQD6jSolWy V41hJiC35fYbPuu/F+AL3f7KFozi8QUkbUN9VUFTXtJaif+/vbNG/4lZBpKWRY/33ryp wIVJxGkW+vWXAWnl8pnHrTiiPehRoseapAyqJXRiYbl7Mpq3150jiCT44sIwPJ4gKwrW yeBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h3TGgKimQqBFyGHcd9y1oiGbpFwHsWNBlN9QXv6g2Uc=; b=ch4cUp6zj4RogF2w53M82kUUXLXAO2lp3uNPHnM6vfhRnXBkrk+KqQwd8kxW/oEsLD Y4w0Szand6/iw0W6/HUpL1IO97jtdwB2kYE6y6+7PHtGvMfBV2eGF6PEib6/SpDMh+Je dt3lKTh0oVeNYgQy/mCis+ZVtl/UzdjCs2V3r2/1qTQ5TLbBAtvBgYCZYYcDkInJv8Qq Fa2T3WgD0tcCy3LbMGCzs7ZBdic5PGWmkoQ9rfXMx4TqXJySlAzM0wpoj58YcUNGvNHH /gG/wGcmkgLpzJ+2UxIL7xyoxSmCBGSPRRHAhRA7Vg6oanI5L78jOpa6BXunrBoeK9me hOLQ==
X-Gm-Message-State: AIVw111+OX2oyJQA2ba7Iw+Sqo9ITwShMjGUxaYslNB29aPYfX7SbSsd FCHKNS2Ms5R6Z/9GgSD6J9IRlK6z7Q==
X-Received: by 10.99.104.74 with SMTP id d71mr30456784pgc.7.1499402407145; Thu, 06 Jul 2017 21:40:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.130.3 with HTTP; Thu, 6 Jul 2017 21:40:06 -0700 (PDT)
In-Reply-To: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 7 Jul 2017 13:40:06 +0900
Message-ID: <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/A2iTN3CMdONYuUdHTD256jOEe3Q>
Subject: Re: [secdir] Secdir last call review of draft-ietf-httpbis-early-hints-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 04:40:09 -0000

Hi Melinda,

Thank you very much for the review. My responses below.

2017-07-05 4:37 GMT+09:00 Melinda Shore <melinda.shore@gmail.com>om>:
> Reviewer: Melinda Shore
> Review result: Has Issues
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> Summary:   Has minor issues.
>
> This draft defines a status code for sending an informational
> response that contains header fields that are likely to be included in the
> final response.  A server can send the informational response containing
> some of the header fields to help the client start making preparations
> for processing the final response, and then run time-consuming operations
> to generate the final response.  The informational response can also be used by an
> origin server to trigger HTTP/2 server push at a caching intermediary.
>
> Passed nit checker without complaints other than publication date.  Sections
> 5 and 6 should be appendices.

The issue has been fixed in the github repo.

>
> One minor issue: in the security considerations section, "Therefore,
> a server might refrain from sending Early Hints over HTTP/1.1 unless when
> the client is known to handle informational responses correctly" is a bit squishy
> (and contains a superfluous "when").  I'm not sure this merits a text change and
> I'm rather certain that it doesn't merit normative 2119 language but it did stand
> out as an overly soft recommendation.

The superfluous "when" has been removed from the github repo.

Regarding the wording, I think it would be better to keep the tone
as-is, rather than suggesting implementers not to send an Early Hints
response over HTTP/1.1 depending on the client.

Users behind a proxy that cannot handle informational response
correctly is exposed to response splitting attack regardless of if
Early Hints is used (in HTTP/1.1, a server is allowed to send any
informational response at it's own discretion).

So while it is beneficial to warn the risks, I think that there is no
merit in restricting the use of Early Hints.

-- 
Kazuho Oku