That will typically be the case because standards take time. Interoperability is a huge win though.
-Adam On 7/13/07, Lemon Obrien <[EMAIL PROTECTED]> wrote:
>>Are any of these protocols actually used by real-world P2P applications or developers? no. i think the industry is light years ahead of anything official. *David Barrett <[EMAIL PROTECTED]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]> >* wrote: Are any of these protocols actually used by real-world P2P applications or developers? Or are they more solutions in search of problems? It seems to me the IETF should focus on standardizing the protocols that have already been proven in the real world: any protocol that lacks an active userbase depending upon its success is probably not worth the effort to standardize. Maybe the IETF should come out with something like the "IRTF" for "Internet Research Task Force" where academic communities and research groups can propose and iterate upon forward-thinking designs without being distracted by the real world. This would let the IETF refocus on those protocols that are sufficiently mature and tested to warrant real standardization. -david > -----Original Message----- > From: [EMAIL PROTECTED]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]>[mailto: p2p-hackers- <https://mail.google.com/mail?view=cm&tf=0&to=p2p-hackers-> > [EMAIL PROTECTED]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]>] On Behalf Of Wes Felter > Sent: Thursday, July 12, 2007 6:14 PM > To: theory and practice of decentralized computer networks > Subject: [p2p-hackers] New P2P protocols galore in the IETF > > Looks like the IETF P2PSIP working group is having some kind of > protocol deathmatch. Some of these are just DHTs, while others are > more general. > > Peer-to-Peer Protocol (P2PP) http://tools.ietf.org/html/draft-baset- > p2psip-p2pp-00 > > "This document defines the Peer-to-Peer Protocol (P2PP), an > application-layer protocol, for creating and maintaining an overlay > of participant nodes. The overlay can be created using various > structured and unstructured peer-to-peer protocols such as Chord, > Pastry, Kademlia, Gnutella, and Gia." > > REsource LOcation And Discovery (RELOAD) http://tools.ietf.org/html/ > draft-bryan-p2psip-reload-01 > > "This document outlines the motivation, requirements, and > architectural design for a extensible and lightweight distributed > REsource LOcation And Discovery (RELOAD) protocol. RELOAD is a > Peer- > to-Peer (P2P) based approach for registration and resource discovery > using distributed hash tables maintained with binary messages." > > Address Settlement by Peer to Peer http://tools.ietf.org/html/draft- > jennings-p2psip-asp-00 > > "This document defines Address Settlement by Peer-to-Peer (ASP), a > peer-to-peer (P2P) binary signaling protocol for usage on the > Internet. A P2P signaling protocol provides its clients with an > abstract hash table service between a set of cooperating peers that > form the P2P network. " > > Extensible Peer Protocol (XPP) http://tools.ietf.org/html/draft- > marocco-p2psip-xpp-00 > > "This document defines the Extensible Peer Protocol (XPP), a > lightweight binary protocol for end-to-end sessions between peers in > distributed overlay networks. One of the main goals while creating > this protocol was support for nodes located behind firewalls and > NATs. XPP therefore uses UDP and allows endpoints to simultaneously > initiate sessions. Given the choice of the underlying protocol > (UDP), XPP also defines mechanisms for message fragmentation and > reliability." > > A Distributed Transport Function in P2PSIP using HIP for Multi-Hop > Overlay Routing http://tools.ietf.org/html/draft-matthews-p2psip-hip- > hop-00 > > "This document examines a P2PSIP architecture where the peer-to-peer > (P2P) layer is separate from and lies below the SIP layer. We > discuss the functions of the P2P layer in such an architecture, and > focus in on the Distributed Transport function - the function that > allows a peer to exchange messages with any other peer in the > overlay, even in the presence of NATs. ... the > Host Identity Protocol (HIP) already provides a number of these > features. We then propose extensions to HIP that allow it to > provide > the missing features. We discuss how a complete P2PSIP architecture > can be built around HIP, and contrast this approach with other > approaches for implementing a P2P layer." > > Wes Felter - [EMAIL PROTECTED]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]>- http://felter.org/wesley/ > > _______________________________________________ > p2p-hackers mailing list > [email protected]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]> > http://lists.zooko.com/mailman/listinfo/p2p-hackers _______________________________________________ p2p-hackers mailing list [email protected]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]> http://lists.zooko.com/mailman/listinfo/p2p-hackers You don't get no juice unless you squeeze Lemon Obrien, the Third. http://www.tamago.us _______________________________________________ p2p-hackers mailing list [email protected]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]> http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
