Re: [ppsp] PPSP Re-charter discussion
Arno Bakker <arno@cs.vu.nl> Wed, 22 February 2012 14:55 UTC
Return-Path: <a.bakker@vu.nl>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F86521F87BA for <ppsp@ietfa.amsl.com>; Wed, 22 Feb 2012 06:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.439
X-Spam-Level:
X-Spam-Status: No, score=0.439 tagged_above=-999 required=5 tests=[AWL=-0.916, BAYES_20=-0.74, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YR7+FT4yf4M8 for <ppsp@ietfa.amsl.com>; Wed, 22 Feb 2012 06:55:50 -0800 (PST)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.18]) by ietfa.amsl.com (Postfix) with ESMTP id 88FE921F87B9 for <ppsp@ietf.org>; Wed, 22 Feb 2012 06:55:50 -0800 (PST)
Received: from PEXHB012B.vu.local (130.37.236.67) by mailin.vu.nl (130.37.164.18) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 22 Feb 2012 15:55:47 +0100
Received: from [130.161.211.249] (130.37.238.20) by mails.vu.nl (130.37.236.67) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 22 Feb 2012 15:55:48 +0100
Message-ID: <4F4501F4.80704@cs.vu.nl>
Date: Wed, 22 Feb 2012 15:55:48 +0100
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: zhangyunfei <zhangyunfei@chinamobile.com>
References: <2012021923584463860669@chinamobile.com>, <4F420CA8.8090701@cs.vu.nl> <2012022211013534382619@chinamobile.com>
In-Reply-To: <2012022211013534382619@chinamobile.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] PPSP Re-charter discussion
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2012 14:55:51 -0000
On 22/02/2012 04:15, zhangyunfei wrote:
> The picture I imagine is that we have a mandatory media transport
> mechanim in PPSP. I don't mean to design
> a new protocol parallel to UDP or TCP. Rather the spec should make it
> clear how to use UDP or TCP in PPSP environment. Maybe it also
> involves some extensions above UDP or TCP.
Hi
what is the reason for describing media transport in a separate
specification and not keeping it in the peer protocol spec where it is
now (Section 6. Transport Protocols and Encapsulation)?
I'm afraid the PPSP specification will be fragmented over too many
documents: 3 specs for the P2P part (peer proto spec, media transport
spec and usage guide). Not nice for reading, not nice for authoring.
Regards,
Arno
- [ppsp] PPSP Re-charter discussion zhangyunfei
- [ppsp] Planning of a virtual interim meeting for … zhangyunfei
- Re: [ppsp] PPSP Re-charter discussion Arno Bakker
- Re: [ppsp] PPSP Re-charter discussion ZongNing
- Re: [ppsp] PPSP Re-charter discussion Riccardo Bernardini
- Re: [ppsp] PPSP Re-charter discussion zhangyunfei
- Re: [ppsp] PPSP Re-charter discussion zhangyunfei
- Re: [ppsp] PPSP Re-charter discussion zhangyunfei
- Re: [ppsp] PPSP Re-charter discussion Arno Bakker
- Re: [ppsp] PPSP Re-charter discussion Wesley Eddy