IETF Logo Mail Archive

Re: [httpstreaming] Current Status and Our Goal

"Ali C. Begen (abegen)" <abegen@cisco.com> Sun, 10 October 2010 10:08 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: httpstreaming@core3.amsl.com
Delivered-To: httpstreaming@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEA3F3A67A8 for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 03:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.558
X-Spam-Level:
X-Spam-Status: No, score=-10.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGHnfXsAOMii for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 03:07:59 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A67C03A67A6 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 03:07:59 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYGAF8tsUyrR7Ht/2dsb2JhbACULo17cZwUm16FSASEUoh4
X-IronPort-AV: E=Sophos;i="4.57,309,1283731200"; d="scan'208";a="198444639"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 10 Oct 2010 10:09:08 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9AA981D022781; Sun, 10 Oct 2010 10:09:08 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 10 Oct 2010 03:09:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 10 Oct 2010 03:09:06 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540B8AA1B6@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <AANLkTi=bPEOQku1bLLLEfOKb81dM3PWFeSmuURANP5sU@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [httpstreaming] Current Status and Our Goal
Thread-Index: ActoW/5eVCCpdWQORpSYHdqRytvleQABy3d+
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <wenboz@google.com>
X-OriginalArrivalTime: 10 Oct 2010 10:09:08.0003 (UTC) FILETIME=[2D3A2F30:01CB6863]
Cc: httpstreaming@ietf.org, csp@csperkins.org
Subject: Re: [httpstreaming] Current Status and Our Goal
X-BeenThere: httpstreaming@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network based HTTP Streaming discussion list <httpstreaming.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/httpstreaming>
List-Post: <mailto:httpstreaming@ietf.org>
List-Help: <mailto:httpstreaming-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Oct 2010 10:08:01 -0000

But then that is not a proxy anymore. You probably do not wanna replace all those proxies or introduce new ones with heavier tasks.  

-acbegen

----- Original Message -----
From: Wenbo Zhu [mailto:wenboz@google.com]
Sent: Sunday, October 10, 2010 02:17 AM
To: Ali C. Begen (abegen)
Cc: Lars Eggert <lars.eggert@nokia.com>om>; Colin Perkins <csp@csperkins.org>rg>; httpstreaming@ietf.org <httpstreaming@ietf.org>
Subject: Re: [httpstreaming] Current Status and Our Goal

On Sun, Oct 10, 2010 at 12:45 AM, Ali C. Begen (abegen)
<abegen@cisco.com> wrote:
>> > Wanna give a specific example for "intermediaries"? I think you are referring to something besides the http caches.
>> proxies.
>
> What should a proxy support for streaming?
Proxies don't know anything about streaming, and they only understand
HTTP. If the goal is to optimize the transport, then clearly defined
protocol semantics would be necessary for proxies to distinguish
streaming traffic from regular HTTP traffic.

>
>> >
>> >> to offer direct support for streaming traffic, and different client
>> >> platforms will also be able to improve end-user experience
>> >> independently of vendor or media-protocol specific solutions.
>> >
>> > Sure but is not that all client implementation, which is mostly left for product differentiation?
>> I am interested to find out whether existing implementations (that
>> have successfully deployed HTTP-based streaming over internet) expose
>> streaming resource via open protocols or API's?
>
> There are source codes floating around (with different licenses of course). Have you looked at OSMF and OVP?
> http://openvideoplayer.sourceforge.net/
> http://opensource.adobe.com/wiki/display/osmf/Open+Source+Media+Framework
Thanks for the info.

- Wenbo

>
> -acbegen
>
>

v2.8.7 | Report a Bug | By Email