Re: Proposed response to the 3GPP Liaison Statement
Ted Hardie <ted.ietf@gmail.com> Thu, 31 October 2019 13:58 UTC
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 230EB120048 for <quic@ietfa.amsl.com>; Thu, 31 Oct 2019 06:58:22 -0700 (PDT)
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=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 CHPKiyqxeNUq for <quic@ietfa.amsl.com>; Thu, 31 Oct 2019 06:58:19 -0700 (PDT)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 BA908120044 for <quic@ietf.org>; Thu, 31 Oct 2019 06:58:19 -0700 (PDT)
Received: by mail-il1-x131.google.com with SMTP id s6so5490818iln.0 for <quic@ietf.org>; Thu, 31 Oct 2019 06:58:19 -0700 (PDT)
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=SGs1XoEMy/FxmHz6DjsJ+CzebnlbhYWdsSx2QdSgbEY=; b=MN0Khgy/FcyfRRtQBcuadLdyudL3JR0Us95+OkXniuv24ZYA/ZavvvhLUZhWW9dcKF qB9k6w0gmGSUp2TOEL9QJbQvMV12atekzXHAYHowLjyyWehuhYWTJ06OupAYFBxsb24W 9aeUIfKbqy7JZOgnl/u3cBAoHbZPQZc8mn9EcM7yeVAnESjRyQSZlEcFfMom5U5fRxzr NFByje58NSNd12iOATLmQRKfE3N5vZYEJBwWl4eEIHpgeHr4BZeFS9a+AwsP/MmizFag 7CXQo/eC6W3ekyFHSzVGsJx2GJFMvTolH6D2p+iF5F99c3tfSATqS7cIy7jt4aOthLsb MvpQ==
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=SGs1XoEMy/FxmHz6DjsJ+CzebnlbhYWdsSx2QdSgbEY=; b=EFs9JS9AUW78GVLARxqf91Nw21pMfWAEfNgvVsAmmmn/qKQoML7B+gqhoVzrNIowPq r6Q0N5TCP+xZA1J8O7IjaoAvpmeQIy0WUs/Xy3fE6cHmcHHPI5d+yTzUH5U12EhVWLMO jhxw6JhigCjU7X55sLh1zPeG8+/Rz8ve25PjRLxcGbhCi6iqZ6r+/nXsFES+eSdBF1a8 cKk+1t/z6lKMgrYZajEZLSIXl+kfj3/TzMbfLAgFWuy2O3zV45kO9zB8QH7Ed73WvVt8 qXnYXoRn5pgbOcUP/Cvny5/XVRB+SES40Ge5E7YqpFW06hMACnmcSwOLJDXfFj0pFHOX HPzg==
X-Gm-Message-State: APjAAAXttY4vOWIBfR9eKYoe2bsw98+z7MCScax5noIM9jH47CmDUN0+ 3TKenwyEVoVIhPmvGdfzlbT1YPMuVLOjnrcW+7AKjQ==
X-Google-Smtp-Source: APXvYqxOdjfrWGdQ8eyHdYNSLdc+GU1rOcJ8KKIhg2vPp8mPwPPPa3hv2kmIlZshFZ8zaDOYpWTshdiOL9r1LyvYsLE=
X-Received: by 2002:a05:6e02:cc1:: with SMTP id c1mr3047958ilj.139.1572530298817; Thu, 31 Oct 2019 06:58:18 -0700 (PDT)
MIME-Version: 1.0
References: <3218A80B-DAFD-43EF-8200-F99C660DF9C9@mnot.net> <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com>
In-Reply-To: <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 31 Oct 2019 06:58:06 -0700
Message-ID: <CA+9kkMBbuG+4309XfZoVb69Pz_s3=RPv2JWZS8zrkVFBkDMJuw@mail.gmail.com>
Subject: Re: Proposed response to the 3GPP Liaison Statement
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dc18e70596353dec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-ShrBRApINCSMzImaMSL12HpZM0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 13:58:22 -0000
On Wed, Oct 30, 2019 at 6:14 PM Martin Thomson <mt@lowentropy.net> wrote: > https://tools.ietf.org/html/draft-iab-path-signals-03 seems like it might > be a helpful supporting document. > > If you do choose to cite it, it has been published as RFC 8558, so it would be best to use that. Ted > On Thu, Oct 31, 2019, at 12:09, Mark Nottingham wrote: > > QUIC WG participants, > > > > Lars and I have discussed a response to this statement and plan on > > sending the message below. If you have comments, please respond to this > > e-mail by 6 November. > > > > Regards, > > > > ~~~ > > Thank you for your input to our specifications. > > > > Regarding the encryption of headers in addition to payload, this was a > > conscious design decision by the Working Group. Transport header > > encryption prevents modification by middleboxes, thereby avoiding > > ossification of the protocol, and also makes traffic analysis more > > difficult. The impact upon network operators was discussed extensively > > as part of that decision. > > > > Regarding the spin bit, we believe that your characterisation is correct. > > > > Regarding packet loss measurements, QUIC does support them, but only by > > the endpoints of communication -- not by third parties observing it. > > Keys may be exported by one of the endpoints to allow decoding of > > packet traces (e.g., with Wireshark), but that is not part of the QUIC > > standard. > > > > Regarding performance analysis, it would be helpful if you described > > your use case in more detail. However, it's important to know that the > > Working Group decided early on that QUICv1 would focus on the use case > > of HTTP/3. > > > > In turn, HTTP standardisation focuses primarily on the Web browsing use > > case; while we acknowledge that there are other uses of the protocol, > > and we accommodate them where possible, we cannot change the protocol > > in ways that harms that use. Exposing transport metadata would likely > > do so. > > > > Kind regards, > > > > Mark Nottingham and Lars Eggert, QUIC Working Group chairs > > ~~~ > > > > > >
- Proposed response to the 3GPP Liaison Statement Mark Nottingham
- Re: Proposed response to the 3GPP Liaison Stateme… Martin Thomson
- Re: Proposed response to the 3GPP Liaison Stateme… Ted Hardie
- RE: Proposed response to the 3GPP Liaison Stateme… Lubashev, Igor
- Re: Proposed response to the 3GPP Liaison Stateme… David Schinazi
- Re: Proposed response to the 3GPP Liaison Stateme… Martin Thomson
- Re: Proposed response to the 3GPP Liaison Stateme… Salz, Rich
- Re: Proposed response to the 3GPP Liaison Stateme… Jana Iyengar
- RE: Proposed response to the 3GPP Liaison Stateme… Flinck, Hannu (Nokia - FI/Espoo)
- Re: Proposed response to the 3GPP Liaison Stateme… Jana Iyengar