RE: Proposed response to the 3GPP Liaison Statement
"Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com> Tue, 05 November 2019 09:13 UTC
Return-Path: <hannu.flinck@nokia-bell-labs.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 256FF120844 for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 01:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 OUmJLBuHFcZe for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 01:12:59 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60124.outbound.protection.outlook.com [40.107.6.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF10120841 for <quic@ietf.org>; Tue, 5 Nov 2019 01:12:59 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G56Hmzoc7yTYDoK7aRw4Mdj26e6/SsX75q78CknHL/qqBfsWvaGcFf1lZlsMA+3g4VCA9fglJoADXCxChDm94NHu7OoPITX+xNM8km5PVrib2iOkVrkbpqs+Fc/LfbI/VwGqGY5F+19CWDiJNMSEOIdP/6YL6Mf1hu0OpROdYSpBhm/DxnSUW38RGZnKmuf+nhZ2Pv9EcfEDeuTj49jSLZkXLs/7EtAx3GIa3Pus9u6tP7OD9/VOAjczUTkMFNOIrRxX+EOn0EMgr+U/oeL9K4JD5yRKwpgSJpcJ7Uesa/jnl08FCn06HK9rq+DnUjY5zOkQOSJubBE6IBlLwdoQbQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IiYN8TkfaykYRBKFYs5+KJBofka2BVeRPef9nN26gmQ=; b=MtoMxc7sq+Puu1/lQ4+PdU7ft1A5dqGsFLmlQmg0eveiRnjhO/sWdi4Q5TDBteuEZoh4ukYLU2t5kn7efSK1tEo8RGK1D4vyVyTmC2c7Hr5SQ2gjqE3GtwC121IhzB+CFwIY43iTaL9e9trcj3JJUNltcKYhU5dn4tePzefKGr8F5e7ehs5sS1XQNV/DKUJJw70DD9GxbnXOE2eaV4NXTgxgEE0cBdCpFMAscwN/LlWPXAg6i0ix6PjcqO7EVgHTV8eDDNQWbRzVczT2FHofGoiszabQoRB+6tFmMa785HXF/RbN9y82HnX1lK7pO6c/av5MKwi1P+5oZ6kBCqGKFw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia-bell-labs.com; dmarc=pass action=none header.from=nokia-bell-labs.com; dkim=pass header.d=nokia-bell-labs.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IiYN8TkfaykYRBKFYs5+KJBofka2BVeRPef9nN26gmQ=; b=RUkfK/QzA1j6/JvIM/fwR5xCyO0l+BBTKhaGIA7nolEFmNDjbhLDuU30/l7htD2Zp28qv29UkPjT4Rl67bDvSoyurydoJRCdNMGxJBTKzUNj6gaSGhGsXi3kSlZ5AM6QFVAQaTptxDRgX6ym7lQDyDRO0jNYCzhIL8gDh4KzBTQ=
Received: from HE1PR07MB3306.eurprd07.prod.outlook.com (10.170.242.27) by HE1PR07MB3385.eurprd07.prod.outlook.com (10.170.244.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.15; Tue, 5 Nov 2019 09:12:54 +0000
Received: from HE1PR07MB3306.eurprd07.prod.outlook.com ([fe80::ed4e:9a7a:99c3:f4c1]) by HE1PR07MB3306.eurprd07.prod.outlook.com ([fe80::ed4e:9a7a:99c3:f4c1%6]) with mapi id 15.20.2408.016; Tue, 5 Nov 2019 09:12:54 +0000
From: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
To: Jana Iyengar <jri.ietf@gmail.com>, "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
Thread-Topic: Proposed response to the 3GPP Liaison Statement
Thread-Index: AQHVk3MjNniwyX9WDk+/sAGVUFFHQ6d8SWsw
Date: Tue, 05 Nov 2019 09:12:54 +0000
Message-ID: <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
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>
In-Reply-To: <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hannu.flinck@nokia-bell-labs.com;
x-originating-ip: [131.228.2.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 7773b87b-ccdf-4365-15fb-08d761d05754
x-ms-traffictypediagnostic: HE1PR07MB3385:
x-microsoft-antispam-prvs: <HE1PR07MB3385AF323E455069F58FD9BF9B7E0@HE1PR07MB3385.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(346002)(396003)(376002)(39860400002)(189003)(199004)(81166006)(25786009)(55016002)(236005)(9686003)(186003)(71190400001)(446003)(53546011)(6506007)(7696005)(76176011)(66556008)(14454004)(2906002)(3846002)(102836004)(66066001)(6306002)(86362001)(8676002)(26005)(66946007)(76116006)(66446008)(790700001)(64756008)(4326008)(71200400001)(6116002)(52536014)(5660300002)(66476007)(7736002)(11346002)(81156014)(8936002)(478600001)(6246003)(476003)(486006)(74316002)(99286004)(229853002)(110136005)(54906003)(33656002)(6436002)(256004)(54896002)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB3385; H:HE1PR07MB3306.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FhqsbpoXFHmt7RT8ttwJvXUXC3eITAecuwVTF0913gsIgXDkDBdkjm0oWDmo9zi2p/PghpxMNdGIjcCFreeaEPhHiNddFuP1rlJTs2zaTg3YEMdl6V+Y87BWvgm0jY8m7mAQ8KRgaKUb/jZJ40hrCs5xc6YWZMjHOoT1guhhKbMJ0by3Y0/2zxJhZ/yNp6h+0X1vzX8Zh9NgSytcsTU84vxN1etPR2WJPYVe2pJElb9RgBcdO3S+Zud5LfPPDRsDzkZjxw2TUg9kvcjbnp2wCgBl/Ph+RuqXAbDw9oGy584dU6GUYEEViakMC2zOOYfCbQhBPcXnuaoD6s18YUceDqADQFogLPO92MFR+Co3Xp1+Ll+mqFPiqQMWC3ut4xR5YzYD3Jc2d+gHwsVSLKr7R3rUbBs1qCL2Xta31e6Rq1xtEXB5ugk7i40ZqU67L4FS
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3306A309F29ED901A2957D1D9B7E0HE1PR07MB3306eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7773b87b-ccdf-4365-15fb-08d761d05754
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 09:12:54.1035 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8x6x1L8yMgx+9hZoZroill6ZXvzkwhGyuqweTCSx04KVOanJXq/tWiHnKaZ8QRN2iyfciqbs8ZT9hCNNsZrLL8mTSbUeATYIDyVW1fE0M9hCMORO/qLl8dCUVJiXC6Uo
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3385
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/31lCL90mv_Xf1Kc-c7-0F73WrJw>
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 09:13:02 -0000
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<mailto: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