IETF Logo Mail Archive

Re: [httpstreaming] Current Status and Our Goal

Wenbo Zhu <wenboz@google.com> Sun, 10 October 2010 09:16 UTC

Return-Path: <wenboz@google.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 BAAAE3A67A6 for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 02:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.977
X-Spam-Level:
X-Spam-Status: No, score=-106.977 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Grt23oMpDNnS for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 02:16:11 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 6D0C43A672F for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 02:16:06 -0700 (PDT)
Received: from kpbe12.cbf.corp.google.com (kpbe12.cbf.corp.google.com [172.25.105.76]) by smtp-out.google.com with ESMTP id o9A9HEc8004112 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 02:17:14 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1286702234; bh=GzJfVVAvUFykEw/p9YeLQq6+Qmg=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=n2DnJStxCVJoi91IyhnlXyRMQfw+E5dOzI4WxH5S98euzSW+nF0xHa23/DV4i/a6C MBU8Jg9JqY525TayPR+Vg==
Received: from gwb10 (gwb10.prod.google.com [10.200.2.10]) by kpbe12.cbf.corp.google.com with ESMTP id o9A9HDhM014239 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 02:17:13 -0700
Received: by gwb10 with SMTP id 10so18924gwb.14 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 02:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=WuuSaaMWLSOE06hosb479H9lSWo+tVo1P/ZBz1u36kI=; b=BjaUWvmLOI+r6+taf+F0gJqolK+4SQxetbjZX33bn3dDRZJgAm3kSB6RToKRNN5wnd fMSRNrJKREFf8EkVTLyw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Exc6ae+bAT4MdbDHR2YdJ70a1W15dwOcvD37GzhQ/9VaspquxfeNMcdDxFVgGWEOFB nyVWx0CL76kLnUzrGG7g==
MIME-Version: 1.0
Received: by 10.90.36.6 with SMTP id j6mr2422952agj.28.1286702232787; Sun, 10 Oct 2010 02:17:12 -0700 (PDT)
Received: by 10.91.213.18 with HTTP; Sun, 10 Oct 2010 02:17:12 -0700 (PDT)
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A1@xmb-sjc-215.amer.cisco.com>
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com> <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com> <03f501cb65a1$50699d70$f13cd850$%roni@huawei.com> <B1C30D3B-6D5C-46B9-848D-3AE0C8B6058C@csperkins.org> <9690AB8A-315E-4730-ABD8-78F4BB3E4CB6@nokia.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF35F@xmb-sjc-215.amer.cisco.com> <AANLkTimc=72t59x-N+xDzL+AYc_g8Noa0=H8cHYZsrFs@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A0@xmb-sjc-215.amer.cisco.com> <AANLkTim1dPg-TtQ6Jm0y+pKdvvLbU1Xq4Q4d7w+aMeG9@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A1@xmb-sjc-215.amer.cisco.com>
Date: Sun, 10 Oct 2010 02:17:12 -0700
Message-ID: <AANLkTi=bPEOQku1bLLLEfOKb81dM3PWFeSmuURANP5sU@mail.gmail.com>
From: Wenbo Zhu <wenboz@google.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: httpstreaming@ietf.org, Colin Perkins <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 09:16:20 -0000

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.23.0 | Report a Bug | By Email