From nobody Sun Jan 3 00:29:35 2016 Return-Path: X-Original-To: ppsp@ietf.org Delivered-To: ppsp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 552161A870B; Wed, 30 Dec 2015 23:08:44 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.11.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20151231070844.6843.53739.idtracker@ietfa.amsl.com> Date: Wed, 30 Dec 2015 23:08:44 -0800 Archived-At: X-Mailman-Approved-At: Sun, 03 Jan 2016 00:29:34 -0800 Cc: ppsp@ietf.org Subject: [ppsp] I-D Action: draft-ietf-ppsp-base-tracker-protocol-12.txt X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2015 07:08:44 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Peer to Peer Streaming Protocol Working Group of the IETF. Title : PPSP Tracker Protocol-Base Protocol (PPSP-TP/1.0) Authors : Rui Santos Cruz Mario Serafim Nunes Gu Yingjie Jinwei Xia Rachel Huang Joao P. Taveira Deng Lingli Filename : draft-ietf-ppsp-base-tracker-protocol-12.txt Pages : 54 Date : 2015-12-30 Abstract: This document specifies the base Peer-to-Peer Streaming Protocol- Tracker Protocol (PPSP-TP/1.0), an application-layer control (signaling) protocol for the exchange of meta information between trackers and peers. The specification outlines the architecture of the protocol and its functionality, and describes message flows, message processing instructions, message formats, formal syntax and semantics. The PPSP Tracker Protocol enables cooperating peers to form content streaming overlay networks to support near real-time Structured Media content delivery (audio, video, associated timed text and metadata), such as adaptive multi-rate, layered (scalable) and multi-view (3D) videos, in live, time-shifted and on-demand modes. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ppsp-base-tracker-protocol/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ppsp-base-tracker-protocol-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ppsp-base-tracker-protocol-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jan 7 00:33:34 2016 Return-Path: X-Original-To: ppsp@ietf.org Delivered-To: ppsp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3D51A87BE; Thu, 7 Jan 2016 00:33:32 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Barry Leiba" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.11.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160107083332.9514.8387.idtracker@ietfa.amsl.com> Date: Thu, 07 Jan 2016 00:33:32 -0800 Archived-At: Cc: ppsp-chairs@ietf.org, ppsp@ietf.org, draft-ietf-ppsp-base-tracker-protocol@ietf.org Subject: [ppsp] Barry Leiba's No Objection on draft-ietf-ppsp-base-tracker-protocol-12: (with COMMENT) X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 08:33:32 -0000 Barry Leiba has entered the following ballot position for draft-ietf-ppsp-base-tracker-protocol-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-ppsp-base-tracker-protocol/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Version -12 addresses my DISCUSS points and almost all of my comments. Thanks very much for the work on this. Two non-critical things remain, if you don't mind another minor update: In Section 4, I would prefer that you add the section reference for Content-Type, like this: OLD the Content-Type field in HTTP/1.1 [RFC7231], NEW the Content-Type field in HTTP/1.1 (Section 3.1.1.5 of [RFC7231]), END But that's not critical, and the HTTP references are OK now. I also still prefer that you change the title of Section 8.1 to "Media Type Registration" ... but also not critical. From nobody Sun Jan 10 14:13:08 2016 Return-Path: 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 3F58C1A040C; Sun, 10 Jan 2016 14:13:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.602 X-Spam-Level: X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 iQpSFuJ8oAZi; Sun, 10 Jan 2016 14:13:05 -0800 (PST) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29D6F1A0430; Sun, 10 Jan 2016 14:13:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C2CB5BE3E; Sun, 10 Jan 2016 22:13:03 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPrfIlVrsf-u; Sun, 10 Jan 2016 22:13:02 +0000 (GMT) Received: from [10.87.48.91] (unknown [86.46.21.60]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5BE53BE39; Sun, 10 Jan 2016 22:13:01 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1452463982; bh=mOw6cJWLtvLJIwLhEbz+rnSMJxGW8xVhmdY51lgtBXk=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=06VTxFmNMT4QgDQP9zTpBQaWL0+GMS9tOL85G3EsYk0jQta/SVfIMMt7hWrWvqA/l SVG5BuYFSabnSlXWj+0gAGQDk9TWQeAF+8gFZ+FJetF9vDND5ab90021qk5qJuY1ky fxElB3aX1QeQ4oYlS2yVEMZizgA0s9L4ftk51ZIg= To: "Huangyihong (Rachel)" , The IESG References: <20151014192642.8481.70035.idtracker@ietfa.amsl.com> <51E6A56BD6A85142B9D172C87FC3ABBB864448AA@nkgeml501-mbs.china.huawei.com> From: Stephen Farrell Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url= Message-ID: <5692D76C.6010108@cs.tcd.ie> Date: Sun, 10 Jan 2016 22:13:00 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB864448AA@nkgeml501-mbs.china.huawei.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: "ppsp-chairs@ietf.org" , "ppsp@ietf.org" , "draft-ietf-ppsp-base-tracker-protocol@ietf.org" Subject: Re: [ppsp] Stephen Farrell's Discuss on draft-ietf-ppsp-base-tracker-protocol-10: (with DISCUSS and COMMENT) X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 22:13:07 -0000 Hi, Sorry for my extremely slow response, but given that you've gotten the other discusses cleared and I've not found time to delve into this more myself, I've cleared my discuss on the basis of your explanation below. Thanks, S. On 22/10/15 08:09, Huangyihong (Rachel) wrote: > Hi Stephen, > > Thank you for your comments and sorry for our late replies. Please see inline. > > BR, > Rachel > >> -----Original Message----- >> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie] >> Sent: Thursday, October 15, 2015 3:27 AM >> To: The IESG >> Cc: ppsp-chairs@ietf.org; draft-ietf-ppsp-base-tracker-protocol@ietf.org; >> Zongning; ppsp@ietf.org >> Subject: Stephen Farrell's Discuss on draft-ietf-ppsp-base-tracker-protocol-10: >> (with DISCUSS and COMMENT) >> >> Stephen Farrell has entered the following ballot position for >> draft-ietf-ppsp-base-tracker-protocol-10: Discuss >> >> When responding, please keep the subject line intact and reply to all email >> addresses included in the To and CC lines. (Feel free to cut this introductory >> paragraph, however.) >> >> >> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html >> for more information about IESG DISCUSS and COMMENT positions. >> >> >> The document, along with other ballot positions, can be found here: >> https://datatracker.ietf.org/doc/draft-ietf-ppsp-base-tracker-protocol/ >> >> >> >> ---------------------------------------------------------------------- >> DISCUSS: >> ---------------------------------------------------------------------- >> >> >> 6.2 - can you explain to me how the overall protection against pollution works? >> I'm not quite following it and am concerned that it may be lacking. But that may >> just be me forgetting how this ties together with rfc7574. > > [Rachel]: Tracker protocol is used to exchange information like peer list, peer status between peers and trackers. Content pollution is usually caused by content changing between peers. Because trackers don't exchange content information with peers, they don't have ways to detect if a peer is polluting the content or not. The integrity verification schemes mentioned in Section 6.2 are considered in peer protocol, which can reference section 6.1 of RFC7574. So how about changing the Section 6.2 to the following: > " > Malicious peers may declaim ownership of popular content to the tracker and try to serve polluted (i.e., decoy content or even virus/trojan infected contents) to other peers. For trackers, they don't exchange content information among peers, hence they are difficult to detect if a peer is polluting the content or not. Usually, this kind of pollution can be detected by PPSPP [RFC7574]. More details can be seen in Section 6.1 and Section 12 of [RFC7574]. > " > >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> - I-D nits notes a bunch of missing reference entries, e.g. >> for RFC6972 as well as 6 others. Probably some xml2rfc issue. > > [Rachel]: Will fix it in the new version. >> >> - intro: last para (just before 1.1) puzzles me. Not sure why it''s there. > > [Rachel]: How about changing to > > OLD > " > This document describes the base PPSP Tracker protocol and how it > satisfies the requirements for the IETF Peer-to-Peer Streaming > Protocol, in order to derive the implications for the standardization > of the PPSP streaming protocols and to identify open issues and > promote further discussion. > " > > NEW > " > This document introduces a base PPSP Tracker Protocol which satisfies the requirements from [RFC6972]. > " >> >> - intro: why is there no mention of Bit Torrent? This seems to be the same >> design for the same purpose, and BT is in widespread use so not explaining the >> relationship seems a bit odd. 5.1.2 seems to be plain silly in that light, while BT >> is not a "standard" that is irrelevant - it has been widely deploy and migration >> from BT to this, or co-existence, would seem critical to the success of this >> effort. > > [Rachel]: Actually, at the drafting of PPSP-TP, there's another draft [draft-ietf-ppsp-survey] which has described most of the popular and deployed p2p applications. Currently, [draft-ietf-ppsp-survey] is dead, so maybe we should include some BT descriptions in our draft? > >> >> - RFC2616 is obsoleted. > > [Rachel]: Will update. > >> >> - 6.1: I agree with Katheen's discuss, a MUST use TLS is needed here really and >> just reflects reality and is not an additioanl consideration. It is needed for >> clarity though. > > [Rachel]: Ok. > >> >> - 6.2: Given the history of spoofing in BT I wondered why there is no object level >> origin auth defined here. > > [Rachel]: How about adding a paragraph in Section 6.2 as following: > > NEW > " > Some attackers that disrupt P2P streaming on behalf of content providers may provide false or modified content or peer list information to achieve certain malicious goals. Peers connecting to those portals or trackers provided by the attackers may be redirected to some corrupted malicious content. However, there is no standard ways to for peers to avoid this kind of situations completely. Peers can have mechanisms to detect undesirable content or results themselves. For example, if a peer finds the portal returns some undesired content information or the tracker returns some malicious peer lists, the peer may want to quit the swarm, or switch to other P2P streaming services provided by other content providers. > " > >> >> - I also agree with Ben's discuss. >> > From nobody Tue Jan 12 08:42:26 2016 Return-Path: X-Original-To: ppsp@ietf.org Delivered-To: ppsp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA641B2AED; Tue, 12 Jan 2016 08:42:24 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.11.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160112164224.32486.58889.idtracker@ietfa.amsl.com> Date: Tue, 12 Jan 2016 08:42:24 -0800 Archived-At: Cc: draft-ietf-ppsp-base-tracker-protocol@ietf.org, The IESG , ppsp-chairs@ietf.org, ppsp@ietf.org, rfc-editor@rfc-editor.org Subject: [ppsp] Protocol Action: 'PPSP Tracker Protocol-Base Protocol (PPSP-TP/1.0)' to Proposed Standard (draft-ietf-ppsp-base-tracker-protocol-12.txt) X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2016 16:42:24 -0000 The IESG has approved the following document: - 'PPSP Tracker Protocol-Base Protocol (PPSP-TP/1.0)' (draft-ietf-ppsp-base-tracker-protocol-12.txt) as Proposed Standard This document is the product of the Peer to Peer Streaming Protocol Working Group. The IESG contact persons are Spencer Dawkins and Martin Stiemerling. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-ppsp-base-tracker-protocol/ Technical Summary This document specifies the Peer-to-Peer Streaming Protocol Tracker Protocol (PPSP-TP), an application-layer control (signaling) protocol for the exchange of meta information between trackers and peers. The specification outlines the architecture of the protocol and its functionality, and describes message flows, message processing instructions, message formats, formal syntax and semantics. The PPSP-TP enables cooperating peers to form content streaming overlay networks to support near real-time Structured Media content delivery (audio, video, associated timed text and metadata). Working Group Summary There was debate on the encoding of the protocol messages, particularly on text-based versus binary-based. Rough consensus was finally made that using text-based encoding as mandatory encoding scheme. Document Quality There is at least one implementation of PPSP-TP, as described in another PPSP Usage I-D. The document itself should have good quality, based on several rounds of expertise review conducted within PPSP group. Personnel Document shepherd is Ning Zong. Responsible AD is Martin Stiemerling From nobody Wed Jan 13 14:38:00 2016 Return-Path: X-Original-To: ppsp@ietf.org Delivered-To: ppsp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E76D81A877C; Wed, 13 Jan 2016 14:37:58 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: "IETF Announcement List" X-Test-IDTracker: no X-IETF-IDTracker: 6.12.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160113223758.20338.1172.idtracker@ietfa.amsl.com> Date: Wed, 13 Jan 2016 14:37:58 -0800 Archived-At: Cc: ppsp@ietf.org, hishigh@sina.com Subject: [ppsp] WG Action: Conclusion of Peer to Peer Streaming Protocol (ppsp) X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 22:37:59 -0000 The Peer to Peer Streaming Protocol (ppsp) working group in the Transport Area has successfully finished its chartered work and is now closed. The PPSP mailing list (ppsp@ietf.org) will remain open. Thank you to all contributors, draft authors, and the chairs! Regards, Martin Stiemerling TSV Transport Area Director From nobody Sat Jan 16 19:04:31 2016 Return-Path: X-Original-To: ppsp@ietf.org Delivered-To: ppsp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F6B1A884E for ; Wed, 13 Jan 2016 04:04:40 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.11.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160113120440.25827.32212.idtracker@ietfa.amsl.com> Date: Wed, 13 Jan 2016 04:04:40 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Sat, 16 Jan 2016 19:04:30 -0800 Subject: [ppsp] Milestones changed for ppsp WG X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 12:04:40 -0000 Changed milestone "Submit problem statement to IESG as Informational", resolved as "Done". Deleted milestone "Submit architectural survey to IESG as Informational". Changed milestone "Submit requirements document to IESG as Informational", resolved as "Done". Changed milestone "Submit PPSP peer protocol to IESG as Proposed Standard", resolved as "Done". Changed milestone "Submit PPSP tracker protocol to IESG as Proposed Standard", resolved as "Done". Deleted milestone "Submit usage guide to IESG to IESG as Informational". URL: https://datatracker.ietf.org/wg/ppsp/charter/ From nobody Thu Jan 21 01:31:17 2016 Return-Path: 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 442371A1B87 for ; Thu, 21 Jan 2016 01:31:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.988 X-Spam-Level: *** X-Spam-Status: No, score=3.988 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, CN_BODY_35=0.339, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SPF_PASS=-0.001] autolearn=no 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 7MjYSIDQ1M_F for ; Thu, 21 Jan 2016 01:31:14 -0800 (PST) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 088821A1B84 for ; Thu, 21 Jan 2016 01:31:14 -0800 (PST) Received: by mail-wm0-x234.google.com with SMTP id b14so70390440wmb.1 for ; Thu, 21 Jan 2016 01:31:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=biLxa7vZcL3lIY+xK/7j7aIhBMRfUALo3rY2jYb2M2Q=; b=TWVqlqbUbN9TZp2dOuTxkOfwyyPzit4Xdt0Mz+uSTar8APyCMaTXAtAr80SWqp/zxR iApagm5jXPAaQigi3ewzq80FjurQI+K/zcJHDSlWq7YXygmPOCx5SdmzBd4W0oVRnB0C HUVf1pa6mEHkBg92V1pCPhkqms08eRDj+AkO4WLSDDGXNntt60jRTuE4gcKKx6YUwkMg tQITLp9dW5ZAwOdJ+KrhdJfddCkSiCXsAWBigrrHi2bQ15YiPIT6mHL+x/WQ3DI0VGX7 R/WwzRJhg+ilFPVTDWIfl1zv1AoX10J2cGRl4ly73Nh/BKeAqX+gu1fa6QwqQDjxg4SZ 9uYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=biLxa7vZcL3lIY+xK/7j7aIhBMRfUALo3rY2jYb2M2Q=; b=dfueSrYTqB/8MW8Fygk8xiu91L8x+RD9xvaJ8VZiZ2EBgVpQ2bkaeY21KfRsrHo6g1 dG/5guYCwisfrSF955KkXMPcH2YylWkRZkR+TbxBzxz0eDuSGAF/YRyaK12UfWon2vmt XyQi9Wgx2badlbIEYpSxCDaRwjPjvZmZ30yOUlHuc97s+HuJNyurEfgIy77tfD0qNrzG JtwJUiQjrsgs/uokLO1ZmRTd60BnXPXNPIrvsqfEjxeOCCn/4SS5yJeO5rO8q+NUu+C1 /Cp8NA/9wBlf4cbXfNntA0vB0mWd+a4lIf9h4dkqhIP/rs/ldKEWsJBtkBgbjF6xAjIU hCgw== X-Gm-Message-State: AG10YOTQl3mSDDES9vBkyo7vBzten/FVbSJuB9rOytOIzZwGiVhjO7tFSW/qEQ/Io6fZAw== X-Received: by 10.28.230.92 with SMTP id d89mr9555550wmh.12.1453368671598; Thu, 21 Jan 2016 01:31:11 -0800 (PST) Received: from Martins-MacBook-Pro-2.local ([2001:41b8:9bf:fda6:b043:653b:cbfd:5a3f]) by smtp.googlemail.com with ESMTPSA id z65sm2010685wmg.10.2016.01.21.01.31.10 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jan 2016 01:31:10 -0800 (PST) To: ppsp References: <20160115051801.C1BA32E0132@webmail.sinamail.sina.com.cn> From: Martin Stiemerling Message-ID: <56A0A55D.7000801@gmail.com> Date: Thu, 21 Jan 2016 10:31:09 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160115051801.C1BA32E0132@webmail.sinamail.sina.com.cn> Content-Type: text/plain; charset=gbk; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ppsp] =?utf-8?b?5Zue5aSN77yaV0cgQWN0aW9uOiBDb25jbHVzaW9uIG9mIFBl?= =?utf-8?q?er_to_Peer_Streaming_Protocol_=28ppsp=29?= X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2016 09:31:15 -0000 Hi Yunfei, all, One thing to emphasize: The PPSP list is open and you can use this to discuss issues around the specifications, if any, and also, which is more important at this time, to discuss implementation efforts! Thanks, Martin Am 15.01.16 um 06:18 schrieb yunfei: > Hi all, > > Thanks all of you, the contributors and draft authors for your > support and hard work to PPSP working group all the time ever since its > initiatives in IETF. It's YOU who really makes PPSP come true. > > I really appreciate the guidance and help from the AD, Lars and > Martin, who make the working group work as planned. I am grateful to > work together with the administration team of the PPSP working > group, Gonzalo,Cullen, Martin and Ning. It's really a great experience > in IETF. > > The PPSP mailing list (ppsp@ietf.org) will remain open. Please > feel free to discuss things related to PPSP and wish to have opportunity > to continue working with all of you! > > > > Best regards, > > Yunfei > > > > ----- 原始邮件 ----- > 发件人：IESG Secretary > 收件人："IETF Announcement List" > 抄送人：zongning@huawei.com, hishigh@sina.com, ppsp@ietf.org > 主题：WG Action: Conclusion of Peer to Peer Streaming Protocol (ppsp) > 日期：2016年01月14日 06点37分 > > > The Peer to Peer Streaming Protocol (ppsp) working group in the > Transport Area has successfully finished its chartered work and is now > closed. The PPSP mailing list (ppsp@ietf.org) will remain open. > Thank you to all contributors, draft authors, and the chairs! > Regards, > Martin Stiemerling > TSV Transport Area Director