IETF Logo Mail Archive

Re: [WARNING: ATTACHMENT(S) MAY CONTAIN MALWARE]Re: HTTP(3) priorities

"Oliver, Wesley, Vodacom South Africa (External)" <Wesley.Oliver@vcontractor.co.za> Thu, 25 July 2019 06:51 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC9212036D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Jul 2019 23:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 igo6aRiw4uns for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Jul 2019 23:51:26 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (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 C035E120355 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 24 Jul 2019 23:51:26 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hqXYY-00051g-NR for ietf-http-wg-dist@listhub.w3.org; Thu, 25 Jul 2019 06:48:50 +0000
Resent-Date: Thu, 25 Jul 2019 06:48:50 +0000
Resent-Message-Id: <E1hqXYY-00051g-NR@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <Wesley.Oliver@vcontractor.co.za>) id 1hqXYV-00050p-SB for ietf-http-wg@listhub.w3.org; Thu, 25 Jul 2019 06:48:47 +0000
Received: from vbmtbmm003.vodacombusiness.co.za ([41.0.3.6]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <Wesley.Oliver@vcontractor.co.za>) id 1hqXYT-0002pc-Lm for ietf-http-wg@w3.org; Thu, 25 Jul 2019 06:48:47 +0000
Received: from ZAEXMBXPP02.vodacom.net (Not Verified[10.132.88.150]) by vbmtbmm003.vodacombusiness.co.za with Trustwave SEG (v7, 3, 6, 7949) id <B5d39506a0002>; Thu, 25 Jul 2019 08:47:06 +0200
Received: from ZAEXMBXPP01.vodacom.net (10.132.32.205) by ZAEXMBXPP02.vodacom.net (10.132.32.203) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 08:48:19 +0200
Received: from ZAEXMBXTC02.vodacom.net (10.132.32.202) by ZAEXMBXPP01.vodacom.net (10.132.32.205) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 08:48:18 +0200
Received: from ZAEXMBXTC02.vodacom.net ([fe80::802c:a284:2b10:ea9]) by ZAEXMBXTC02.vodacom.net ([fe80::802c:a284:2b10:ea9%20]) with mapi id 15.00.1473.005; Thu, 25 Jul 2019 08:48:18 +0200
From: "Oliver, Wesley, Vodacom South Africa (External)" <Wesley.Oliver@vcontractor.co.za>
To: Kazuho Oku <kazuhooku@gmail.com>
CC: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Thread-Topic: [WARNING: ATTACHMENT(S) MAY CONTAIN MALWARE]Re: HTTP(3) priorities
Thread-Index: AQHVNrtpgTZw0n2Bd0qYIEPG+P4cXKbZ96KAgADjQQA=
Date: Thu, 25 Jul 2019 06:48:18 +0000
Message-ID: <564520DD-2BAE-48EE-9041-3FCF5531328A@vcontractor.co.za>
References: <CAKcm_gOzeufrZua5Y9HSVKn3UeuA+XM9bBmEw8W6LdtfhE5LDg@mail.gmail.com> <CANatvzw0rzbDFoc4GZy=KMsDT2udS1PwEK9uXJ4+HsA9CTtYcA@mail.gmail.com>
In-Reply-To: <CANatvzw0rzbDFoc4GZy=KMsDT2udS1PwEK9uXJ4+HsA9CTtYcA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-ID: <588E2399D5F7144183C8D0DA9F4F3125@vodacom.co.za>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Received-SPF: permerror client-ip=41.0.3.6; envelope-from=Wesley.Oliver@vcontractor.co.za; helo=vbmtbmm003.vodacombusiness.co.za
X-W3C-Hub-Spam-Status: No, score=-2.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, W3C_NW=0.5
X-W3C-Scan-Sig: mimas.w3.org 1hqXYT-0002pc-Lm 8a326d6abff53f5bf9106ec33233cb92
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [WARNING: ATTACHMENT(S) MAY CONTAIN MALWARE]Re: HTTP(3) priorities
Archived-At: <https://www.w3.org/mid/564520DD-2BAE-48EE-9041-3FCF5531328A@vcontractor.co.za>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36834
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi,

The only thing I could suggest is that you make those priority flags increments of 20,
So that if there are changes or minor priority preference per website, then
That in between numbers can be used. If there is any new future priority conventions
Then just add them in the middle of the 20 group splitting the existing group.
Maybe make the field 2 bytes, which allows for future expansion, were there are many files, streams
Which require a new priority order.

Otherwise one needs to build a priority map, over the deps, converting a high resolution to low resolution.

Kind Regards,

Wesley Oliver

> On 24 Jul 2019, at 19:14, Kazuho Oku <kazuhooku@gmail.com> wrote:
>
> Hi!
>
> Attached are the slides that Lucas and I presented during the side meeting.
>
> Thank you all for the feedback.
>
> 2019年7月9日(火) 21:00 Ian Swett <ianswett=40google.com@dmarc.ietf.org>:
>>
>> There has been quite a bit of discussion of HTTP priorities lately on both the QUIC and HTTP mailing lists, with more to follow.  The plan for IETF in Montreal is as follows:
>>
>> Monday: Overview of priorities for 15 minutes in HTTP, with 15 minutes discussion.
>> Wednesday: A side meeting will be held from 8:30-9:45am in Van Horne.
>> Thursday: I'll summarise the side meeting in Wednesday's HTTP session.
>>
>> Thanks, Ian
>
>
>
> --
> Kazuho Oku
> <The Priority Header Field.pdf>

This e-mail is classified C2 - Vodacom Restricted - Information to be used inside Vodacom but it may be shared with authorised partners.

"This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this linkhttps://www.vodacom.co.za/vodacom/terms/email-acceptable-user-policy"

v2.23.0 | Report a Bug | By Email