Re: [AVT] Pointer for the IETF-for-pro-production folks ...
Ross Finlayson <finlayson@live555.com> Fri, 14 April 2006 21:18 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUVg2-0001q4-UO; Fri, 14 Apr 2006 17:18:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUVg0-0001pz-26 for avt@ietf.org; Fri, 14 Apr 2006 17:18:00 -0400
Received: from ns.live555.com ([66.80.62.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUVfu-00012r-MZ for avt@ietf.org; Fri, 14 Apr 2006 17:17:56 -0400
Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.13.4/8.13.4) with ESMTP id k3ELHrd8025437 for <avt@ietf.org>; Fri, 14 Apr 2006 14:17:53 -0700 (PDT) (envelope-from rsf@ns.live555.com)
Received: (from rsf@localhost) by ns.live555.com (8.13.4/8.13.4/Submit) id k3ELHrjo025432; Fri, 14 Apr 2006 14:17:53 -0700 (PDT) (envelope-from rsf)
Message-Id: <7.0.1.0.1.20060414140539.01e6f2d8@live555.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Fri, 14 Apr 2006 14:17:48 -0700
To: avt@ietf.org
From: Ross Finlayson <finlayson@live555.com>
Subject: Re: [AVT] Pointer for the IETF-for-pro-production folks ...
In-Reply-To: <3DAB34A0-7C0E-4774-B73B-B76E550F30DF@eecs.berkeley.edu>
References: <3DAB34A0-7C0E-4774-B73B-B76E550F30DF@eecs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
> By and large, store-and-forward media flows
>are going over IP, but real-time media flows use
>mostly circuit-switched standards
The unmentioned - but significant - big question here, however, is:
Just how important will "real-time media flows" be for 'television'
in the future? More and more people these days are watching
television shows 'on demand', using DVRs, or downloaded off the
Internet. (Personally, almost all of the 'television' that I watch
these days is shows downloaded via bittorrent.) If this trend
continues - and there's every sign that it will - then what will be
the best way to design a television nework when live viewing becomes
the exception (e.g., major sporting events like the Superbowl or
World Cup final) rather than the rule?
Ross.
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt