Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 04 November 2019 17:15 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4FBA120824; Mon, 4 Nov 2019 09:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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, URIBL_BLOCKED=0.001] autolearn=no 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 Z6qPNpLgVBpj; Mon, 4 Nov 2019 09:15:49 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (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 B62BE120AF4; Mon, 4 Nov 2019 09:15:49 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id k11so2536320ual.10; Mon, 04 Nov 2019 09:15:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8hczRM5IfxYUI9AixS7XXZ7Wlm3oCBTuXjDHST8y2zI=; b=ejSLxNSroR7+YaglkntTY1hVMewXxWxlzOWgC9hvwqTGaPDbK51YpcfixDWRaj151D G2OmUCzf82yRUXxNkBjxC7lkEbcHyup2QfYsLTBNGVZsqSLx9JUntON+yX7ZaHYrsWUf f+SBp/9TqHSyzraiW0b4QJvo8Zyy5zq+mCNs0gXkE0eEmhFnam2cJCvD0ZevtESxwG42 NOqwDgDDNfi4hNybHHSUXuCRmUFzIdW6PeSJjvXHqQ8Kvu5H1jLpUN1nDmlEsqAJ5AIT pKs5HF51cIJ9DSOXbq1u9Bxm/LMekzH2fMQ3HYc4CWDfpliTgiYDCDz7SansLsFoIH5d aUew==
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:cc; bh=8hczRM5IfxYUI9AixS7XXZ7Wlm3oCBTuXjDHST8y2zI=; b=jefW4IzisvKDtiFPHFaqSX9SguMcXC9/dHXs5io+KYBWhaOQFBN/lCmQJAw3D11kYm BrCCKTyDhsmD4nHdYCVisxaOcFYb77jHnXnsz3+C8Cs2GdcUkjcVZxAu/WXbPiYdJ69d ED6JNmXlFCn9T+sGLwOplQubT6W+Kz9Q/9ZvywfgIK5c52f9mAMNbawpcjJP+Ixo8Fak yL8bBrIxygoa2El65mfP0fBbI6snLvev4k6Pc1GQ5rRcRIfHVhzSa/LzafqrSXfB3ICf fa/W1lEoUi8wDETnjE2T12Yhfq/rtCBg2eDLCTbSRlcXZNQ4GExj+1nNvykbKOtVmkHa snAg==
X-Gm-Message-State: APjAAAVTSQgmNTy1A+TP2JWCmamvu8FH2S5DV/csJKGgrWlDDgSe+6Hx GC7N/mW9wr0GxPz4nFY6exHfKmJTSkuRIHwNbvM=
X-Google-Smtp-Source: APXvYqwnFCEBM9l87u4JbivnKaqdOFp4HxFi+HnPJwzi5qr7vAGkkdd6k74lKHQy9flEKvfSRVSt4LN18fp4ZMGzeBE=
X-Received: by 2002:a9f:2304:: with SMTP id 4mr12812543uae.69.1572887748569; Mon, 04 Nov 2019 09:15:48 -0800 (PST)
MIME-Version: 1.0
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com> <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com> <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com>
In-Reply-To: <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 4 Nov 2019 17:15:37 +0000
Message-ID: <CALGR9oYHce0mnkj5Kz13EoR-zN3-xSr0igkJF2Z_dJ2vgfVNSQ@mail.gmail.com>
To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
Cc: "quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Type: multipart/alternative; boundary="000000000000866f3d05968877bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/Lj3HPp_b3wSJuH5fUBfpNEjAzEk>
Subject: Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 17:15:53 -0000

I'm not an expert in either WPAD [1] or PAC [2], but I am an expert in
feeling their pain as a user on Windows. Part of their pain comes from lack
of formal standardization, resulting in some word-of-mouth approaches to
problem solving, especially how they work (or don't) with the standardised
approaches such as DHCP.

In looking this up, I did discover draft-ietf-wrec-wpad-01, a > 20 I-D for
WPAD [3], wow!

[1] - https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol
[2] - https://en.wikipedia.org/wiki/Proxy_auto-config
[3] - https://tools.ietf.org/html/draft-ietf-wrec-wpad-01

On Mon, Nov 4, 2019 at 5:09 PM Mirja Kuehlewind <
mirja.kuehlewind@ericsson.com>; wrote:

> Hi Lucas,
>
>
>
> no, we didn’t consider this yet but only because we were not really aware
> of that. Do you have a pointer? Or send a PR 😊
>
>
>
> https://github.com/mirjak/draft-kuehlewind-quic-proxy-discovery
>
>
>
> Mirja
>
>
>
>
>
> *From: *Lucas Pardue <lucaspardue.24.7@gmail.com>;
> *Date: *Monday, 4. November 2019 at 18:06
> *To: *Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>;
> *Cc: *"quic@ietf.org"; <quic@ietf.org>;, "masque@ietf.org"; <masque@ietf.org>;,
> Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>;
> *Subject: *Re: [Masque] FW: New Version Notification for
> draft-kuehlewind-quic-proxy-discovery-00.txt
>
>
>
> Thanks for sharing this.
>
>
>
> I wonder if you considered WPAD (Web Proxy Autodiscovery) or PAC (Proxy
> auto-config)? Although targetted at the application layer, it might help to
> comment on how those forms of discovery would relate to the methods
> outlined in your draft.
>
>
>
> Cheers,
>
> Lucas
>
>
>
> On Mon, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind <mirja.kuehlewind=
> 40ericsson.com@dmarc.ietf.org>; wrote:
>
> Hi all,
>
> we submitted a new draft that lists discovery mechanisms for QUIC-based
> proxies (see below). This is one piece of work that is needed for most of
> the use cases in draft-kuehlewind-quic-substrate.
>
> Let me know if you have any questions or comments!
>
> Mirja
>
>
> On 04.11.19, 17:53, "internet-drafts@ietf.org"; <internet-drafts@ietf.org>;
> wrote:
>
>
>     A new version of I-D, draft-kuehlewind-quic-proxy-discovery-00.txt
>     has been successfully submitted by Mirja Kuehlewind and posted to the
>     IETF repository.
>
>     Name:               draft-kuehlewind-quic-proxy-discovery
>     Revision:   00
>     Title:              Discovery Mechanism for QUIC-based,
> Non-transparent Proxy Services
>     Document date:      2019-11-04
>     Group:              Individual Submission
>     Pages:              11
>     URL:
> https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discovery-00.txt
>     Status:
> https://datatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/
>     Htmlized:
> https://tools.ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00
>     Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discovery
>
>
>     Abstract:
>        Often an intermediate instance (such as a proxy server) is used to
>        connect to a web server or a communicating peer if a direct end-to-
>        end IP connectivity is not possible or the proxy can provide a
>        support service like, e.g., address anonymisation.  To use a non-
>        transparent proxy a client explicitly connects to it and requests
>        forwarding to the final target server.  The client either knows the
>        proxy address as preconfigured in the application or can dynamically
>        learn about available proxy services.  This document describes
>        different discovery mechanisms for non-transparent proxies that are
>        either located in the local network, e.g. home or enterprise
> network,
>        in the access network, or somewhere else on the Internet usually
>        close to the target server or even in the same network as the target
>        server.
>
>        This document assumes that the non-transparent proxy server is
>        connected via QUIC and discusses potential discovery mechanisms for
>        such a QUIC-based, non-transparent proxy.
>
>
>
>
>     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
>
>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>
>