Re: [RAI] Draft on P2P architectures
Dan York <dyork@voxeo.com> Tue, 24 February 2009 10:24 UTC
Return-Path: <dyork@voxeo.com>
X-Original-To: rai@core3.amsl.com
Delivered-To: rai@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C29433A6ADA for <rai@core3.amsl.com>; Tue, 24 Feb 2009 02:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hc5Ka7XKrg6c for <rai@core3.amsl.com>; Tue, 24 Feb 2009 02:24:37 -0800 (PST)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with SMTP id 2CE163A6A9A for <rai@ietf.org>; Tue, 24 Feb 2009 02:24:36 -0800 (PST)
Received: from 176.sub-97-175-99.myvzw.com (account dyork [97.175.99.176] verified) by voxeo.com (CommuniGate Pro SMTP 5.2.3) with ESMTPSA id 39153284; Tue, 24 Feb 2009 10:24:55 +0000
Message-Id: <D10B33C7-6871-49FF-8C54-E7A170D91F9C@voxeo.com>
From: Dan York <dyork@voxeo.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <49A2B548.5090200@ericsson.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 24 Feb 2009 05:24:52 -0500
References: <49A2B548.5090200@ericsson.com>
X-Mailer: Apple Mail (2.930.3)
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] Draft on P2P architectures
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 10:24:38 -0000
Gonzolo, On Feb 23, 2009, at 9:40 AM, Gonzalo Camarillo wrote: > the IAB has just submitted the following draft: > > http://www.ietf.org/internet-drafts/draft-iab-p2p-archs-00.txt > > Comments are welcome. Overall I think this is a useful document to help people understand what is going on with P2P architectures. A couple of comments: - I'll second Dan Wing's comment that the draft should include some mention of Bittorrent, given the wide usage of that P2P protocol. Many sites have info about torrent usage - some good pointers off of the Wikipedia page: http://en.wikipedia.org/wiki/ BitTorrent_(protocol) A mention (and links) would be good if for no other reason than to point people interested in learning more about P2P architectures to the wealth of info out there about torrent-based networks. - In section 2, it would seem to me beneficial to provide some further examples of applying the P2P definition beyond simply DNS, SIP and P2PSIP. I realize that the authors may be trying to constrain discussion to items directly handled by the IETF, but there are significant P2P deployments out there on the Internet (Bittorrent being one of them, but there are many others) that could be interesting to discuss in the document to help readers understand how the P2P definition can relate to deployed P2P systems. - When providing guidance on whether a P2P architecture is appropriate, it may be useful to encourage developers to think about the *type* of endpoints that will most likely be part of their network. I believe it was Xiao Lin in the P2PSIP mailing list who suggested that there were three types of endpoints to consider: fixed (e.g desktop computers), mobile (e.g. mobile phones) and mixed (e.g. laptops). Fixed endpoints or laptops may be good candidates for *peers* in a P2P environment, whereas mobile handsets may not be. (But they could be as "clients", see next bullet.) - The mobility discussion in the P2PSIP mailing list has highlighted that there may be some P2P environments where some nodes connect to the P2P overlay to access services but do not participate as full peers, perhaps because they don't have the processing capabilities or perhaps because they are too mobile and would create too much churn in the overlay with their movement. They are simply "clients" of the P2P network. It may be useful to mention this concept in this draft. - For the security section, I know there are several Internet-Drafts out there that get into P2P security issues and it may be useful to point to those drafts from this document. One of them that I know of (because I am involved with it) is for P2PSIP and is at: http://tools.ietf.org/html/draft-matuszewski-p2psip-security-requirements . (The draft is currently being refactored to align with the newest main P2PSIP specification and to split some pieces out into a separate document, but the content there may still be of interest.) - Also, the security section mentions does not mention (that I could see) that dealing with some of these security issues is precisely why some P2P networks will implement centralized enrollment/authentication servers (which were mentioned briefly back at the beginning of section 3). If you look at Skype, for example, they maintain tight centralized control over joining the P2P overlay through their enrollment servers. You have to have a valid Skype username and password in order for Skype to connect to the P2P cloud. Again, I think a document like this is quite a useful contribution to the interest out there in P2P architectures and I thank the IAB for putting it together. Regards, Dan -- Dan York, CISSP, Director of Emerging Communication Technology Office of the CTO Voxeo Corporation dyork@voxeo.com Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com Build voice applications based on open standards. Find out how at http://www.voxeo.com/free
- [RAI] Draft on P2P architectures Gonzalo Camarillo
- Re: [RAI] Draft on P2P architectures Dan Wing
- Re: [RAI] Draft on P2P architectures Dan York
- Re: [RAI] Draft on P2P architectures Gonzalo Camarillo
- Re: [RAI] Draft on P2P architectures Gonzalo Camarillo
- Re: [RAI] Draft on P2P architectures Dan Wing
- Re: [RAI] Draft on P2P architectures Enrico Marocco
- Re: [RAI] Draft on P2P architectures Gonzalo Camarillo
- Re: [RAI] Draft on P2P architectures Enrico Marocco
- Re: [RAI] Draft on P2P architectures Gonzalo Camarillo