Are Alt-Svc and Alt-Used headers "hop-by-hop"?
Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 18 June 2019 02:16 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 1520B1202B7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 17 Jun 2019 19:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 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.001, 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=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 pgMZXeDGwOps for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 17 Jun 2019 19:16:05 -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 518AA120234 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 17 Jun 2019 19:16:05 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hd3cW-000452-8i for ietf-http-wg-dist@listhub.w3.org; Tue, 18 Jun 2019 02:13:12 +0000
Resent-Date: Tue, 18 Jun 2019 02:13:12 +0000
Resent-Message-Id: <E1hd3cW-000452-8i@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 <lucaspardue.24.7@gmail.com>) id 1hd3cS-00044H-WF for ietf-http-wg@listhub.w3.org; Tue, 18 Jun 2019 02:13:09 +0000
Received: from mail-vs1-xe32.google.com ([2607:f8b0:4864:20::e32]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <lucaspardue.24.7@gmail.com>) id 1hd3cR-0002uu-HF for ietf-http-wg@w3.org; Tue, 18 Jun 2019 02:13:08 +0000
Received: by mail-vs1-xe32.google.com with SMTP id j26so7558538vsn.10 for <ietf-http-wg@w3.org>; Mon, 17 Jun 2019 19:12:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=psQvLcMwiILRCNF5HPvgTXshzwUFwVk9pFlI67Q3Oqw=; b=sVT3/dFIQQ/UulCKo7YDZOKilpKlrlWo3YK7tE23pP3/GgOKxyv8MuvTDcM6lR8vp2 sgkNfbbMkFoUu8W2RgxNdmU6fKojMLk4dRmvdIizgVBIVCm3g1AmLrCwhnpz1HYT6JCq xphR99cOUgd+GDEx/CL4kilCh6ctzS70Q3dQMjf4mNzDSbV1ap4maSMwgHmMF05Vzjpk o33tCerW/PBiadXwvZ2E1aPRHBDiXHEyEzcNg5kZgUvshUTtyXbM/9iPjln9XLxdymUB Fgbvooo8APPK1XNm9Kz0v/jVYv6HvUb05T7AfmYVqh3dvKbxdoUUw9gCu12+ZNX46x0Q PT/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=psQvLcMwiILRCNF5HPvgTXshzwUFwVk9pFlI67Q3Oqw=; b=ezVZ34fONVGtKmZ59JTekaqXarDtpMOdPVo8wvUyhFmDYaWCeIzyQn1O4TFhTSJWCH 5q2D2GXoRUnLMXVgPfGY8OeSeiXfT8MMij3hpa/x/c8IDEZEsgdV8r2T2MZd/2GHK57v Qq2pyZOkreUCEszWGrjWmQak2KhRwi3KvunicyIaA3gwkyhYWMPSklS2jvAyc9vfh2I2 GUMYPWj6LXUpcYLisLuh/vEW43IoJuMx+ffL0UHOk3OAMGexlkyrn++9yJhWrZVtPRCW 4IjxFuhmSVvZAdJvuc2ApdxlAzWTqWt5MpJtEBA4lToo6mTeqawRJns8CSNBCIARbooe JViw==
X-Gm-Message-State: APjAAAVNFgfpTBufxJPi/IAF2P+Lcc6T5L8KMSncuhYpM4RNHFmP7NMk sSQF9jDH/IafJLLtmmNZajYEwqIitHMmz2OXGLpuqQ==
X-Google-Smtp-Source: APXvYqw4kNZyga4uQMRv1xzVuKSRQqQBHtdqJZbT/KMfT9oX2Vy4kO1DyPNyOssQC8Qs28xGVOvhmf/YezXP1MSRgxs=
X-Received: by 2002:a67:d58a:: with SMTP id m10mr43627539vsj.15.1560823966552; Mon, 17 Jun 2019 19:12:46 -0700 (PDT)
MIME-Version: 1.0
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 18 Jun 2019 03:12:36 +0100
Message-ID: <CALGR9oZdVvYB=BU-2RLqpUw824rc2QNeYtdqLT3TEZYOcU1w9A@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000155f6d058b8fa6ba"
Received-SPF: pass client-ip=2607:f8b0:4864:20::e32; envelope-from=lucaspardue.24.7@gmail.com; helo=mail-vs1-xe32.google.com
X-W3C-Hub-Spam-Status: No, score=-2.3
X-W3C-Hub-Spam-Report: AWL=1.596, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hd3cR-0002uu-HF cff81bb038f85919937aebd95b1f2f75
X-Original-To: ietf-http-wg@w3.org
Subject: Are Alt-Svc and Alt-Used headers "hop-by-hop"?
Archived-At: <https://www.w3.org/mid/CALGR9oZdVvYB=BU-2RLqpUw824rc2QNeYtdqLT3TEZYOcU1w9A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36725
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>
Hello WG, RFC 7838 defines the Alt-Svc and Alt-Used header fields, and the ALTSVC frame. Section 4 states: ALTSVC frame is processed hop-by-hop. An intermediary MUST NOT forward ALTSVC frames, though it can use the information contained in ALTSVC frames in forming new ALTSVC frames to send to its own clients. So I begin to wonder if an intermediary should process the headers in a similar way. That seems, to me, to be the most correct to avoiding leaking characteristics of the connections on either side of the intermediary. However, since the specification doesn't state this, I'm inclined to think that the intention might be to treat these as end-to-end headers. Any thoughts on this? Kinds regards Lucas
- Are Alt-Svc and Alt-Used headers "hop-by-hop"? Lucas Pardue