[ppsp] Fw: New Version Notification for draft-ietf-ppsp-problem-statement-13.txt

zhangyunfei <zhangyunfei@chinamobile.com> Mon, 25 February 2013 02:39 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 1D51921F9191 for <ppsp@ietfa.amsl.com>; Sun, 24 Feb 2013 18:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.656
X-Spam-Level:
X-Spam-Status: No, score=-98.656 tagged_above=-999 required=5 tests=[AWL=1.720, BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_221=2.222, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3qEU7jlFT92 for <ppsp@ietfa.amsl.com>; Sun, 24 Feb 2013 18:39:57 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id F26CF21F9071 for <ppsp@ietf.org>; Sun, 24 Feb 2013 18:39:56 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.21]) by rmmx-oa_allagent01-12001 (RichMail) with SMTP id 2ee1512acee52be-772be; Mon, 25 Feb 2013 10:39:33 +0800 (CST)
X-RM-TRANSID: 2ee1512acee52be-772be
Received: from zyf-PC (unknown[10.2.43.220]) by rmsmtp-oa_rmapp03-12003 (RichMail) with SMTP id 2ee3512acee10fb-9a321; Mon, 25 Feb 2013 10:39:33 +0800 (CST)
X-RM-TRANSID: 2ee3512acee10fb-9a321
Date: Mon, 25 Feb 2013 10:39:40 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: ppsp <ppsp@ietf.org>
X-Priority: 3
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2013022510394050334718@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart637664606022_=----"
Subject: [ppsp] Fw: New Version Notification for draft-ietf-ppsp-problem-statement-13.txt
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: Mon, 25 Feb 2013 02:39:59 -0000

Hi all,
   
    A new revision of PPSP problem statement and requirement draft has been uploaded. Any review and comments are welcome.

BR
Yunfei




zhangyunfei

From: internet-drafts
Date: 2013-02-23 03:44
To: zhangyunfei
CC: zongning
Subject: New Version Notification for draft-ietf-ppsp-problem-statement-13.txt

A new version of I-D, draft-ietf-ppsp-problem-statement-13.txt
has been successfully submitted by Yunfei Zhang and posted to the
IETF repository.

Filename:  draft-ietf-ppsp-problem-statement
Revision:  13
Title:  Problem Statement and Requirements of Peer-to-Peer Streaming Protocol (PPSP)
Creation date:  2013-02-20
Group:  ppsp
Number of pages: 26
URL:             http://www.ietf.org/internet-drafts/draft-ietf-ppsp-problem-statement-13.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-ppsp-problem-statement
Htmlized:        http://tools.ietf.org/html/draft-ietf-ppsp-problem-statement-13
Diff:            http://www.ietf.org/rfcdiff?url2=draft-ietf-ppsp-problem-statement-13

Abstract:
   Peer-to-Peer(P2P for short) streaming systems show more and more
   popularity in current Internet with proprietary protocols. This
   document identifies problems of the proprietary protocols, proposes
   the development of Peer to Peer Streaming Protocol(PPSP) including
   the Tracker and Peer protocol, and discusses the scope, requirements
   and use cases of PPSP.

                                                                                  
The Meta-Data check indicates the following error:
 *Document date* None
Creation Date field is empty or the creation date is not in a proper format 

I check the draft without finding the error. So I manually update the metadata with the right creation time. Thanks for the help.



The IETF Secretariat