[ppsp] Rough time plan for the leaving work in PPSP WG
"yunfei" <hishigh@sina.com> Fri, 14 November 2014 00:22 UTC
Return-Path: <hishigh@sina.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B88061A00B0 for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 16:22:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHdD9VEKoxNB for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 16:22:16 -0800 (PST)
Received: from smtp2911-211.mail.sina.com.cn (mail2-189.sinamail.sina.com.cn [60.28.2.189]) by ietfa.amsl.com (Postfix) with SMTP id BE90E1A006F for <ppsp@ietf.org>; Thu, 13 Nov 2014 16:22:14 -0800 (PST)
Received: from unknown( HELO webmail.sinamail.sina.com.cn)([172.16.201.96]) by sina.com with SMTP 14 Nov 2014 08:22:11 +0800 (CST)
X-Sender: hishigh@sina.com
X-SMAIL-MID: 6432479061657
Received: by webmail.sinamail.sina.com.cn (Postfix, from userid 80) id D4B495605AD; Fri, 14 Nov 2014 08:22:10 +0800 (CST)
Date: Fri, 14 Nov 2014 08:22:10 +0800
Received: from hishigh@sina.com([31.133.163.59]) by m0.mail.sina.com.cn via HTTP; Fri, 14 Nov 2014 08:22:10 +0800 (CST)
From: yunfei <hishigh@sina.com>
To: ppsp <ppsp@ietf.org>
MIME-Version: 1.0
X-Priority: 3
X-MessageID: 54654b3220863b96
X-Originating-IP: [172.16.201.96]
X-Mailer: Sina WebMail 4.0
Content-Type: multipart/alternative; boundary="=-sinamail_alt_f23fbf7b772b2199be4c652ec73020b9"
Message-Id: <20141114002210.D4B495605AD@webmail.sinamail.sina.com.cn>
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/a7wJR5uK2prCBI9R3BNtWi7045k
Cc: "spencerdawkins.ietf" <spencerdawkins.ietf@gmail.com>
Subject: [ppsp] Rough time plan for the leaving work in PPSP WG
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: hishigh@sina.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: Fri, 14 Nov 2014 00:22:21 -0000
Hi guys,
First of all, Ning and I would express our best appreciation on your contributions to PPSP WG. As Martin mentioned, we need to hurry up our delivables under discussion. Here is our rough time plan for the WG before next Feb:
1. Base tracker protocol:
Discussion(onging): This week and next week.
WG decision on the encoding: By the end of next week.
Revised I-D Ready: Early of Dec.
WG Last Call: Early of Dec.
2. Extend tracker protocol:
Review: We talked with the authors and they see value in continuing documenting this extended tracker protocol. So shall I request the experts in the WG to actively review this document NOW and feedback in the mailing list before end of Dec? It is VERY important to show the energy of working on the draft.
Call for adoption: Based on review result, the WG decides if we should call for adoption on this document in the end of Dec. Review will be the pre-condition of the call.
Revised I-D Ready: If adopted as WG draft, revised draft addressing ALL review comments received should be ready before end of Jan, 2015.
3. Usage guide:
There is an individual draft (draft-zhang-ppsp-usage-01) that could be the basis for this work item. Same as extended tracker protocol, please review it NOW and the WG will call for adoption accordingly.
Review: Before end of Dec.
Call for adoption: end of Dec.
Revised I-D Ready: If adopted as WG draft, revised draft addressing ALL review comments received should be ready before mid of Feb, 2015.
We plan to have one/two online techincial discussions within this process and finalize to solve all the techincal issues before end of Feb, 2015. Please let us know if you have any comments and suggestion. Thanks.
BR
Ning and Yunfei