Re: [ppsp] Question on PPSP IOP and implementation

Arno Bakker <arno@cs.vu.nl> Fri, 05 June 2015 06:03 UTC

Return-Path: <a.bakker@vu.nl>
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 5BC4E1B2C4D for <ppsp@ietfa.amsl.com>; Thu, 4 Jun 2015 23:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.885
X-Spam-Level:
X-Spam-Status: No, score=0.885 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 StglCuWnPGnm for <ppsp@ietfa.amsl.com>; Thu, 4 Jun 2015 23:03:13 -0700 (PDT)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.19]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC95A1B2C50 for <ppsp@ietf.org>; Thu, 4 Jun 2015 23:03:12 -0700 (PDT)
Received: from PEXHB012A.vu.local (130.37.236.66) by mailin.vu.nl (130.37.164.19) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 5 Jun 2015 08:03:10 +0200
Received: from m90-132-138-215.cust.tele2.nl (130.37.253.20) by mails.vu.nl (130.37.236.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 5 Jun 2015 08:03:09 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <609FE8B8E7BD1248A27BD3B8BC699ABD1D7424A9@SMTP2.etri.info>
References: <609FE8B8E7BD1248A27BD3B8BC699ABD1D7424A9@SMTP2.etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----QUEDNP971SXZ7GADKXQHJ6UNJZW9BV"
Content-Transfer-Encoding: 8bit
From: Arno Bakker <arno@cs.vu.nl>
Date: Fri, 5 Jun 2015 08:02:55 +0200
To: =?UTF-8?B?6rmA7ISx7Zic?= <shkim@etri.re.kr>, "ppsp@ietf.org" <ppsp@ietf.org>
Message-ID: <87DA90A8-464C-43D7-A7F9-A6E066CBB3FA@cs.vu.nl>
X-Originating-IP: [130.37.253.20]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ppsp/b75ko4x1BJJhjozZO09JFxToTws>
Subject: Re: [ppsp] Question on PPSP IOP and implementation
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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, 05 Jun 2015 06:03:17 -0000

Hi

The libswift implementation is up-to-date. Only PEX_REScert not implemented.

CU,
       Arno

On June 5, 2015 4:07:44 AM CEST, "김성혜" <shkim@etri.re.kr> wrote:
>
>
>Hi All,
>
>We are planning to develop PPSP including both of TP and PP.
>Some of the solutions (open source) we’ve found are
>libswift(https://github.com/libswift/libswift) and
>Swirl(http://www.swirl-project.org/).
>I seems libswift is implemented on draft version 00. Is this still
>valid?
>Are there any other PPSP implementations?
>Does this WG have any plan for IOP test for PPSP?
>Regards,
>Sung