[Wpack] Fwd: New Version Notification for draft-yasskin-http-origin-signed-responses-04.txt

Jeffrey Yasskin <jyasskin@chromium.org> Fri, 15 June 2018 00:12 UTC

Return-Path: <jyasskin@google.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29569130FF4 for <wpack@ietfa.amsl.com>; Thu, 14 Jun 2018 17:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.25
X-Spam-Level:
X-Spam-Status: No, score=-9.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 RcQEwz9Klj5Y for <wpack@ietfa.amsl.com>; Thu, 14 Jun 2018 17:12:36 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 53A02130FB1 for <wpack@ietf.org>; Thu, 14 Jun 2018 17:12:36 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id x6-v6so2899066ybl.12 for <wpack@ietf.org>; Thu, 14 Jun 2018 17:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=4e21L0okFCicKyE6s8+Vnh5T2MdyV1iZby0OyJu3T/o=; b=cBPhM62lXsBT3cOEQQHpG/kB7zljCy+sNhMwEzYz3AL/8aRZtAMBGiIaLX5CHW2S4I ilv2sThhMWLRsKNWYJhW/FpzvKepBJXUcrjXBeuEM0QYoKsH/bzJDtx/S3ZLu6IfrkGy Da6jey97C7AWKeXhEP+Rb9M3QzxEKSASkf48U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=4e21L0okFCicKyE6s8+Vnh5T2MdyV1iZby0OyJu3T/o=; b=q42/hJOpDsOUA6ef53YbWtApxfj3HK1K6e7WJVFbsFLYMAHQ72CXgkVFb6lmcWmvRe Xj3MSlWmjvwT3nhhxHXXl4k3+InhlcYqMUZq6cDd8j96MELP7x6rQlgGPLrfhbXlh29O sI4jcR8SNdPbzux72SIO9lNOXWTRpTj87OdwkDwhNb9i4hM0CAAVDH/5ZBOyLTscMOrZ eOINIWbcyedmJscOEkPARQgCEdITn17quB+gnLaBXrNVANqrtY5Z7YmE+mkq36QWjVFK Yaf21W5cNJMIi9iKMnKoZbC299gUiHMt54W6c3ktFdw8cKMyKo0LMCu9hLTXP77Q+J4v UFGw==
X-Gm-Message-State: APt69E08DOuDgD0SXsl9pP1h3HoqjbSip9GmPnNdbO/Jwhpu9JQXuzIz ii3TfceB3sFIY2bNek6+0sQSCuN6ax+NIiMK+CHm/Q==
X-Google-Smtp-Source: ADUXVKK9c+zZNl3Q2gUOrDBa/daPcywMuERPRE0mdPh10PqUBWM4PusFqVusnmx41czVY1u1SM22/lODoysW8qAyeoM=
X-Received: by 2002:a25:51c2:: with SMTP id f185-v6mr2140347ybb.456.1529021555164; Thu, 14 Jun 2018 17:12:35 -0700 (PDT)
MIME-Version: 1.0
References: <152901383792.26589.11168569668089355517.idtracker@ietfa.amsl.com>
In-Reply-To: <152901383792.26589.11168569668089355517.idtracker@ietfa.amsl.com>
From: Jeffrey Yasskin <jyasskin@chromium.org>
Date: Thu, 14 Jun 2018 17:12:22 -0700
Message-ID: <CANh-dXnkX_68_WJGQS7g3ePNHpNbPvWqjCyy_P16WmHT=hCa8g@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>, wpack@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a6daf6056ea3120a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/w_e8lJrqwEkX_Lpma7oame2J7AI>
Subject: [Wpack] Fwd: New Version Notification for draft-yasskin-http-origin-signed-responses-04.txt
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Web Packaging <wpack.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpack>, <mailto:wpack-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wpack/>
List-Post: <mailto:wpack@ietf.org>
List-Help: <mailto:wpack-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpack>, <mailto:wpack-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2018 00:12:39 -0000

This update contains several changes to make it easier to parse a
cross-origin signed exchange and to start loading it while it's only
partially transferred over the network.

We've also allocated a test OID for the CanSignHttpExchanges extension so
that people can start testing the design, and I believe at least 1 CA is
working on being able to issue certificates with that extension.

Please keep submitting issues at https://github.com/WICG/webpackage/issues
when something in the specification doesn't work for your uses.

Thanks,
Jeffrey

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Thu, Jun 14, 2018 at 3:04 PM
Subject: New Version Notification for
draft-yasskin-http-origin-signed-responses-04.txt
To: Jeffrey Yasskin <jyasskin@chromium.org>



A new version of I-D, draft-yasskin-http-origin-signed-responses-04.txt
has been successfully submitted by Jeffrey Yasskin and posted to the
IETF repository.

Name:           draft-yasskin-http-origin-signed-responses
Revision:       04
Title:          Signed HTTP Exchanges
Document date:  2018-06-14
Group:          Individual Submission
Pages:          51
URL:
https://www.ietf.org/internet-drafts/draft-yasskin-http-origin-signed-responses-04.txt
Status:
https://datatracker.ietf.org/doc/draft-yasskin-http-origin-signed-responses/
Htmlized:
https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-04
Htmlized:
https://datatracker.ietf.org/doc/html/draft-yasskin-http-origin-signed-responses
Diff:
https://www.ietf.org/rfcdiff?url2=draft-yasskin-http-origin-signed-responses-04

Abstract:
   This document specifies how a server can send an HTTP request/
   response pair, known as an exchange, with signatures that vouch for
   that exchange's authenticity.  These signatures can be verified
   against an origin's certificate to establish that the exchange is
   authoritative for an origin even if it was transferred over a
   connection that isn't.  The signatures can also be used in other ways
   described in the appendices.

   These signatures contain countermeasures against downgrade and
   protocol-confusion attacks.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat