Re: [rtcweb] H.264 SVC and BUNDLE

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Thu, 30 August 2012 20:07 UTC

Return-Path: <richard.ejzak@alcatel-lucent.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 12A8C21F8497 for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 13:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.902
X-Spam-Level:
X-Spam-Status: No, score=-7.902 tagged_above=-999 required=5 tests=[AWL=-1.653, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 JcuhDiZTWiEO for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 13:07:54 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id 1B5FB21F848F for <rtcweb@ietf.org>; Thu, 30 Aug 2012 13:07:53 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q7UK7bSU008128 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rtcweb@ietf.org>; Thu, 30 Aug 2012 22:07:50 +0200
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 30 Aug 2012 22:07:47 +0200
Received: from US70UWXCHMBA04.zam.alcatel-lucent.com ([169.254.12.110]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Thu, 30 Aug 2012 16:07:44 -0400
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] H.264 SVC and BUNDLE
Thread-Index: AQHNhhfAiyhaIO3vJU6HglhL+lp/Z5dxo1QAgAEeYkA=
Date: Thu, 30 Aug 2012 20:07:40 +0000
Message-ID: <03FBA798AC24E3498B74F47FD082A92F177393B8@US70UWXCHMBA04.zam.alcatel-lucent.com>
References: <503E0B63.3020708@ericsson.com>, <E17CAD772E76C742B645BD4DC602CD8106A9810E@NAHALD.us.int.genesyslab.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F4C@ESESSCMS0356.eemea.ericsson.se> <035101cd8636$3b654160$b22fc420$@com>
In-Reply-To: <035101cd8636$3b654160$b22fc420$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
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 20:07:55 -0000

Dan Wing wrote:
> 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.

Dan,
You make a claim that is not necessarily true.  If packets within a 5-tuple have different DSCP values that are then erased by the network, why would it be "impossible" to restore those values later?  Within the context of multiplexing of RTP streams, each RTP stream within a 5-tuple would of necessity need to still use a single DSCP value.  If signaling can be used to inform a node of some means of identifying each RTP stream then the original DSCP markings could be restored.

While I agree that it would be easier to assign the same DSCP value to all packets in a 5-tuple, it would still be "possible" to filter on, for example, the SSRC value used for each stream (in addition to the 5-tuple) to reassign the original DSCP value (or a mapped value with appropriate meaning in the target network) for each stream.

Richard