Re: [rtcweb] DSCP and media

Justin Uberti <juberti@google.com> Wed, 20 July 2011 21:10 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 ACB3D21F8A6F for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 14:10:11 -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 hsNT8ECdc7jK for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 14:10:07 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEA621F8A64 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 14:10:07 -0700 (PDT)
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82]) by smtp-out.google.com with ESMTP id p6KL9tP2024600 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 14:09:55 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311196196; bh=kRLtt02+DrLbwzYtF78owYPui7Y=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=cndNIiB7QDQs/1zWkEXwyklOzyMlByP7/HOOQMpmJ0OIM83gogTjvP5ptwxby8/fY emb4XOz9WihJ4iNRg0Y/g==
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=o0XW7Ff05dYPt5PEZAJBXj1w+70GjmdLT+M3vanjg+0HHEywnRqTwONKcu7L/Zd9F EOSDuuENzgLdBgwb+Jd6A==
Received: from qwi4 (qwi4.prod.google.com [10.241.195.4]) by kpbe18.cbf.corp.google.com with ESMTP id p6KL9XcA016858 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rtcweb@ietf.org>; Wed, 20 Jul 2011 14:09:54 -0700
Received: by qwi4 with SMTP id 4so366963qwi.29 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 14:09:54 -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=zTYTmT1TK8CeJTCGaQfZ3F6x7Ygqj7k+MQsrfJZA2gg=; b=Z5gvdB1nQFWzR2fN+Qqkup4UMqbKJiaATea9gYAPfr+v0HNfVgXzXp3ElRKlqSkH7u Pe8gUEf+AbwSNe2J6zEw==
Received: by 10.229.77.38 with SMTP id e38mr5745841qck.151.1311196194168; Wed, 20 Jul 2011 14:09:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.137.81 with HTTP; Wed, 20 Jul 2011 14:09:34 -0700 (PDT)
In-Reply-To: <BLU152-W2571B444617CB2FA03DE25934C0@phx.gbl>
References: <E4572FE5-EC81-48A9-9FCD-0F1AB8465B2B@cisco.com> <CAOJ7v-0yTzNMee2Zi3QtPknvS4f4jS6D2dNMoHit39rFCD82Zw@mail.gmail.com> <BLU152-W2571B444617CB2FA03DE25934C0@phx.gbl>
From: Justin Uberti <juberti@google.com>
Date: Wed, 20 Jul 2011 17:09:34 -0400
Message-ID: <CAOJ7v-2V72vtjvaUTJK_JpLY+niTCHZNiX915ZVWttqTgULd_Q@mail.gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary="00235447193c625e9d04a886a7b2"
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 21:10:11 -0000

OK, that's what I suspected.

Ensuring that this is handled properly by the RTCWEB platform can only help
things.

On Wed, Jul 20, 2011 at 4:43 PM, Bernard Aboba <bernard_aboba@hotmail.com>wrote:

>  I think we're talking about things like support of WFA WMM.  Not a NAT
> function per se.
>
> Some info on how this is implemented in the OS is available here<http://blogs.msdn.com/b/wndp/archive/2006/06/28/650363.aspx>.
>
>
> Whether this actually accomplishes anything in practice is a subject of
> debate<http://www.smallnetbuilder.com/wireless/wireless-features/30837-does-wi-fi-multimedia-wmm-really-do-anything-part-3?start=1>.
>
>
> ------------------------------
> From: juberti@google.com
> Date: Wed, 20 Jul 2011 15:39:04 -0400
> To: fluffy@cisco.com
> CC: rtcweb@ietf.org
> Subject: Re: [rtcweb] DSCP and media
>
>
> 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
>
>
>
> _______________________________________________ rtcweb mailing list
> rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
>