Re: [Masque] Call for MASQUE use cases

David Schinazi <dschinazi.ietf@gmail.com> Fri, 06 March 2020 18:56 UTC

Return-Path: <dschinazi.ietf@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 6067B3A045B for <masque@ietfa.amsl.com>; Fri, 6 Mar 2020 10:56:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 rv8YBhmSQZiq for <masque@ietfa.amsl.com>; Fri, 6 Mar 2020 10:56:04 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 31F153A0040 for <masque@ietf.org>; Fri, 6 Mar 2020 10:56:04 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id f13so3330207ljp.0 for <masque@ietf.org>; Fri, 06 Mar 2020 10:56:04 -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=EwoTTPY6YUaJUZeVK1tkb3LKxOvjWsyhpiMM/cWy89Q=; b=FOIB1EHwQRYzJGhqDjJ8nd0rLDIuQiPLzo/1V9U/kD87WP64zqPP0tj865BwkwLb/H pgc7tiiyYokjDCBYg4h2pmpYsloIR7zL+qFASl9Df2qaYrIhF8MDBoReZruHx+TgUTib LTO3cGOoPaJGs+9AtQ3xpcJu6UjDUXn8C9ZTz5d4ugUnpIkFjXTq3HLjvsGxJOUZyzkM B+wGvBcmi6do+AyS6y8GXZ20C2nI7QFj1OGgFbGL2Pz+F2dEEJTVf2HwqRQ8FZYiBXBG SrrbdVpXSY0R3jfxQ8S9B6LL25t7UvrnJ7VCId77LCsDYTrVxA+dqQVFRNdWYk7OSPxq bX0A==
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=EwoTTPY6YUaJUZeVK1tkb3LKxOvjWsyhpiMM/cWy89Q=; b=qjDfl+BpisI2Sz9rzaJxxN50rNSb3PcbqMG4Rs2J6aji2Kdxjda56dkHJwBzEOcAbj ACwIeinm2mXV18vnVNUzrdFuZWF2uE+hoFBx0NNwvDrDSunz+l9G6K0T6wLFQ/1HDuzH B40SGC999wfKfQVbl0L4jsFWPwh5Zt4tB5Rw8hbrpPO1mOVHIzi3s8Bv+/qcc836qwya +uW1Bra/xdBPKzNHqS9ET/VoUW5ZlEZc8HOeWB0iGZ4WG+UosbipreFPo1F8C7onBp51 MyNArc7Y+VBwWG2Ew4M1O0jAIIGu47MuKYSuM3M7jZzBw0smSFDNFUxAYYZYudZ06ald P4Uw==
X-Gm-Message-State: ANhLgQ177A2Jy5tS1twkXRaeu/h/f1QdXZ9Ur3aA9FfZPMyX0cjIgL5n KniKuQbhJQcUNXdSTQxoDSWAGu5ddQjKW9VQez4=
X-Google-Smtp-Source: ADFU+vsSFLG9mLOF962o0/WuyeJCRK/eAJaYH6EQdwDKNzeXSbumMh8Wc0xwfcKqkHdJSzDdWIYpIzNQFi/qJswb50U=
X-Received: by 2002:a2e:6a09:: with SMTP id f9mr2755464ljc.107.1583520962427; Fri, 06 Mar 2020 10:56:02 -0800 (PST)
MIME-Version: 1.0
References: <D46D764C-F682-472A-AFDA-32DDF5CA5F6B@heapingbits.net> <CABcZeBPMUNgOVWMS_sXPTsCU2R+EaK9JDuZsJQ5KSQROXE+4Sg@mail.gmail.com> <CAHbrMsAVXmyvqJKNzcmHOvM3NvPqhpfC9MuDEq9kNUBKe7=7=g@mail.gmail.com> <CAKKJt-etTk6CAqbL1MdSV6gdCgqC2Wz8cdUqbdzbM2h3LKAMhw@mail.gmail.com> <CAHbrMsDqgx7h+TRKLOgW+a3B3+TLWoRE9_DVBVhcKGRC3G=rog@mail.gmail.com> <CAG0m4gQh7=Gvx2_k53st+szAoj+96ef=OK5hqp8_zKSbKr091Q@mail.gmail.com> <CALGR9oaxe54kPPMpsMWuoMiKDznHoyhTLHwmxJeTXdu-zh_xUg@mail.gmail.com> <CAG0m4gT0vA4qMZ=XFJ8DpF8MW4ARugzbCcQU1mgV5BYeX+rA=w@mail.gmail.com>
In-Reply-To: <CAG0m4gT0vA4qMZ=XFJ8DpF8MW4ARugzbCcQU1mgV5BYeX+rA=w@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Fri, 06 Mar 2020 10:55:51 -0800
Message-ID: <CAPDSy+6zdJah6dAZgdN-9k84b-2+O3SJY6UjObVxPt22dn5fBQ@mail.gmail.com>
To: Dragana Damjanovic <dragana.damjano@gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@rtfm.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Christopher Wood <caw@heapingbits.net>, MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000075c5a405a03434b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/XXy5lywC0z2ZHvqKY4V5z-kZ2uc>
Subject: Re: [Masque] Call for MASQUE use cases
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: Fri, 06 Mar 2020 18:56:07 -0000

Hi Dragana,

What's your use-case where the client has a set of IP address literals but
no hostname?

David

On Thu, Mar 5, 2020 at 10:00 PM Dragana Damjanovic <
dragana.damjano@gmail.com> wrote:

>
>
> On Thu, Mar 5, 2020 at 3:19 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
> wrote:
>
>>
>>
>> On Thu, Mar 5, 2020 at 2:05 PM Dragana Damjanovic <
>> dragana.damjano@gmail.com> wrote:
>>
>>>
>>> I was looking into implementing sending an IP address in CONNECT request
>>> to a proxy instead of host name. It is not easy to figure out if connect
>>> should be retried with another IP address.. Having better error codes would
>>> be helpful.
>>>
>>> dragana
>>>
>>
>> That's an interesting case. IIUC correctly, your client might ask the
>> proxy to use IPv6, which could fail, and your client might then try IPv4?
>>
>>
> yes. That would be most common case. We may retry a different ip address,
> but I am actually not sure how often is something like this happening
> because it may have a long delay depending on the netowrk error(try PIv4
> address 1 and if it fails tray IPv4 address 2)
>
>
>> A failure such as this today would be communicated by returning an HTTP
>> error status. Is there a gap that mean HTTP cannot be used to communicate
>> the specific error condition you describe?
>>
>
> no, I think you cannot be 100% sure, the error may mean multiple things.
>
>
> Thinking about it more, maybe it would be better to send a list of IP
> addresses and let proxy chose one or do a happy-eyeballing for example.
> That would mean a CONNECT with list of IP addresses instead of one or a
> host name.
>
> dragana
>
>
>
>
>> Cheers
>> Lucas
>>
>>
>>>
>> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>