Re: Proposed response to the 3GPP Liaison Statement
Jana Iyengar <jri.ietf@gmail.com> Tue, 05 November 2019 00:51 UTC
Return-Path: <jri.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 64DDF120114 for <quic@ietfa.amsl.com>; Mon, 4 Nov 2019 16:51:05 -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=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 61a4SlnMl_Pa for <quic@ietfa.amsl.com>; Mon, 4 Nov 2019 16:51:03 -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 353A412006F for <quic@ietf.org>; Mon, 4 Nov 2019 16:51:03 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id e9so6451462ljp.13 for <quic@ietf.org>; Mon, 04 Nov 2019 16:51:03 -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=2XBb2HdZ9OxbKCVKqVi7PgThcu+UxeO+HGjl1FKLQxg=; b=iHLHllxqwCTPjBT/1IUsHVjRsE0GB3ID08TN9XytAze/HB+Kxmqrpr64LG5jfB8pjR 02lAlBIWamc4CHh/yLFf42v+fV4bW3QjTaWXCKoeGoh74WtFuXdtRsJY/bchV5gzDQd9 e5T1IHkizL1zCzIoUzyZhIboUpN2dU+Z3ZDXkbidReoTqSDy52H2t7KCBg35mQWayvhw x8MZZKMm1bhqHQVh9z1yszNsuOjS06QGsccUnKedXxqRc4/Z+rYhXkt3kM+Vtx7y8Mlv XABpHo5hh2mUu2IjaLb4muz6it8EcKsJPcVoaIGi+jkm/u0qDZ9+4MWVybaAjkP6U1ZM 8jNg==
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=2XBb2HdZ9OxbKCVKqVi7PgThcu+UxeO+HGjl1FKLQxg=; b=qBntEk3CajUkufIbRlnFlhCTWl0m2sOcTyYseIeGXclQ38/TBbITLj4AFA757uKTm/ niwgf1saerDzRqCGlnr9x6RHVTnIuBa/wsWK5LHyeM3KWhIRT/KwF5B7QjXYFrz8u6Lv MTp8L13yz09QjGfuwwX/DE3BuFfN9kiFAsvm5LCgaLW7dQy1Y1CbhYD5QCYexX8g5MxL 13EkzVidkm/yfonlKdWV+WquN+h4xQhb4tr4tP9cdiT8AAGp5Lb5wDbeFff6BlY0JLCD CsHa/CPLfG5aFlXkeZIMp0RWus1FoFQ6mqlXadnC3C5SWC2R+sAI/VrG+q2Sq56t1NGg 8uYQ==
X-Gm-Message-State: APjAAAWDHbN6YoAkfABv1MRlnpTq3TUFXsFpUbuS0vGX3ZXhNYI0Sl/t RlYjobK/MegWxUtO4LoJiyVW8FHLvnTBhQY9PgI=
X-Google-Smtp-Source: APXvYqyiijG3/iQbWRrddn7qOrW9B2/N3Xfq8SBNSBlsf/Y5lL4nc+FrPz0oKjMLeiEDdE5k6OEsk8i5SAV4hpMJC4U=
X-Received: by 2002:a2e:9954:: with SMTP id r20mr2809119ljj.197.1572915061451; Mon, 04 Nov 2019 16:51:01 -0800 (PST)
MIME-Version: 1.0
References: <3218A80B-DAFD-43EF-8200-F99C660DF9C9@mnot.net> <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com> <CA+9kkMBbuG+4309XfZoVb69Pz_s3=RPv2JWZS8zrkVFBkDMJuw@mail.gmail.com> <614379f7e12f46c6b38b7928e999cbab@ustx2ex-dag1mb5.msg.corp.akamai.com> <CAPDSy+6PHwfVReNsAFMHE3KsvM2K_ACD7sUtqikri7oG-QGfLg@mail.gmail.com> <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com>
In-Reply-To: <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 04 Nov 2019 16:50:50 -0800
Message-ID: <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com>
Subject: Re: Proposed response to the 3GPP Liaison Statement
To: "Salz, Rich" <rsalz@akamai.com>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="0000000000007ff12b05968ed375"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4tWkgZ2cyJSE4JF1_me-sfvobo0>
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: Tue, 05 Nov 2019 00:51:05 -0000
The response looks sensible and accurate. I would suggest just one change: move the point about HTTP/3 focus (maybe the last two paras) to the top of the response, adding to it that the QUIC wg is currently chartered to focus on HTTP. Without getting into the use case that they are trying to fit QUIC into, it's difficult to understand the importance of the loss bits. And we surely do not want to block QUICv1 trying to understand that use case. On Thu, Oct 31, 2019 at 3:57 PM Salz, Rich <rsalz@akamai.com> wrote: > Maybe we should suggest that they write an I-D for what they think their > requirements are? > > >
- 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