IETF Logo Mail Archive

Re: [rtcweb] H.264 SVC and BUNDLE

"Dan Wing" <dwing@cisco.com> Thu, 30 August 2012 15:28 UTC

Return-Path: <dwing@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 DF8CE21F858A for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 08:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.5
X-Spam-Level:
X-Spam-Status: No, score=-110.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 TScxLxn9lFF1 for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 08:28:58 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 3030521F8567 for <rtcweb@ietf.org>; Thu, 30 Aug 2012 08:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2333; q=dns/txt; s=iport; t=1346340538; x=1347550138; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=ZHkbAkGU/uxKTTyImXorl7BBuSRDMsBLihy2cYVDyHg=; b=gvHL17jiHFTNX80zANIMEKoiynMmZUjdZ2IGtv0+crnZkS8QH9rj4Nal CyM02xjRiUT1LuI/n4vnavopxwk3K1mRAvCJgRRkSHAa4lvPCD23v2vjU toU9yoICdCsDkTGcvlCrWmJAc51cA3XGpRjM6K+w0haK0NZxzSFo5EUSn M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGuGP1CrRDoH/2dsb2JhbABFqxGPdIEHgiABAQEDAQEBAQUKARcQNBAHAQMCCQ8CBAEBKAcZDhUKCQgCBAESCxeHZQUMnDmgEwSLCIZZA4hPhQ2WLYFngwM
X-IronPort-AV: E=Sophos;i="4.80,341,1344211200"; d="scan'208";a="54183325"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 30 Aug 2012 15:28:57 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q7UFSvQ8016351; Thu, 30 Aug 2012 15:28:57 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, public-webrtc@w3.org, rtcweb@ietf.org
References: <503E0B63.3020708@ericsson.com>, <E17CAD772E76C742B645BD4DC602CD8106A9810E@NAHALD.us.int.genesyslab.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F4C@ESESSCMS0356.eemea.ericsson.se>, <035101cd8636$3b654160$b22fc420$@com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F5C@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05853409FF2F5C@ESESSCMS0356.eemea.ericsson.se>
Date: Thu, 30 Aug 2012 08:28:57 -0700
Message-ID: <04c101cd86c4$2c48c150$84da43f0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHNhhenMhkLi/vCmkGQ1yfqZgaa8pdxXxawgACdAheAAH/40A==
Content-Language: en-us
Subject: Re: [rtcweb] H.264 SVC and BUNDLE
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: Thu, 30 Aug 2012 15:28:59 -0000

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Thursday, August 30, 2012 12:51 AM
> To: Dan Wing; public-webrtc@w3.org; rtcweb@ietf.org
> Subject: RE: [rtcweb] H.264 SVC and BUNDLE
> 
> 
> Hi Dan,
> 
> Thanks for the information!
> 
> The issue you raise is of course not related to BUNDLE, but to
> multiplexing in general.

Yes, of course.  That's why I answered in-line, after your question
about general multiplexing.

-d


> Regards,
> 
> Christer
> ________________________________________
> From: Dan Wing [dwing@cisco.com]
> Sent: Thursday, August 30, 2012 1:32 AM
> To: Christer Holmberg; public-webrtc@w3.org; rtcweb@ietf.org
> Subject: RE: [rtcweb] H.264 SVC and BUNDLE
> 
> > -----Original Message-----
> > From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> > Behalf Of Christer Holmberg
> > Sent: Wednesday, August 29, 2012 11:50 AM
> > To: public-webrtc@w3.org; rtcweb@ietf.org
> > Subject: [rtcweb] H.264 SVC and BUNDLE
> >
> > Hi,
> >
> > At the telco yesterday one of the Microsoft guys claimed that H.264
> SVC
> > does not work with BUNDLE, but he didn't have the details.
> >
> > Could someone please explain the reason why he/she doesn't think
> H.264
> > SVC work with BUNDLE?
> >
> > (Note, that if using the same port for the different codec layers is
> a
> > problem, then it's not a BUNDLE problem - it's a generic multiplexing
> > problem.)
> 
> The general multiplexing of layers onto the same 5-tuple is a problem,
> *if* we want the layers to have different DSCP values.  This is because
> we cannot successfully and reliably set different DSCP values for
> packets
> belonging to a 5-tuple over the Internet -- too many things rewrite
> the DSCP field (to a different value) or simply clear the DSCP field.
> This makes it impossible to restore the per-packet DSCP values later
> (e.g., using RSVP, or using any other better/stronger/faster signaling
> method).  If, however, each 5-tuple has its own DSCP value then that
> DSCP value could be restored.
> 
> -d
> 
> > Thanks!
> >
> > Regards,
> >
> > Christer
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email