Re: [Masque] HTTP Proxy-Status Parameter for DNS Information

Mark Nottingham <mnot@mnot.net> Wed, 12 October 2022 23:02 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 888CAC14CF09 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 12 Oct 2022 16:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.759
X-Spam-Level:
X-Spam-Status: No, score=-2.759 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, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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=jMAnmrze; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PysQevgw
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRxRhGa4OLUY for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 12 Oct 2022 16:02:36 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE3E8C14CF11 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 12 Oct 2022 16:02:36 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1oikk1-002ZYc-ET for ietf-http-wg-dist@listhub.w3.org; Wed, 12 Oct 2022 23:02:21 +0000
Resent-Date: Wed, 12 Oct 2022 23:02:21 +0000
Resent-Message-Id: <E1oikk1-002ZYc-ET@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mnot@mnot.net>) id 1oikjz-002ZXO-Oa for ietf-http-wg@listhub.w3.org; Wed, 12 Oct 2022 23:02:19 +0000
Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mnot@mnot.net>) id 1oikjy-00BuMM-4o for ietf-http-wg@w3.org; Wed, 12 Oct 2022 23:02:19 +0000
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 7CE705C004A; Wed, 12 Oct 2022 19:02:07 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 12 Oct 2022 19:02:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1665615727; x= 1665702127; bh=vURAuEbN/OVxEKsAIXVhUnaI8zdBxjUsA2xfBoDtsB4=; b=j MAnmrzeOyGr+US0lOESByyV1EVnBCpHbgs1pQqjToEm1tqjiWOtwHfEydy2hzYCt CaBt9vcIQiYzOJeaVOebArhjcb2Esh/QqE033HrOd4nwM7A11dhhB+/Wytz+55Vg ywJjLD9qDYHDcsbSBUgdj60Jev6+oeWJ6OBG4HhmaipWcNTscF1pBeM6eKpnX2yM f9mONhrsHbo7QxMJD4ggpHFNVfCCHvYTVdET5TJYTRHARvytYNaJL+HfcDTurRAT boo1oRmyXJk5xYkGx7SNXcGA7AiIJ3Ke+fRjXrDRFFFtJ9ZAZWX2RyKI4kNtvbkf grN8+qRw0hszJHLYz33jw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1665615727; x= 1665702127; bh=vURAuEbN/OVxEKsAIXVhUnaI8zdBxjUsA2xfBoDtsB4=; b=P ysQevgwSNxDDR2JAYZrGB8Wt+NV3sR+InidEf1uq85nN1XV55oBBz+bDLUiVOTs0 /WML9RdgmQJn7Tk5iwlIjbKKHjn3QeF69bd/xfXonQlzmVvZdubqJJaD24DbRG3U czv34D5lpH7SBDnDUlQGQCq6pmeyM4ukwNjs8FF3vticZ0x9kWlayk8OewNilJQp akp1+kwQV7iyaNgs5v1ngBaOY2Jl56RA9NZok29X6H6e4eYTx6om9TTyfQSPfHY7 Z9QgduOSD8AWclfLUYmMo1rUNTWw/AOQZYbvTAnbvPos6/QhNVemCkloTV32DpB0 9z/R7C3x0lKjXlChISNhw==
X-ME-Sender: <xms:b0dHY94BS9kb3Kv-wKWNbr0L2-qoI6D7gFx67PY1sCaS253PInGYqQ> <xme:b0dHY65bO22bj6oBErVeMdQI82TD49T7oZOotGQMvNBni9-c64es4mxiJraccDR1h UmiymwTeQkwchVyuQ>
X-ME-Received: <xmr:b0dHY0e1bDaTRMbaxlGJD4tdX83B238LKpNfgj9MZjzTdopP3BuUYA9t4DI7U-jfHKT10Rr0BS2lMf_DohkEuWHSy4qZYSBuz3DoIZCabNcLSjB81hBf9Jc5>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeejledgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepveffveelheeuueeugfffveetjeejtdejffduvdevtefhffetffettdehtdff vedunecuffhomhgrihhnpegrphhplhgvrdgtohhmpdhhthhtphdrsggvshhtpdhivghtfh drohhrghdpghhithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:b0dHY2JlfstbKDczsuoP-8XKc4zCvAjJmyIeiPnpR3v1rRFTnPnnjw> <xmx:b0dHYxL7guLFIMYX8RkVcfGBytjK6X3SW1ORRNB0q0eFpxKszyiQIA> <xmx:b0dHY_yu1bCOaMl7xvFlKd3tFb0fgjRdTwS5yYC2nA0YKRVNRXcqTA> <xmx:b0dHYzyUKv09kVH8sQ6RiOwV4WRjJXwxWgsddW1z_DW3dekL4JLegg>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 Oct 2022 19:02:05 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <B18ACDAA-3B4C-48C7-B759-749EDF3FAA4E@apple.com>
Date: Thu, 13 Oct 2022 10:02:03 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C91FC9A7-661D-4E8B-BE09-AD96EE7E3C4C@mnot.net>
References: <4D32628F-B514-4B9E-9F50-9FDA652A59B6@apple.com> <B18ACDAA-3B4C-48C7-B759-749EDF3FAA4E@apple.com>
To: Tommy Pauly <tpauly@apple.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Received-SPF: pass client-ip=66.111.4.28; envelope-from=mnot@mnot.net; helo=out4-smtp.messagingengine.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=mnot.net), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=messagingengine.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oikjy-00BuMM-4o cf3e795947a5ead592cb2c1fc5398960
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [Masque] HTTP Proxy-Status Parameter for DNS Information
Archived-At: <https://www.w3.org/mid/C91FC9A7-661D-4E8B-BE09-AD96EE7E3C4C@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40434
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>

Speaking personally -- I don't have any strong feelings either way, as long as appropriate communication happens. If the use cases are for non-MASQUE proxying too (and it seems like they are), that might tilt it slightly towards HTTP.

Cheers,


> On 11 Oct 2022, at 2:46 am, Tommy Pauly <tpauly@apple.com> wrote:
> 
> Hi HTTP,
> 
> I wanted to share this draft with this group, which I’ve initially started discussion on in MASQUE.
> 
> It’s a simple parameter addition to proxy-status, to let the proxy send back the IP and CNAME/alias chain it used to reach the next hop. This is useful for clients of CONNECT/CONNECT-UDP proxies that want to apply policies to specific IPs and CNAMEs (for tracker detection, cookie rules, etc).
> 
> In addition to any reviews and feedback on the technical content, we’d like to know if this is something that the HTTPbis WG would like to own, or if it is fine letting the work happen in MASQUE and get review from HTTP.
> 
> Best,
> Tommy
> 
>> Begin forwarded message:
>> 
>> From: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
>> Subject: [Masque] HTTP Proxy-Status Parameter for DNS Information
>> Date: October 4, 2022 at 12:29:33 PM PDT
>> To: masque@ietf.org
>> 
>> Hello MASQUErs,
>> 
>> I wanted to share this document with this group, since it is mainly applicable to MASQUE-style (CONNECT/CONNECT-UDP) proxies.
>> 
>> Right now, when a client connects to a TCP or UDP server via the proxy using a hostname in the request, it doesn’t perform its own DNS, and thus doesn’t learn about the IP address of the server it ultimately is connected to, or the CNAME / AliasMode chain that was used to get to the IP address of the server. That’s generally fine, but there are use cases where clients may want to know the IP address or CNAMEs to detect cases where trackers are performing CNAME cloaking, etc.
>> 
>> So, this is a very simple proposal to define a new, optional proxy-status parameter that can let MASQUE-style proxies tell clients about the IP address and CNAME chain from DNS.
>> 
>> https://www.ietf.org/archive/id/draft-pauly-masque-dns-proxy-status-00.html
>> 
>> This certainly does not solve all of the use cases where clients may want to know more DNS details (SVCB/HTTPS records for ECH, alpn support, etc), and I expect more work to be needed for those use cases. However, I believe this extra bit of information is something that is incrementally useful, easy to implement, and simple to define.
>> 
>> Thoughts and feedback welcome!
>> 
>> Thanks,
>> Tommy
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org
>>> Subject: New Version Notification for draft-pauly-masque-dns-proxy-status-00.txt
>>> Date: October 4, 2022 at 11:01:29 AM PDT
>>> To: Tommy Pauly <tpauly@apple.com>
>>> 
>>> 
>>> A new version of I-D, draft-pauly-masque-dns-proxy-status-00.txt
>>> has been successfully submitted by Tommy Pauly and posted to the
>>> IETF repository.
>>> 
>>> Name:		draft-pauly-masque-dns-proxy-status
>>> Revision:	00
>>> Title:		HTTP Proxy-Status Parameter for DNS Information
>>> Document date:	2022-10-04
>>> Group:		Individual Submission
>>> Pages:		5
>>> URL:            https://www.ietf.org/archive/id/draft-pauly-masque-dns-proxy-status-00.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-pauly-masque-dns-proxy-status/
>>> Html:           https://www.ietf.org/archive/id/draft-pauly-masque-dns-proxy-status-00.html
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pauly-masque-dns-proxy-status
>>> 
>>> 
>>> Abstract:
>>>   This document defines an HTTP Proxy-Status Parameter that contains
>>>   the IP address and CNAME chain received over DNS that was used to
>>>   establish the connection to the next hop.
>>> 
>>> Discussion Venues
>>> 
>>>   This note is to be removed before publishing as an RFC.
>>> 
>>>   Source for this draft and an issue tracker can be found at
>>>   https://github.com/tfpauly/privacy-proxy.
>>> 
>>> 
>>> 
>>> 
>>> The IETF Secretariat
>>> 
>>> 
>> 
>> -- 
>> Masque mailing list
>> Masque@ietf.org
>> https://www.ietf.org/mailman/listinfo/masque
> 

--
Mark Nottingham   https://www.mnot.net/