IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Mon, 17 September 2012 22:19 UTC

Return-Path: <fluffy@cisco.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 621F721E808F for <rtcweb@ietfa.amsl.com>; Mon, 17 Sep 2012 15:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 g5nQPUGKKwy5 for <rtcweb@ietfa.amsl.com>; Mon, 17 Sep 2012 15:19:31 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 7740C21E808E for <rtcweb@ietf.org>; Mon, 17 Sep 2012 15:19:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1561; q=dns/txt; s=iport; t=1347920371; x=1349129971; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zmF31JqDmrG507C0hpjVuhetlMQXYPoNx1Lk0eao4Pg=; b=KJc//gQwOnn4GGtygGhyMHTIpN/0vRC5P2hfh042pQpX6uPRgxlLkwkS p/OBzJgUyDZI5TBcm0eH6G+18pNmf+NcvFlYvLmuX656gtI2RZSvty74l QOZ4+mq+f12v0iEmq+WI5m/stmmu+eiBuKmvNSRhfaiFoazcpNmyIUir3 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAI+hV1CtJXG//2dsb2JhbABFvCKBB4IgAQEBAwEBAQEPAQodNAsFCwIBCDYQJwslAgQOBSKHWAYLmjmgDgSLIYYIYAOVYo44gWmCZoIX
X-IronPort-AV: E=Sophos;i="4.80,438,1344211200"; d="scan'208";a="122546916"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 17 Sep 2012 22:19:31 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id q8HMJUGg029474 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 17 Sep 2012 22:19:30 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.26]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0298.004; Mon, 17 Sep 2012 17:19:29 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] Comments on draft-jennings-rtcweb-qos (Re: Call for adoption of QoS draft)
Thread-Index: AQHNlSKAoqIciQQiU0ubxXAsF2TA3Q==
Date: Mon, 17 Sep 2012 22:19:28 +0000
Message-ID: <07676155-04ED-4FA2-AEF5-6A6D7DB2FD00@cisco.com>
References: <CA+9kkMBo10T=EgRXmkeB1vfB6MdUMVeWUpZowoXdP=E_+rm+mQ@mail.gmail.com> <504DF5EF.7070602@alvestrand.no>
In-Reply-To: <504DF5EF.7070602@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.167]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19188.004
x-tm-as-result: No--33.708300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2A186A8672AC2F4DA7C791F357ADCB7E@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:19:32 -0000

On Sep 10, 2012, at 8:15 , Harald Alvestrand wrote:

> Since this draft is mercifully short, I did a quick review.
> 
> Notes:
> 
> - Pointers to documentation on how browsers are expected to be able to set QCI and WiFI markings would be a good addition. Compared to those, DSCP codepoint setting is well understood.

I think the draft needs all the correct pointers to the specs for this the QCI / WIFI stuff as well as pointers to the normative mapping tables defined by the appropriate SDOs for them. If the device is sending a packet on a network that supports QCI or Wifi marking, it can use them.  I'm not really sure what else to say. (Note that I don't think this could be a MUST use ).

> 
> - I find it good that these 3 mechanisms are the only ones considered in the draft. I'm making the leap of faith that we intend to state that an implementation MUST implement DSCP code point

I have not tracked this all down but have been told that it might not be possible for a browser to do this in some versions of the windows operating system so I suspect the DSCP would end up being SHOULD not a MUST   

> m unforotanly arking, SHOULD implement QCI and WiFI markings when attached to appropriate interfaces, and that no other mechanism is going to get a MUST or SHOULD recommendation from the WG. If I'm right, can we make that explicit?
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email