Re: [Dart] I-D Action: draft-york-dart-dscp-rtp-00.txt

"Paul E. Jones" <paulej@packetizer.com> Sun, 15 June 2014 04:04 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: dart@ietfa.amsl.com
Delivered-To: dart@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6C51B29D1 for <dart@ietfa.amsl.com>; Sat, 14 Jun 2014 21:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.653
X-Spam-Level:
X-Spam-Status: No, score=-2.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SYhFo92m5oM for <dart@ietfa.amsl.com>; Sat, 14 Jun 2014 21:04:56 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDCD91B2889 for <dart@ietf.org>; Sat, 14 Jun 2014 21:04:55 -0700 (PDT)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s5F44etI012586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 15 Jun 2014 00:04:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1402805092; bh=QpCwlETiDnUrT8hXmyif3Wa+5DgQaNe6BhVQXhnEGZ4=; h=From:To:Subject:Date:Content-Transfer-Encoding:Content-Type: In-Reply-To:Message-Id:Mime-Version:Reply-To; b=a/pPLNS6jpLsUJveP+qw7LqFHgbLq/YzB9/mWOVToPVTdpel4xOpsjskeB/8d6Lh2 KUDmSFJfzoeXqFiaGglHtnugYZ+ZLQAblRtbEcY6NZoWqP15VXsMOphiySU0I4j0WS 9Z+8hlGO8u5m3jEhUwKwteROYiup6Q870/QgkacQ=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Harald Alvestrand" <harald@alvestrand.no>, dart@ietf.org
Date: Sun, 15 Jun 2014 04:04:52 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <539838DF.8010506@alvestrand.no>
Message-Id: <emb32d8c69-c6a3-4b57-889b-ea36fe70b3be@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.20154.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/bHi5-5ra_UkpO7y0Aa0DP1wgX3o
Subject: Re: [Dart] I-D Action: draft-york-dart-dscp-rtp-00.txt
X-BeenThere: dart@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <dart.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dart>, <mailto:dart-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dart/>
List-Post: <mailto:dart@ietf.org>
List-Help: <mailto:dart-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dart>, <mailto:dart-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jun 2014 04:04:58 -0000


------ Original Message ------
From: "Harald Alvestrand" <harald@alvestrand.no>
To: dart@ietf.org
Sent: 6/11/2014 7:09:19 AM
Subject: Re: [Dart] I-D Action: draft-york-dart-dscp-rtp-00.txt

>On 06/10/2014 09:44 PM, Black, David wrote:
>>
>>Could you suggest a reference that could be cited for usage of an RTP
>>packet stream for each MediaStream independent of how many
>>MediaStreamTracks each MediaStream contains?
>
>Careful - "RTP packet stream" is one of those concepts that can be 
>meaningless without citing a specific definition.
>
>draft-ietf-avtext-rtp-grouping-taxonomy is probably the best reference 
>at the moment. It says this about "Packet stream":
>

Indeed.  I threw my two cents in on the word "Packet Stream". I spoke 
with (at least some of) the authors asking them to call this "RTP Packet 
Stream" or to pick something entirely different.  Between "packet 
stream" and "MediaStream" and "Media Stream" (yeah, those are different, 
too), the language makes it hard to follow.


>
>The term "media flow" doesn't sound to me like a good term to use for 
>this concept.
>Would the authors be willing to consider switching to "packet stream"?
>

I don't have a strong preference, except that I'd prefer to qualify that 
as "RTP Packet Stream".

Paul