From p2psip-bounces@ietf.org Tue Oct 09 06:44:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfCYh-0001Nq-4x; Tue, 09 Oct 2007 06:43:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfCYf-0001Kw-ME for p2psip@ietf.org; Tue, 09 Oct 2007 06:43:25 -0400 Received: from wip-cdc-wd.wipro.com ([203.91.201.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfCYY-0001bg-3L for p2psip@ietf.org; Tue, 09 Oct 2007 06:43:25 -0400 Received: from wip-cdc-wd.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 05F3C18062 for ; Tue, 9 Oct 2007 16:13:07 +0530 (IST) Received: from blr-ec-bh01.wipro.com (blr-ec-bh01.wipro.com [10.201.50.91]) by wip-cdc-wd.wipro.com (Postfix) with ESMTP id E35EF18051 for ; Tue, 9 Oct 2007 16:13:06 +0530 (IST) Received: from PNE-HJN-MBX01.wipro.com ([10.111.50.181]) by blr-ec-bh01.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 9 Oct 2007 16:13:06 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: [P2PSIP] Who is working on an implementation for a P2PSIPproposal? Date: Tue, 9 Oct 2007 16:11:12 +0530 Message-ID: <5DE86B4C624D4545B8A5CA1467DB936405E623AF@PNE-HJN-MBX01.wipro.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [P2PSIP] Who is working on an implementation for a P2PSIPproposal? thread-index: AcgBH5x+GUTPOiiZTVaihIvBFeGvbgJQFuUA References: From: To: X-OriginalArrivalTime: 09 Oct 2007 10:43:06.0719 (UTC) FILETIME=[2D3DCEF0:01C80A61] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8a961490db2a74c7613bf0201229f176 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: p2psip-bounces@ietf.org =20 Is HIP-HOP implementation will be based out of following draft ?? Or there will be any further updations to it ?? http://www.ietf.org/internet-drafts/draft-matthews-p2psip-hip-hop-00.txt -chetan -----Original Message----- From: p2psip-request@ietf.org [mailto:p2psip-request@ietf.org]=20 Sent: Thursday, September 27, 2007 9:31 PM To: p2psip@ietf.org Subject: P2PSIP Digest, Vol 9, Issue 25 Send P2PSIP mailing list submissions to p2psip@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www1.ietf.org/mailman/listinfo/p2psip or, via email, send a message with subject or body 'help' to p2psip-request@ietf.org You can reach the person managing the list at p2psip-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of P2PSIP digest..." ---------------------------------------------------------------------- The group behind the HIP-HOP proposal has an implementation planned. The approach we are taking is to write a -00 draft of an I-D describing an aspect of the proposal first, and then implement the result. In our opinion, there is a certain discipline that comes from writing an I-D; it forces you to think more about what you are doing. For example, it forces you to argue for your design choices and forces you to think about the security implications of your design. We plan to write an I-D before starting our implementation, and then use the feedback from the implementation to revise the I-D. In our case, we are planning to base our implementation on an existing HIP implementation, since HIP-HOP is an extension to HIP. Initially, this will likely be the Ericsson HIP-for-BSD implementation, though we are also investigating the OpenHIP implementation and may choose to do two implementations. Both of these HIP implementations are available today. The current HIP-HOP document describes a high-level architecture. We are currently working out the details on some of the aspects of this design before writing an I-D. - Philip Message: 1 Date: Thu, 27 Sep 2007 09:50:52 -0400 From: chayn@imhocorp.com Subject: [P2PSIP] Out of Office To: p2psip@ietf.org Message-ID: =09 <48c491b5c0b5453699592539dee85bad@2fcd6b8b14534629b4a69e841de77654> Content-Type: text/plain; charset=3Diso-8859-1 Hello, I am out of the office and will be unable to respond to messages until Monday. Claude ------------------------------ Message: 2 Date: Thu, 27 Sep 2007 16:29:53 +0200 From: "Jan Seedorf" Subject: Re: [P2PSIP] Who is working on an implementation for a P2PSIPproposal? To: Message-ID: <113091BD57179D4491C19DA7E10CD696017E2227@mx1.office> Content-Type: text/plain; charset=3D"us-ascii" Dear Mosiuoa and all, I supervise a thesis at the University of Hamburg where we actually use the the same componenents to build a P2P-SIP prototype: OpenChord as a DHT and JAIN-SIP to build a SIP-to-DHT-Adaptor. It works fine (tested only with softphones so far). Our focus is security: we intend to measure how much delay certain security add-ons (either on the DHT layer or on the application/SIP-layer) add to the total call setup-time. From a security perspective we believe that the real-time demands for VoIP may yield certain DHT-security techniques more suited for P2P-SIP than others. Exploring this area is the core of our work. Mosiuoa: if you are interested in exchanging experiences etc. send me an e-mail, I am interested in your experiences so far. Specifically, we had some (minor) problems with iterative routing in OpenChord, some of which have been fixed in the latest release. Kind regards, Jan -----Original Message----- From: Mosiuoa Tsietsi [mailto:mosiuoat@gmail.com] Sent: Tuesday, September 25, 2007 5:05 PM To: Adrian Georgescu Cc: P2PSIP Mailing List Subject: Re: [P2PSIP] Who is working on an implementation for a P2PSIPproposal? Hi, We at Rhodes University in South Africa have implemented a design for a P2P SIP node based on the OpenChord and Bamboo DHTs. Its basically middleware between the application logic and the underlying SIP stack. For proof of concept, we incorporated this layer into a VOIP client from NIST labs which embeds a JAIN stack. We have not been able to push out an ID yet, but are planning to - but alot of the ideas that have been criss-crossing on this list have fed into the implementation i.e. DHT agnosticism (overlay pluggability), SIP-over-P2P, separation of P2P layer from service layer (pluggable services), use of DynDNS for CS SIP-P2P SIP interoperation etc; Hope to submit something soon just to communicate ideas and experiences.=20 Mos On 9/25/07, Adrian Georgescu wrote: AG Projects is also providing infrastructure solutions for self- organizing SIP Proxies by using P2PSIP concepts. =09 Adrian =09 On Sep 25, 2007, at 4:32 PM, Bruce Lowekamp wrote: =09 > SIPeerior has a full P2PSIP that is for sale now and is being used by=20 > real-world customers. > > There are some slight differences between the commercial version and > RELOAD, mostly due to lessons learned from one being incorporated into > the other at different times.=20 > > Bruce > > > On 9/24/07, Hannes Tschofenig wrote: >> Let's just ask the group: Who has done implementation work (or is=20 >> planning todo some implementation work) with regard to a proposal >> discussed in this group? >> >> Ciao >> Hannes >> >> >> Peter Pan wrote: >>> not just "when and how" but also "who and whether", i think: >>> >>> may we know who are working on p2psip implementations (both >>> private and >>> open-source)? >>> >>> how can we know whether yours are comprehensive (competent,=20 >>> independent, >>> interoperable, operational, ... ) or not? > > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org =20 > https://www1.ietf.org/mailman/listinfo/p2psip =09 =09 _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org =20 https://www1.ietf.org/mailman/listinfo/p2psip =09 ------------------------------ Message: 3 Date: Thu, 27 Sep 2007 17:46:56 +0200 From: "Mosiuoa Tsietsi" Subject: Re: [P2PSIP] A DHT question on peers running out of storage To: "Spencer Dawkins" Cc: P2PSIP Mailing List Message-ID: <9b9e17760709270846n79e2b759ldc66d912271ba637@mail.gmail.com> Content-Type: text/plain; charset=3D"iso-8859-1" Hi again, If we assume that the overlay refuses to store the key because the correct root of the key is unable to hold it due to exhausted storage capacity, then we find ourselves in a similar situation that skype did. However, if we allow the root of the key to delegate the key to another adjacent node, it probably must maintain state about that (some pointer that is lighter than storing the actual resource), otherwise, how do we differentiate between a key that doesn't exist in the overlay anymore (i.e. a node that has since resigned and had its binding removed from the overlay) and a key that is on the adjacent node? Otherwise, we find ourselves 3XX'ing for stuff that's not there anymore. Taking a step back though, I think it's unlikely to happen. If the only nodes that store keys are the peer nodes then I think constraints are put on them to have enough storage to implement the location service. My thots, Mos On 9/27/07, Spencer Dawkins wrote: > > Does the "not enough storage" peer remember specific key/value pairs=20 > that have been stored on an alternative peer, or just 3XX everything=20 > it doesn't find locally to the same alternative peer? > > Spencer > > ----- Original Message ----- > *From:* Michal Giermasinski > *To:* Mosiuoa Tsietsi > *Cc:* P2PSIP Mailing List > *Sent:* Thursday, September 27, 2007 3:55 AM > *Subject:* Re: [P2PSIP] A DHT question on peers running out of storage > > Hello Mosiuia, Jiang, > > I can see a potential problem here. When for storing some data in a=20 > peer that has not enough place to store it you opt to send SIP 480 or=20 > 486. Then data can be stored in the relevant peer with key neer the=20 > chosen one. For sure this will work. But there will be a problem when=20 > peer C would like to read these data. He will try to retrieve some=20 > information according to the known key for DHT. But when reaching the=20 > node that was supposed to store information this will fail. 3xx message (redirection) will be sent. > > THis will work but we need to remember that this will not be optimal I > guess. > > kind regards > Michal > > > > 2007/9/26, Mosiuoa Tsietsi : > > > > Hi again, > > > > True, it's not the aim of P2P SIP to engineer DHT algorithms, but to > > reuse what is there and hopefully provide generic interfaces to all=20 > > things DHT (or all things P2P for that matter). But I am hoping=20 > > that pressure for such features will stimulate work in the area to=20 > > provide such tweaks in the algorithms. Much like you said Jiang,=20 > > until such a time, the P2P node probably needs to be intelligent=20 > > enough to at the higher level to avoid irregularities in the DHT. > > > > In the case of P2P over SIP, a node would probably want to send out=20 > > something like a 480 Temp Unavailable or 486 Busy Here, and indicate > > to the requestor to try some other node closer to the key until one=20 > > such node is found. I'm guessing if there is no proper candidate=20 > > found (though I imagine it is quite unlikely that such a situation=20 > > may arise), the node is not allowed to register, until some free space is found in the DHT. > > > > More or less the same for SIP over P2P, where the associated=20 > > protocols employed for the put operation would fail, and the node=20 > > would not be allowed entry until later. > > > > That said, the stuff I have been working on explores the possibility > > of creating a new niche market for application developers who=20 > > develop plugin wrapper objects for currently existing DHT=20 > > implementations which implement a generic interface. It does=20 > > require a rather detailed understanding of the inner working of the=20 > > DHT itself. I'm hoping that other work in the area will put such=20 > > kind of pressure so that more people start work in interventions in DHTs for specific use in applications such as P2P SIP. > > > > Mos > > > > On 9/26/07, JiangXingFeng wrote: > > > > > > Hi all, > > > > > > >I agree that implementing this facility at a layer above the DHT > > > logic is a > > > >possibility. But I also think it can be achieved innately within=20 > > > >the > > > DHT > > > algorithms >without breaking the mapping structure. Much in the=20 > > > same way that proximity >metrics are incorporated into DHT=20 > > > algorithms (for example to choose the "best >neighbor") perhaps=20 > > > the same kind of logic can be used to choose the "best storer" of=20 > > > >data. When the DHT is performing maintenance tasks, as it=20 > > > optimises routing tables >and such, it can also take into > > > > > > consideration some storage metrics as well. > > > > > > Yes, if the DHT algorithm could provide the storage property like=20 > > > what you've just described, I think it would be the best solution=20 > > > to the issue of storage shortage of the peer. P2PSIP peer=20 > > > protocol does not intend to > > > > > > develop new DHT algorithms. What it really does is to accommodate=20 > > > different DHT algorithms and make sure the message format could be > > > extensible enough to convey the semantics of the each DHT=20 > > > algorithm. So if the DHT algorithm does not solve the shortage of=20 > > > the peer's storage, the better choice to this issue is to solve it > > > on the upper layer application above. > > > > > > Comments? > > > > > > Mos > > > > > > > > > > > > > > > > _______________________________________________ > > P2PSIP mailing list > > P2PSIP@ietf.org > > https://www1.ietf.org/mailman/listinfo/p2psip > > > > > ------------------------------ > > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www1.ietf.org/mailman/listinfo/p2psip > > > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www1.ietf.org/mailman/listinfo/p2psip > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www1.ietf.org/pipermail/p2psip/attachments/20070927/be1f605d/atta chment-0001.html ------------------------------ _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip End of P2PSIP Digest, Vol 9, Issue 25 ************************************* _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip From p2psip-bounces@ietf.org Tue Oct 09 08:44:33 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfERe-0001we-36; Tue, 09 Oct 2007 08:44:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfERc-0001nX-Ob for p2psip@ietf.org; Tue, 09 Oct 2007 08:44:16 -0400 Received: from mail5.primus.ca ([216.254.141.172] helo=mail-05.primus.ca) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfERR-0006C8-JM for p2psip@ietf.org; Tue, 09 Oct 2007 08:44:11 -0400 Received: from [216.13.42.68] (helo=[10.10.80.124]) by mail-05.primus.ca with esmtpa (Exim 4.63) (envelope-from ) id 1IfEQl-0002AP-01; Tue, 09 Oct 2007 08:43:23 -0400 In-Reply-To: <5DE86B4C624D4545B8A5CA1467DB936405E623AF@PNE-HJN-MBX01.wipro.com> References: <5DE86B4C624D4545B8A5CA1467DB936405E623AF@PNE-HJN-MBX01.wipro.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <213C4531-F1EE-4C71-8C20-453AE4284561@magma.ca> Content-Transfer-Encoding: 7bit From: Philip Matthews Subject: Re: [P2PSIP] Who is working on an implementation for a P2PSIPproposal? Date: Tue, 9 Oct 2007 08:44:07 -0400 To: "chetan.amale@wipro.com> X-Mailer: Apple Mail (2.752.2) X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68] X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: p2psip@ietf.org X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: p2psip-bounces@ietf.org On 9-Oct-07, at 06:41 , wrote: > > Is HIP-HOP implementation will be based out of following draft ?? Or > there will be any further updations to it ?? > > http://www.ietf.org/internet-drafts/draft-matthews-p2psip-hip- > hop-00.txt > > -chetan We are working on an update to it. The hip-hop-00 draft was just a high-level design sketch, and we are now working out the details. - Philip _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip From p2psip-bounces@ietf.org Thu Oct 25 06:07:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikzbn-0001TM-KR; Thu, 25 Oct 2007 06:06:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikzbm-0001SQ-6M for p2psip@ietf.org; Thu, 25 Oct 2007 06:06:34 -0400 Received: from tidos.tid.es ([193.145.240.2] helo=correo.tid.es) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ikzbg-0006eO-Av for p2psip@ietf.org; Thu, 25 Oct 2007 06:06:33 -0400 Received: from tid (filvit [192.168.48.202]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JQG00AY7PEMJN@tid.hi.inet> for p2psip@ietf.org; Thu, 25 Oct 2007 12:06:22 +0200 (MEST) Received: from N90 (N90.hi.inet [10.95.14.205]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JQG00AXYPEMJN@tid.hi.inet> for p2psip@ietf.org; Thu, 25 Oct 2007 12:06:22 +0200 (MEST) Date: Thu, 25 Oct 2007 12:06:33 +0200 From: Gustavo Garcia To: p2psip@ietf.org Message-id: <008b01c816ee$b8c93240$cd0e5f0a@N90> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcgW7rhsA5bcTw8AQSKmavZA1lqONg== X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [P2PSIP] Draft: P2PSIP bootstrapping using DNS-SD X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: p2psip-bounces@ietf.org We have submitted a draft documenting a P2PSIP bootstrap mechanism using DNS-SD that we have implemented in our prototypes. We hope this is useful to somebody. Comments are welcomed. Until it is officially available you can find it here: http://195.235.93.189/~ggb/draft-garcia-p2psip-dns-sd-bootstrapping-00.txt Abstract: "This document describes a DNS-based bootstrap mechanism to discover the initial peer or peers needed to join a P2PSIP Overlay. The document specifies the use of DNS Service Discovery (DNS-SD) and the format of the required resource records to support the discovery of P2PSIP peers. This mechanism can be applied in scenarios with DNS servers or combined with multicast DNS to fulfill different proposed P2PSIP use cases." Thanks, G. _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip From p2psip-bounces@ietf.org Thu Oct 25 09:20:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2cT-0004gy-RT; Thu, 25 Oct 2007 09:19:29 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2cT-0004gO-47 for p2psip@ietf.org; Thu, 25 Oct 2007 09:19:29 -0400 Received: from brinza.cc.columbia.edu ([128.59.29.8]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il2cS-0006Ua-P8 for p2psip@ietf.org; Thu, 25 Oct 2007 09:19:29 -0400 Received: from [192.168.0.103] (pool-71-183-34-28.nycmny.fios.verizon.net [71.183.34.28]) (user=jwl3 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id l9PDJR7f015085 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Oct 2007 09:19:27 -0400 (EDT) In-Reply-To: <008b01c816ee$b8c93240$cd0e5f0a@N90> References: <008b01c816ee$b8c93240$cd0e5f0a@N90> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <76B29C63-EC62-42E5-9CF2-E1AC67B4DB03@cs.columbia.edu> Content-Transfer-Encoding: 7bit From: Jae Woo Lee Subject: Re: [P2PSIP] Draft: P2PSIP bootstrapping using DNS-SD Date: Thu, 25 Oct 2007 09:19:24 -0400 To: Gustavo Garcia X-Mailer: Apple Mail (2.752.3) X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: p2psip@ietf.org X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: p2psip-bounces@ietf.org Dear Gustavo, Thank you for writing this draft. DNS-SD is definitely a great way for locating a P2PSIP admitting peer, and it's good to see that the details get specified. One small thing you might want to fix in the next version: with [I- D.lee-sip-dns-sd-uris], I think you meant to reference our draft http://tools.ietf.org/id/draft-lee-sip-dns-sd-uri-01.txt, but it points to something else instead. Regards, Jae On Oct 25, 2007, at 6:06 AM, Gustavo Garcia wrote: > > We have submitted a draft documenting a P2PSIP bootstrap mechanism > using > DNS-SD that we have implemented in our prototypes. We hope this is > useful > to somebody. Comments are welcomed. > > Until it is officially available you can find it here: > http://195.235.93.189/~ggb/draft-garcia-p2psip-dns-sd- > bootstrapping-00.txt > > Abstract: > "This document describes a DNS-based bootstrap mechanism to discover > the initial peer or peers needed to join a P2PSIP Overlay. The > document specifies the use of DNS Service Discovery (DNS-SD) and the > format of the required resource records to support the discovery of > P2PSIP peers. This mechanism can be applied in scenarios with DNS > servers or combined with multicast DNS to fulfill different proposed > P2PSIP use cases." > > Thanks, > G. > > > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www1.ietf.org/mailman/listinfo/p2psip _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip