IETF Logo Mail Archive

Re: [Masque] Proposed draft charter

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 12 February 2020 01:10 UTC

Return-Path: <spencerdawkins.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 485C512085E for <masque@ietfa.amsl.com>; Tue, 11 Feb 2020 17:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=unavailable 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 kPvJcqw0nrLq for <masque@ietfa.amsl.com>; Tue, 11 Feb 2020 17:10:17 -0800 (PST)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 1D8EE12085D for <masque@ietf.org>; Tue, 11 Feb 2020 17:10:17 -0800 (PST)
Received: by mail-lf1-x12e.google.com with SMTP id m30so303495lfp.8 for <masque@ietf.org>; Tue, 11 Feb 2020 17:10:17 -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=JLMfobu4hmIffP28V8SpGKJ/QL6kZlc16QD+ZTHLw+M=; b=ixlOZVmvNcd+W/5L5VxQGEdv8Vgz6cQTFN/BoD+PgAgt3808oRKTSmbiMMptwb6Epi Brfsy91vUaw8D+MQPLm4Srv4LBOXi9PP+HawkYj9mSogXnwHcl7m81VWn6iLtg5WKPBL l2v56ut9xFcC3WKLDxPI4Z3zrkM5i0mTHVIwH5cu9BLDKDdHJh/nEAyWEyxQwH+J9Lfz j+vOiRK/ID6YGwrcxLXbSJc3uZeeU6WHppvD8OqosXjcVWhUXKRHpuEF9w5Dd0kBqGmN wGlkMmEtCsb0jHxLcsfyK4gO0QCttw78sBFBL0RuH1lE8D3fNwN0dnna46rwSaDb7Vs+ 9dHQ==
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=JLMfobu4hmIffP28V8SpGKJ/QL6kZlc16QD+ZTHLw+M=; b=KbJdtuEQXuwrDDKBxq+R+oPbUO/7rdAZDkBE8L9Z85sd5YMtRO264ug+keGibnxx/T 7YeyTDHhQiLxj6VPglZf+NPnSIB9IhXHj4fP2zKcb0Tu6FcUHW6n3ZAiBdNCvoyFnzkz jIu9zWF1pY/FBvgRdOREkmuHBpDTPqgVSoSTZB1555ZJHng4Ixq8WiId9F0ysKlum9/4 jTvehVUmCF/w7v7tlZJoZ6j5ucVjc/HiJO4r+CrqonSPjb/yYzGtkePtEa2oboBA15hX nV9F4H+dWpL6l5rCZWCs5nNw4LtZ9W+vf5vSTe1gDII5lv4uQ6++cCW5AxTDO9BvRffO XCJg==
X-Gm-Message-State: APjAAAXWkKlC69ZnS/0zb6BtH0IYC9HVyXHIiXSfhVFLKuEv8yLT7ojL FWHW4fFOkHqF7GrIpapqimWlvqls6uob5lKtsB0=
X-Google-Smtp-Source: APXvYqwE0iHySO0/VgvIrR7lBIAE6Ah9owpu4LXdD9IJJFZrvr3/wyNGt/7B7iMX2s665gqCrgtwCTJidiYQTy4zOdQ=
X-Received: by 2002:a19:c82:: with SMTP id 124mr5111982lfm.152.1581469815360; Tue, 11 Feb 2020 17:10:15 -0800 (PST)
MIME-Version: 1.0
References: <845946C2-EB98-4F3A-966E-968AE349302C@ericsson.com> <CABcZeBOJtyaa+J9PqoEZ7n8QahFy4n8nbBaCwUd0W+1BoMNnZQ@mail.gmail.com> <E68FB662-F6E5-49EE-AD92-AFCCCEA0CCE9@ericsson.com> <CABcZeBNEekD6GivQUvg8Gmz=_0EB1T_7PAeK=MNR_7+ObWJuTA@mail.gmail.com> <AE645E8F-6E17-4844-B8CC-373EB0909775@apple.com> <C58665A7-8550-4828-A7CD-603E3A64CFAF@ericsson.com> <1E734838-6F8E-4F13-AEEE-0A00F3E0C04C@apple.com> <CAKKJt-dFrVvcWUAVjAWMJHxk2BOhX+-y1R65i9KFLmB4SHDncA@mail.gmail.com> <CAKKJt-dQ8SR-f7MLv372O9dnZWnRHxNNEFcdpWT3dVZJrB37Xg@mail.gmail.com> <CABcZeBMX+iS9CKusrraarKycQviVLHeFi6H=Avf9hG5MCc5wyQ@mail.gmail.com>
In-Reply-To: <CABcZeBMX+iS9CKusrraarKycQviVLHeFi6H=Avf9hG5MCc5wyQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 11 Feb 2020 19:09:49 -0600
Message-ID: <CAKKJt-f4WyJc-k2o+Rf93Ec+kgqZ6rfBe3mc4XVyWiRKvzNiUA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Eric Kinnear <ekinnear=40apple.com@dmarc.ietf.org>, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, "masque@ietf.org" <masque@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000915145059e56a215"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/7E8U4Vd7gBnTDa_MNHnRU-HghVw>
Subject: Re: [Masque] Proposed draft charter
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: Wed, 12 Feb 2020 01:10:20 -0000

Hi, Eric,

On Tue, Feb 11, 2020 at 2:52 PM Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Tue, Feb 11, 2020 at 12:50 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Just following up - I had two questions, and people might have missed the
>> first one .
>>
>> On Mon, Feb 10, 2020 at 6:31 PM Spencer Dawkins at IETF <
>> spencerdawkins.ietf@gmail.com> wrote:
>>
>>> I'm finally reading this charter, as opposed to looking at the words ...
>>> mostly, this looks fine to me.
>>>
>>> A couple of things inline..
>>>
>>> On Thu, Feb 6, 2020 at 6:05 AM Eric Kinnear <ekinnear=
>>> 40apple.com@dmarc.ietf.org> wrote:
>>>
>>>>
>>>> (Deleted down to )
>>
>>>
>>>> QUIC is a good candidate protocol for tunneling these types of traffic,
>>>> as QUIC
>>>> provides secure connectivity, multiplexed streams, and connection
>>>> migration.
>>>> Further, HTTP/3 supports an established request/response semantic that
>>>> can be
>>>> used to set up and configure services.
>>>>
>>>
>>> The definition of QUIC as practiced in 2020 is "HTTP/3 over QUIC",
>>> although we certainly see proposals for other application protocols over
>>> something QUIC-like. Would something like
>>>
>>> "HTTP/3, carried over QUIC, is a good candidate protocol for tunneling
>>> these types of traffic, as QUIC
>>> provides secure connectivity, multiplexed streams, and connection
>>> migration.
>>> Further, HTTP/3 supports an established request/response semantic that
>>> can be
>>> used to set up and configure services."
>>>
>>> make that clearer?
>>>
>>
>> (deleted)
>>
>
> No, I dont think this is correct. We are most likely going to use Datagram
> for tunnelling UDP, and that is not part of H3.
>

That's kind of what I expected, but it sure isn't clear from the
description of what QUIC is providing, which is

"QUIC provides secure connectivity, multiplexed streams, and connection
migration."

Perhaps it's worth mentioning datagram as well, given that secure
connectivity,  multiplexed streams, and connection migration have been in
the QUIC charter since 2016, and datagram is only being added to the
proposed charter now.

Best,

Spencer


>
>> Best,
>>
>> Spencer
>> --
>> Masque mailing list
>> Masque@ietf.org
>> https://www.ietf.org/mailman/listinfo/masque
>>
>

v2.23.0 | Report a Bug | By Email