Weekly github digest (HTTP Working Group Specifications)

Github Notifications <do_not_reply@mnot.net> Sun, 28 July 2019 00:48 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B211120047 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 27 Jul 2019 17:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.751
X-Spam-Level:
X-Spam-Status: No, score=-2.751 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=E9QVKVmr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iDtU7Yrl
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 yJhh38y4aE7W for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 27 Jul 2019 17:48:43 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B652E1200C1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 27 Jul 2019 17:48:43 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hrXK1-0004EE-D9 for ietf-http-wg-dist@listhub.w3.org; Sun, 28 Jul 2019 00:45:57 +0000
Resent-Date: Sun, 28 Jul 2019 00:45:57 +0000
Resent-Message-Id: <E1hrXK1-0004EE-D9@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <do_not_reply@mnot.net>) id 1hrXJz-0004DT-AE for ietf-http-wg@listhub.w3.org; Sun, 28 Jul 2019 00:45:55 +0000
Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <do_not_reply@mnot.net>) id 1hrXJw-0006NA-MV for ietf-http-wg@w3.org; Sun, 28 Jul 2019 00:45:55 +0000
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DEEE221951 for <ietf-http-wg@w3.org>; Sat, 27 Jul 2019 20:45:30 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 27 Jul 2019 20:45:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm3; bh=PKtogINsnUrRlCYw/XuK/b5hCfPIAQC+ejQ2VVv5Q5Q=; b=E9QVKVmr 3nycgCr8bc1nCCLzLUvUVzeZsxFimf+ozjQvmtKF0RJtUiYMlEkoNqP7YiRNi1NL ZtLR4az6x9cz9xHY8lQn/G6E2NbsjyU4SNPwvpNPqaU0hMxC9iIKCwG+K4M11XGU f0LGt1YHq4qz2I11nvhyXfmwBDSKLWm+hzIXpFfZ+amJ+XBuDud9Yq0TrD7bn6DL NWiyVJJfnjObvyi7opya/bq0PSyz8UlZY5PQjCA7Uvow0101AElZrV5rALK7u9Rc X/nf5wrZbVV2JtDPTVtPJq2Bf8wKM/Io/MppfWLnMJoe5tKuIl9blMBLXa7+s1hP z9pPwnM7vSpXDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=PKtogINsnUrRlCYw/XuK/b5hCfPIA QC+ejQ2VVv5Q5Q=; b=iDtU7YrlpPE1/sqx+8hRr4fy0e/oNyKEhEYmxOhiB1u5H jV7nYFzTBow07GT1ZxsImlUUswKg4PQ9VINth3FO/iEuseIr3t0qnnnhOtiRKMzf woV6heAWiN8sas/EG7ZdRf3z6IL2znSnsrUq+29jNUjj7MoDvVqzScrvJcgt6g9F YJB0so4gWiC8Y3dSfC+PvN6SlEguejnk9/YDq+YEZ+6qcVJ80xpEB93AbqaiqWAy dEYqunsMpSVAPorPV567RsYKxXR9w8mGO2xiwvVuJIDMPMafA3HnGaYBXHxaoSSE 1LZPOhL+4SLAf3krVsIdEOVy7/bO74uwo+Z5NN1tg==
X-ME-Sender: <xms:KvA8Xan1v01J7LoEXpwSvY9Edm3IEvIi94S9_9CD1EPq20Rh1gREcw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrkeejgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtjeenuc fhrhhomhepifhithhhuhgspgfpohhtihhfihgtrghtihhonhhsuceoughopghnohhtpghr vghplhihsehmnhhothdrnhgvtheqnecuffhomhgrihhnpehgihhthhhusgdrtghomhenuc fkphepudduledrledrgeefrddvgedunecurfgrrhgrmhepmhgrihhlfhhrohhmpeguohgp nhhothgprhgvphhlhiesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgepud
X-ME-Proxy: <xmx:KvA8XfNGW_PXDzeYRLtnVPtVqOaIA8OnlzJAIXylVM34UzX8d2INAg> <xmx:KvA8Xf_-oZrq8jKgjMuwKo9BFrNa9V1uxJBYkqJmPN7Izln-Dar8wQ> <xmx:KvA8XZEV5ypfvBZNxCcoYJj9ekPKjIaJf8tKFHcU1s-SLbHHIosruw> <xmx:KvA8Xd9PFxwbqfH3wXSub8tnnD-gebmZ8m5-7LOv4mAKXzr66UYGxA>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id C468B80059 for <ietf-http-wg@w3.org>; Sat, 27 Jul 2019 20:45:29 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id E1E22C0F8D for <ietf-http-wg@w3.org>; Sun, 28 Jul 2019 00:45:26 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============6430026692493964033=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: ietf-http-wg@w3.org
Message-Id: <20190728004526.E1E22C0F8D@cloud.mnot.net>
Date: Sun, 28 Jul 2019 00:45:26 +0000 (UTC)
Received-SPF: pass client-ip=66.111.4.27; envelope-from=do_not_reply@mnot.net; helo=out3-smtp.messagingengine.com
X-W3C-Hub-Spam-Status: No, score=-3.6
X-W3C-Hub-Spam-Report: AWL=1.167, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hrXJw-0006NA-MV ff90d796b338f8b9107189d40bafacf8
X-Original-To: ietf-http-wg@w3.org
Subject: Weekly github digest (HTTP Working Group Specifications)
Archived-At: <https://www.w3.org/mid/20190728004526.E1E22C0F8D@cloud.mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36851
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>



Events without label "editorial"

Issues
------
* httpwg/http-extensions (+6/-6/💬33)
  6 issues created:
  - Request `Digest` validation (by ioggstream)
    https://github.com/httpwg/http-extensions/issues/874 
  - Use cases for Digest (by ioggstream)
    https://github.com/httpwg/http-extensions/issues/872 [digest-headers] 
  - Enable Client Hints on first navigation request through HTTPSSVC (by yoavweiss)
    https://github.com/httpwg/http-extensions/issues/871 
  - Disentangle the DNS Check argument (by MikeBishop)
    https://github.com/httpwg/http-extensions/issues/869 [secondary-certs] 
  - Relationship to SRI (by martinthomson)
    https://github.com/httpwg/http-extensions/issues/868 
  - Should the obsolescence of MD5 be stronger? (by tfpauly)
    https://github.com/httpwg/http-extensions/issues/867 

  14 issues received 33 new comments:
  - #867 Should the obsolescence of MD5 be stronger? (10 by ioggstream, LPardue, tfpauly)
    https://github.com/httpwg/http-extensions/issues/867 [digest-headers] 
  - #848 Serializing sh-float is hard (5 by reschke, phluid61, martinthomson, bsdphk)
    https://github.com/httpwg/http-extensions/issues/848 [header-structure] 
  - #716 Consider a `Sec-CH-` prefix for client hint headers (3 by reschke, yoavweiss)
    https://github.com/httpwg/http-extensions/issues/716 [client-hints] 
  - #868 Relationship to SRI (2 by ioggstream, LPardue)
    https://github.com/httpwg/http-extensions/issues/868 [digest-headers] 
  - #874 Request `Digest` validation (2 by ioggstream, LPardue)
    https://github.com/httpwg/http-extensions/issues/874 [digest-headers] 
  - #782 define a URI reference type (2 by kazuho, tfpauly)
    https://github.com/httpwg/http-extensions/issues/782 [header-structure] 
  - #821 Considering http_response_status (2 by martinthomson, alyssawilk)
    https://github.com/httpwg/http-extensions/issues/821 [proxy-status] 
  - #700 Clarify behavior for multiple values for CH headers (1 by yoavweiss)
    https://github.com/httpwg/http-extensions/issues/700 [client-hints] 
  - #786 Active vs. passive fingerprinting (1 by yoavweiss)
    https://github.com/httpwg/http-extensions/issues/786 [client-hints] 
  - #852 Create a threat model for `Digest` header. (1 by ioggstream)
    https://github.com/httpwg/http-extensions/issues/852 [digest-headers] 
  - #855 Shall we use sh-binary serialization for `id-sha` digest-algoritms? (1 by ioggstream)
    https://github.com/httpwg/http-extensions/issues/855 [digest-headers] 
  - #828 Digest Headers: what about the other algorithms? (1 by ioggstream)
    https://github.com/httpwg/http-extensions/issues/828 [digest-headers] 
  - #778 Cache header name (1 by tfpauly)
    https://github.com/httpwg/http-extensions/issues/778 [cache-header] 
  - #767 Client-Hints exposes fingerprint values to additional parties and logging sensitive locations (1 by igrigorik)
    https://github.com/httpwg/http-extensions/issues/767 [client-hints] 

  6 issues closed:
  - Request `Digest` validation https://github.com/httpwg/http-extensions/issues/874 [digest-headers] 
  - Should the obsolescence of MD5 be stronger? https://github.com/httpwg/http-extensions/issues/867 [digest-headers] 
  - Client Hints doesn't distinguish clearly between request and response header fields https://github.com/httpwg/http-extensions/issues/761 [client-hints] 
  - Key -> Variants https://github.com/httpwg/http-extensions/issues/730 [client-hints] 
  - Clarify behavior for multiple values for CH headers https://github.com/httpwg/http-extensions/issues/700 [client-hints] 
  - Shall we use sh-binary serialization for `id-sha` digest-algoritms? https://github.com/httpwg/http-extensions/issues/855 [digest-headers] 

* httpwg/http-core (+0/-1/💬17)
  10 issues received 17 new comments:
  - #218 Disambiguate 403 Forbidden (4 by asbjornu, reschke, mnot)
    https://github.com/httpwg/http-core/issues/218 [discuss] [semantics] 
  - #128 Quoted cache-control directives (2 by reschke, MattMenke2)
    https://github.com/httpwg/http-core/issues/128 [caching] [discuss] 
  - #212 byte-range-set definition allows OWS but probably doesn't work in practice (2 by royfielding, mnot)
    https://github.com/httpwg/http-core/issues/212 [discuss] [semantics] 
  - #48 415 and Accept (2 by jsha, reschke)
    https://github.com/httpwg/http-core/issues/48 [semantics] 
  - #215 field-value value space (2 by reschke, mnot)
    https://github.com/httpwg/http-core/issues/215 [discuss] [semantics] 
  - #32 Duplicate header resolution in H1 (1 by reschke)
    https://github.com/httpwg/http-core/issues/32 [semantics] 
  - #34 Use URL Standard for Location header (1 by mnot)
    https://github.com/httpwg/http-core/issues/34 [discuss] [semantics] 
  - #169 URI length (1 by mnot)
    https://github.com/httpwg/http-core/issues/169 [discuss] [semantics] 
  - #194 QUIC and https:// (1 by mnot)
    https://github.com/httpwg/http-core/issues/194 [discuss] [semantics] 
  - #180 Clarify multiple `authorization` header behaviour or concatenation method (1 by mnot)
    https://github.com/httpwg/http-core/issues/180 [discuss] [semantics] 

  1 issues closed:
  - Method registry should include cacheability https://github.com/httpwg/http-core/issues/54 [erratum] [has-proposal] [semantics] 



Pull requests
-------------
* httpwg/http-extensions (+6/-5/💬8)
  6 pull requests submitted:
  - Detail dimensions of information exposure (by yoavweiss)
    https://github.com/httpwg/http-extensions/pull/879 
  - Remove Accept-CH-Lifetime (by igrigorik)
    https://github.com/httpwg/http-extensions/pull/878 [client-hints] 
  - Obsolete ADLER-32 but don't forbid it. #828 (by ioggstream)
    https://github.com/httpwg/http-extensions/pull/877 
  - Fix: #832. Reference RFC6234 instead of FIPS180. (by ioggstream)
    https://github.com/httpwg/http-extensions/pull/876 
  - md5 must not be used (by ioggstream)
    https://github.com/httpwg/http-extensions/pull/875 
  - Add use cases section. (by ioggstream)
    https://github.com/httpwg/http-extensions/pull/873 

  3 pull requests received 8 new comments:
  - #866 Add an Alt-Svc extension (5 by martinthomson, yoavweiss, davidben)
    https://github.com/httpwg/http-extensions/pull/866 [client-hints] 
  - #776 Add Sec- prefix to security considerations (2 by yoavweiss)
    https://github.com/httpwg/http-extensions/pull/776 [client-hints] 
  - #879 Detail dimensions of information exposure (1 by yoavweiss)
    https://github.com/httpwg/http-extensions/pull/879 

  5 pull requests merged:
  - md5 must not be used
    https://github.com/httpwg/http-extensions/pull/875 
  - Clarify defined headers are response headers
    https://github.com/httpwg/http-extensions/pull/860 [client-hints] 
  - Replace Key with Variants
    https://github.com/httpwg/http-extensions/pull/861 [client-hints] 
  - [Client Hints] Replace ABNF with Structured Headers
    https://github.com/httpwg/http-extensions/pull/862 [client-hints] 
  - Remove workaround for addstyle.sed bug.
    https://github.com/httpwg/http-extensions/pull/813 

* httpwg/http-core (+1/-2/💬1)
  1 pull requests submitted:
  - Disambiguate 403 Forbidden (#218) (by reschke)
    https://github.com/httpwg/http-core/pull/234 

  1 pull requests received 1 new comments:
  - #217 Refactor the range specifier grammar (1 by reschke)
    https://github.com/httpwg/http-core/pull/217 [discuss] [semantics] 

  2 pull requests merged:
  - Move the trailing CRLF from the line grammars into the message format (#62)
    https://github.com/httpwg/http-core/pull/232 
  - Get rid of "cacheable methods"
    https://github.com/httpwg/http-core/pull/229 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/httpwg/http-extensions
* https://github.com/httpwg/http-core