Re: [rtcweb] Comments on draft-jennings-rtcweb-qos (Re: Call for adoption of QoS draft)

Martin Thomson <martin.thomson@gmail.com> Mon, 17 September 2012 22:52 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE3121F846E for <rtcweb@ietfa.amsl.com>; Mon, 17 Sep 2012 15:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.731
X-Spam-Level:
X-Spam-Status: No, score=-3.731 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LkOjVV+G9HmU for <rtcweb@ietfa.amsl.com>; Mon, 17 Sep 2012 15:52:51 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id A1E8C21F846D for <rtcweb@ietf.org>; Mon, 17 Sep 2012 15:52:50 -0700 (PDT)
Received: by lbky2 with SMTP id y2so4920377lbk.31 for <rtcweb@ietf.org>; Mon, 17 Sep 2012 15:52:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=PYvUXyeZ+wSW507BnjkxOhFGY7wuuB91NbUE6+tGaos=; b=ZuZUtLPOSTcM83QCqEiZ+7gbFzksNDLom8n9ORT09H3ZSHfL0rRDa9xfjGntCOUYyP eJGx2EGSundZC8vGX5GLmmN0AA7NbT7sd/TCFNCzWdWVvYo//p/5k6NBVRzf7Zy8o8rg xBV/1pdQQdXh7QgQ9WfCFplxC/AXpy/u2fDAafDefvXv/dIujuoLg0WF5Tyoi7gLe0wj rNxXuNHPPR5/31mEvyi8LUy+ZTUk/SdXy533jzvXNqw1M1Xy6RL6ITDPDU0jdtK9OmoM /2dYdrOsuSYeujYRXjtZxbESa9FFw2ZI8NRyP3A5tcZb3c9P4kbjw8G3teENWRttOjgt G3rw==
MIME-Version: 1.0
Received: by 10.112.49.202 with SMTP id w10mr4346241lbn.109.1347922369349; Mon, 17 Sep 2012 15:52:49 -0700 (PDT)
Received: by 10.112.1.36 with HTTP; Mon, 17 Sep 2012 15:52:49 -0700 (PDT)
In-Reply-To: <185CB042-686A-42F4-A85C-934C6489D0BA@cisco.com>
References: <CA+9kkMBo10T=EgRXmkeB1vfB6MdUMVeWUpZowoXdP=E_+rm+mQ@mail.gmail.com> <504DF5EF.7070602@alvestrand.no> <CABkgnnVckXWQqGR2PhKz+ZO4wphzw6YxEKBRJq-KEUgYT8Agxg@mail.gmail.com> <185CB042-686A-42F4-A85C-934C6489D0BA@cisco.com>
Date: Mon, 17 Sep 2012 15:52:49 -0700
Message-ID: <CABkgnnUZBbpJgpmR7OGdMznOb_1V-c_wGMe8grSmSrLvXDuBZQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Comments on draft-jennings-rtcweb-qos (Re: Call for adoption of QoS draft)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2012 22:52:52 -0000

On 17 September 2012 15:16, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>> What do people think about NOT including QCI/WiFi markings?  Is it not
>> possible for a wireless interface to examine DSCP markings in order to
>> determine the markings for the link?  We should endeavour to maintain
>> the proper abstractions.
>
> On some OS is it is possible to see them but ignoring that … think for a second  about what these marketing are meant to be used for -  they are more meant to be seen by the network not the browser at the far end so not sure this matters much if the some OS can't provide this information to the application

I am not suggesting anything about reading the markings off packets.
Reading markings off is - as you say - close to useless.

I asked if it were possible to consider *not* specifying what link
layer markings are made for packets that are *sent*.  The suggestion
was that if DSCP markings were made, as suggested, the packets could
be marked on the way onto the link by the wireless driver using
whatever link-specific markings are appropriate.  That might lead to a
mapping from DSCP to QCI and WiFi markings, but not necessarily.  That
would be different to the straight-from-the-top application priority
to link-layer, as described in the draft.