IETF Logo Mail Archive

Re: Proposed response to the 3GPP Liaison Statement

Jana Iyengar <jri.ietf@gmail.com> Wed, 06 November 2019 02:11 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 7B9E6120236 for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 18:11:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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] 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 xc0mvATnyW9u for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 18:11:06 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 4319A120154 for <quic@ietf.org>; Tue, 5 Nov 2019 18:11:06 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id e9so10882861ljp.13 for <quic@ietf.org>; Tue, 05 Nov 2019 18:11:06 -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=08rrQjK51oQw8ytW6wUrBK2mxABbOBDNLwJDSIUFNLA=; b=QfOdsNI7t3nax1dx6k/Ve8oUWIB8wwIrQPLbykb3LsXRGJpEpb9P7NGio6EWw1ZtpO Uny3RpvQnZSwTN8ggD2F0BuooDx8HQtr2QuHaNIhqnq3sOYw90pYM5dHUS4BIg6/J5aM xP2YTD3pFgE32CRTuT7D78QDgyB0zfQiIEUMJafj+CPKZBfAb64c9jdlwgkdmZoeiVYT MDmReI2cJJVS5/BEm2iYp/DSbNzEivLgL4qSBZ79DtRkIxQJAnerwe136VX29AL4VvNM 6T3xHlyjYxdlKZxiwh99AgyTvZ2Otnodli6GE2PsCQUAbFvZlVrPfZbkgG7ZKBwKNx1Q pSFw==
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=08rrQjK51oQw8ytW6wUrBK2mxABbOBDNLwJDSIUFNLA=; b=fdjZeaY8yUZI5WGwKkS0ydWtpy3yXS9ElLf9KVAdK2vIRYGUoGb0NUkTva/IfdGpJT oZFMcoeG5q1kCj2bIkQn/pToXLb4albOQBhXLtrNyssdVw+1mv6KrMkw93MXszvG+y3t DhGcxEV/x+BhE5hWKgluwBe9ZQ2XM61BEHGxUEI4gFW9PVy1iGR/Pplru4BG0Vt4RN7Z e/TuD0gfyh1K3jHWY74M1Np90pJOnuilL1Mekh5wfISTq+kLqAG11mWIvQ0mcNvfGbT3 5PmWvDsH6Llt/0pqBKVsLeXIoMPis3/BActe2cz9p7u3QyGDylBlfVU3QasxxJB2xyg+ 06gg==
X-Gm-Message-State: APjAAAVw9X+yb0KMsc5T0iq5OgmlRlHbQOKcAJ3+M6aPD8lMEM4GZrul trcFiolizZlQi6fudoybUQPqIuuihALvCY3pF30=
X-Google-Smtp-Source: APXvYqxrJWR11AJdHOIZAtP/bZ7W9bPXs01/n6RcPkiYBpkj2nKj79pud1lYrxZvG+ATGvFLox8hn/6IaI4X6R/O4aQ=
X-Received: by 2002:a2e:481:: with SMTP id a1mr25589908ljf.209.1573006264568; Tue, 05 Nov 2019 18:11:04 -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> <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com> <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 05 Nov 2019 18:10:53 -0800
Message-ID: <CACpbDceF2mbVc63CKHNYbUDwdpJ2eMWgmoqkqbAkBwBxJ8g_pQ@mail.gmail.com>
Subject: Re: Proposed response to the 3GPP Liaison Statement
To: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, David Schinazi <dschinazi.ietf@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a110310596a40fb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e8v7szkmtuM8iTxMLI26yFnll_4>
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: Wed, 06 Nov 2019 02:11:09 -0000

Hannu,

The request from 3GPP was about a non-HTTP use case.

- jana

On Tue, Nov 5, 2019 at 1:12 AM Flinck, Hannu (Nokia - FI/Espoo) <
hannu.flinck@nokia-bell-labs.com> wrote:

> 3GPP is using HTPP very well in their use case (see more in 3GPP 29.500, Technical
> Realization of Service Based Architecture.). Insisting focus on HTTP in
> the response is not helpful, but confusing instead.
>
>
>
> Best regards
>
> Hannu
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of *Jana Iyengar
> *Sent:* Tuesday, November 5, 2019 2:51 AM
> *To:* Salz, Rich <rsalz@akamai.com>
> *Cc:* David Schinazi <dschinazi.ietf@gmail.com>; Ted Hardie <
> ted.ietf@gmail.com>; Lubashev, Igor <ilubashe@akamai.com>; Martin Thomson
> <mt@lowentropy.net>; IETF QUIC WG <quic@ietf.org>
> *Subject:* Re: Proposed response to the 3GPP Liaison Statement
>
>
>
> 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?
>
>

v2.23.0 | Report a Bug | By Email