IETF Logo Mail Archive

Re: [rtcweb] DSCP and media

Justin Uberti <juberti@google.com> Wed, 20 July 2011 19:39 UTC

Return-Path: <juberti@google.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 9D8C121F8AD6 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 12:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 tRbd4pWIf+W2 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 12:39:26 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0B31321F8ACC for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:39:25 -0700 (PDT)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id p6KJdPfq013993 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:39:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311190765; bh=dp2Ondibz6qGFEnHDoLr+KJFQ6w=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=bAvIcktOkTL1MhhYxASqSEIk/dxYiTO2Dcop7+LwNftbkjCih9thg/JSh+0cASCLD /DYFXAyF3D7aBtM7yWIxg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=rgRFqk1acukUy4QrgeVKx+gn9a2Rn2rmFRak2rf5FmLWzWvCn28megOh5XLLpuoYi Vp5AV30QMcUFC0z+W9dpg==
Received: from qyk30 (qyk30.prod.google.com [10.241.83.158]) by wpaz37.hot.corp.google.com with ESMTP id p6KJc2p4010268 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:39:24 -0700
Received: by qyk30 with SMTP id 30so3346018qyk.13 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:39:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UpMfwbq5GqV0vNwBiPrdD1lx7baXgu4z8/TYNDyWO1U=; b=LT/d9dfxR0ODNyZAzlaV4KQkVz3NVL/it3gHvcfyFMNtrp68T2p91qx4pFNXi6B21T yz/cWb6qGCjBe1UHRQRQ==
Received: by 10.229.77.38 with SMTP id e38mr5665109qck.151.1311190764146; Wed, 20 Jul 2011 12:39:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.137.81 with HTTP; Wed, 20 Jul 2011 12:39:04 -0700 (PDT)
In-Reply-To: <E4572FE5-EC81-48A9-9FCD-0F1AB8465B2B@cisco.com>
References: <E4572FE5-EC81-48A9-9FCD-0F1AB8465B2B@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 20 Jul 2011 15:39:04 -0400
Message-ID: <CAOJ7v-0yTzNMee2Zi3QtPknvS4f4jS6D2dNMoHit39rFCD82Zw@mail.gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="00235447193cbacfd004a885633a"
X-System-Of-Record: true
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] DSCP and media
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: Wed, 20 Jul 2011 19:39:26 -0000

Can you go into more detail about what these NATs do with the DSCP markings?

I'm not convinced we want to expose a generic API for this (too easy to
misuse), but I think it definitely makes sense for implementations to set
appropriate markings on audio and video packets, including different levels
on individual video packets when using hierarchical prediction structures.

On Wed, Jul 20, 2011 at 1:59 PM, Cullen Jennings <fluffy@cisco.com> wrote:

>
> Many home NATs support DSCP based QoS and it does help. I think that the
> IETF should recommend that some default DSCP for audio and video from the
> browser as well as suggest there should be an API to set the DSCP for
> different media steam.
>
> Cullen <with my individual contributor hat on>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email