IETF Logo Mail Archive

RE: Questions on HTTP URI schemes and QUIC

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Thu, 19 July 2018 19:36 UTC

Return-Path: <Lucas.Pardue@bbc.co.uk>
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 2A5AB13111B for <quic@ietfa.amsl.com>; Thu, 19 Jul 2018 12:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 MTxklcdns1YG for <quic@ietfa.amsl.com>; Thu, 19 Jul 2018 12:36:31 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DECC713107A for <quic@ietf.org>; Thu, 19 Jul 2018 12:36:30 -0700 (PDT)
Received: from BGB01XI1012.national.core.bbc.co.uk (bgb01xi1012.national.core.bbc.co.uk [10.161.14.16]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w6JJaNh5008114; Thu, 19 Jul 2018 20:36:23 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1012.national.core.bbc.co.uk ([10.161.14.16]) with mapi id 14.03.0389.001; Thu, 19 Jul 2018 20:36:23 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Sridhar Bhaskaran <sridhar.bhaskaran@huawei.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Questions on HTTP URI schemes and QUIC
Thread-Topic: Questions on HTTP URI schemes and QUIC
Thread-Index: AdQehQaTzEsbGZZvQ4ml64uCil/3zQAGQAMgAByo3kAAIXnVMA==
Date: Thu, 19 Jul 2018 19:36:23 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB786A5@bgb01xud1012>
References: <0E42DD26875E1748992B1E3F732A36AE0129BCBA@BLREML503-MBX.china.huawei.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB77BFA@bgb01xud1012> <0E42DD26875E1748992B1E3F732A36AE0129C45B@BLREML503-MBX.china.huawei.com>
In-Reply-To: <0E42DD26875E1748992B1E3F732A36AE0129C45B@BLREML503-MBX.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-23980.000
x-tm-as-result: No-6.773700-8.000000-10
x-tmase-matchedrid: cgbqQT5W8he7lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p2o+b+yOP0oGCGZ 6VVOVYeW1Fc61VCGvh1ksMOLRwwsVw9DNWzI2FEPQJOfGClqJxm0xIzVr7UlbzaULO2AzDKgBK6 s6YP1Blq61M5/Y3W4NE/SoXfxRM/UK2D6pmarVf/XIwmz2YEJxYrogmbAtARIOdl/GMFVBFtnHb mOz4dRQ+fOVcxjDhcwPcCXjNqUmkUgBwKKRHe+r/NQIWjWJOcZRjHPAocdpPudfkZxob/od5Gct dgmmRomL4wskVNIozg=
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--6.773700-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-23980.000
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/yyrhBFVqqHesTGLy40On5fAmbYg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.27
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, 19 Jul 2018 19:36:40 -0000

Hi Sridhar,

Thanks for sharing the 3GPP work.

Sridhar wrote:

>Note that this SEPP is not a blind forwarding proxy. It does message
>transformations based on operator policies. So as highlighted in slide 8 SEPP's
>role is "in the loop".

Are the required transformations shareable (or captured in some 3GPP document). We are aware of a congestion control use case but additional ones are welcome.

However, considering the model I have for tunnelling QUIC, the amount of in-the-loop processing possible is likely to be minimal due to the end-to-end QUIC security context. The proxy will have access to IP, UDP and QUIC headers but not QUIC protected payload.

Kind regards
Lucas

v2.23.0 | Report a Bug | By Email