Re: [ppsp] Progress on core tracker protocol?

zhangyunfei <zhangyunfei@chinamobile.com> Thu, 28 June 2012 01:46 UTC

Return-Path: <zhangyunfei@chinamobile.com>
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 06E4711E8176 for <ppsp@ietfa.amsl.com>; Wed, 27 Jun 2012 18:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.188
X-Spam-Level:
X-Spam-Status: No, score=-98.188 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, USER_IN_WHITELIST=-100]
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 eU99DDfep1NU for <ppsp@ietfa.amsl.com>; Wed, 27 Jun 2012 18:46:56 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3D78411E8173 for <ppsp@ietf.org>; Wed, 27 Jun 2012 18:46:56 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 96C84E6D3; Thu, 28 Jun 2012 09:46:52 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 89784E6B6; Thu, 28 Jun 2012 09:46:52 +0800 (CST)
Received: from zyf-PC ([10.2.43.220]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012062809465011-2731 ; Thu, 28 Jun 2012 09:46:50 +0800
Date: Thu, 28 Jun 2012 09:46:39 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: Rui Cruz <rui.cruz@ieee-pt.org>, Johan Pouwelse <peer2peer@gmail.com>
References: <CAJYQ-fQbj9WjSt8JTQdiULuaJu4LGbB9ErmrA_C2JN3Fjq6HQg@mail.gmail.com>, <EDCDAC3A-EE05-417B-BEA0-0A881AE9D055@ieee-pt.org>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2012062809463963273025@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-06-28 09:46:50, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-06-28 09:46:52, Serialize complete at 2012-06-28 09:46:52
Content-Type: multipart/alternative; boundary="----=_001_NextPart023312545132_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-19002.003
X-TM-AS-Result: No--49.684-7.0-31-10
X-imss-scan-details: No--49.684-7.0-31-10;No--49.684-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Cc: 'Rui Cruz' <rui.cruz@ieee.org>, ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] Progress on core tracker protocol?
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: zhangyunfei <zhangyunfei@chinamobile.com>
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: Thu, 28 Jun 2012 01:46:58 -0000

Thank Rui for the information. 
P.S.: For the WG, Arno has published a new version of the peer protocol. Please review it and publish your comments. Thanks.

BR
Yunfei




zhangyunfei

From: Rui Cruz
Date: 2012-06-28 00:41
To: Johan Pouwelse
CC: Rui Cruz; ppsp
Subject: Re: [ppsp] Progress on core tracker protocol?
The PPSP-TP base Tracker Protocol draft will be published before the end of June.
It does essentially what we had discussed during IETF 83.
The PPSP-TP Extended Tracker Protocol will bring all those more sophisticated features, and will be published afterwards (during July)


Cumprimentos/Regards,
Rui Cruz


Sent from my iPad2

On 27/06/2012, at 16:52, Johan Pouwelse <peer2peer@gmail.com> wrote:


There was agreement for the need to create a core tracker protocol. Any progress to report, since last month?
What do you think of my proposal below for the focus of this really-limited-to-the-core protocol?




This document specifies the Peer-to-Peer Streaming Protocol--Core Tracker Protocol (PPSP-CTP), an application-layer control protocol for facilitating Peer-2-Peer streaming. This core protocol is limited to a peer discovery request message and reply message.
The PPSP-CTP protocol is limited to the GET-PEERS message and subsequent reply with a peer list. This core protocol is the only requirement for a simple streaming service, along with the PPSP peer protocol. We refer to an upcoming Extended Tracker Protocol for more sophisticated features. For instance,  the exchange of meta information, content information, statistics reporting, etc.




 -johan.
On Tuesday, June 5, 2012, Rui Cruz wrote:

Hi,


The Tracker Protocol is  being split to a base specification draft and to extensions.
We hope to have the base specification submitted in a couple of weeks. 



Regards,


Rui Cruz
rui.cruz@ieee.org


IST/INESC-ID/INOV - Lisbon, Portugal
__________________________________________
ppsp mailing list
ppsp@ietf.org
https://www.ietf.org/mailman/listinfo/ppsp


On 04/06/2012, at 10:39, stefano previdi wrote:


All,

here are some notes i preparation of the next PPSP meeting we're 
going to have in Vancouver (http://www.ietf.org/meeting/84/index.html)

1. Peer Protocol - chunk addressing mechanism
  We currently have two proposals that I'd try to name as:
. Bin Notation
. Ranges
  Both proposals have been discussed in the mailing list and it 
  looks to me we're NOT achieving agreement/consensus on any of 
  them also due to lack of participation of the WG into the 
  discussion (other than the authors of each proposal).

  Therefore, as of today, we can reasonably explore the 
  following options:
  Option-1: We propose both solutions in the peer protocol 
            specification and we define them both MANDATORY so 
            to cope with interoperability issues.
  Option-2: we select one option through a WG vote (this is my 
            least preferred option).

  Since I'd really prefer to avoid Option-2, I can only consider 
  the "dual" specification. WG opinion on this is requested.

  Again, it would be very beneficial to the WG if current 
  implementors of streaming protocols would/could speak-up and 
  give their opinion (see point 4 below).

2. Peer Protocol - Security Section
  The IESG will not accept any protocol specification without a 
  consistent security section (IOW: way more than what we 
  currently have) although there are some arguments on whether 
  we need the security mechanisms in the base spec.

  Arno and Zong Ning proposed some text and we need to agree/amend 
  it asap so to update the draft. I'd like to close this one and 
  have a new version of the draft for next meeting.

3. Tracker Protocol
  After IETF83 we agreed to split into two distinct drafts: base 
  specification and optional extensions.

  Authors, it would be good to have a first submission before next 
  meeting.

4. Survey draft.
  We need to refresh/re-submit and the chairs proposed the 
  authors/editors to include a section on deployment experiences 
  and more precisely on chunk addressing and security mechanisms. 
  Hopefully this will also feed ongoing discussions.

5. Meeting during IETF84.
  We have requested a slot for Vancouver meeting. Anyone 
  interested, please request an agenda slot asap to Yunfei or 
  myself.

Let us know if anything is missing.

Thanks.

Stefano & Yunfei
_______________________________________________
ppsp mailing list
ppsp@ietf.org
https://www.ietf.org/mailman/listinfo/ppsp



_______________________________________________
ppsp mailing list
ppsp@ietf.org
https://www.ietf.org/mailman/listinfo/ppsp