RE: [P2PSIP] Concepts document: proposal for active/passive peerterminology
"Henry Sinnreich" <hsinnrei@adobe.com> Sat, 16 June 2007 04:07 UTC
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzPZe-0002H6-Hk; Sat, 16 Jun 2007 00:07:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzPZd-0002Gw-5D for p2psip@ietf.org; Sat, 16 Jun 2007 00:07:41 -0400
Received: from exprod6og55.obsmtp.com ([64.18.1.191]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HzPZb-0002Ve-KY for p2psip@ietf.org; Sat, 16 Jun 2007 00:07:40 -0400
Received: from source ([192.150.20.142]) by exprod6ob55.postini.com ([64.18.5.12]) with SMTP; Fri, 15 Jun 2007 21:07:33 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l5G47VWs022185; Fri, 15 Jun 2007 21:07:31 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id l5G47K0c012528; Fri, 15 Jun 2007 21:07:30 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 15 Jun 2007 21:07:20 -0700
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] Concepts document: proposal for active/passive peerterminology
Date: Fri, 15 Jun 2007 21:07:16 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D2299BDCC@namail5.corp.adobe.com>
In-Reply-To: <98A61432-091A-48BD-8596-531C688D899C@magma.ca>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [P2PSIP] Concepts document: proposal for active/passive peerterminology
Thread-Index: AcevYGAQ2wVUviPpTiGi5KnFfDdFlAAaeUlQ
References: <EC52E550-3438-4D89-9321-0A104D44828E@magma.ca> <001e01c7af13$506627a0$6905a40a@china.huawei.com><3F18E76823C95E4795181D74BAC7664F048C3D4A@esebe102.NOE.Nokia.com><46725A81.50607@telecomitalia.it><3F18E76823C95E4795181D74BAC7664F048C3F36@esebe102.NOE.Nokia.com> <98A61432-091A-48BD-8596-531C688D899C@magma.ca>
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Philip Matthews <philip_matthews@magma.ca>, marcin.matuszewski@nokia.com, Salman Abdul Baset <salman@cs.columbia.edu>
X-OriginalArrivalTime: 16 Jun 2007 04:07:20.0160 (UTC) FILETIME=[D5AF3600:01C7AFCB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: P2PSIP Mailing List <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 <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org
> I am actually quite sympathetic to the argument that P2PSIP should > not just be about SIP. Agree There is a lot of substance for both (1) the "client" argument and also (2) the "database" argument in the I-D that I recommend reading: > And I agree that supporting this strongly suggests that there should > be a "database access" protocol that is distinct from SIP. Agree As for the recent discussions, there is a lot of substance for both (1) the "client" argument and also (2) the "database" argument in the I-D that I recommend reading: http://tools.ietf.org/id/draft-singh-p2p-sip-01.txt I already regret going on vacation all next week and missing the fun :-) Thanks, Henry -----Original Message----- From: Philip Matthews [mailto:philip_matthews@magma.ca] Sent: Friday, June 15, 2007 5:11 PM To: marcin.matuszewski@nokia.com> <marcin.matuszewski@nokia.com; Salman Abdul Baset Cc: P2PSIP Mailing List Subject: Re: [P2PSIP] Concepts document: proposal for active/passive peerterminology I am actually quite sympathetic to the argument that P2PSIP should not just be about SIP. I do not think that SIP will be the only protocol used inside the overlay, and I now think that the peer protocol should be something other than SIP. But in your last few messages, you two seem to be proposing something different. It seems that you want the Distributed Database inside a P2PSIP overlay to be used for non-SIP-related data, and for this non-SIP-related data to be accessible via Puts/Gets from outside the overlay. I think this is a very interesting idea, but this is a new direction that I believe has not been suggested before. And I agree that supporting this strongly suggests that there should be a "database access" protocol that is distinct from SIP. - Philip _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip
- [P2PSIP] Concepts document: proposal for active/p… Dean Willis
- Fwd: Re: [P2PSIP] Concepts document: proposal for… Ted Hardie
- Re: [P2PSIP] Concepts document: proposal for acti… Avshalom Houri
- Re: [P2PSIP] Concepts document: proposal for acti… David A. Bryan
- Re: [P2PSIP] Concepts document: proposal for acti… Bill Mccormick
- Re: [P2PSIP] Concepts document: proposal for acti… Philip Matthews
- RE: [P2PSIP] Concepts document: proposal for acti… Gustavo García
- Re: [P2PSIP] Concepts document: proposal for acti… Philip Matthews
- Re: [P2PSIP] Concepts document: proposal for acti… Spencer Dawkins
- RE: [P2PSIP] Concepts document: proposal for acti… Henry Sinnreich
- RE: [P2PSIP] Concepts document: proposal for acti… Gustavo García
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- RE: [P2PSIP] Concepts document: proposal for acti… Salman Abdul Baset
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- Re: [P2PSIP] Concepts document: proposal for acti… Salman Abdul Baset
- RE: [P2PSIP] Concepts document: proposal for acti… JiangXingFeng
- Re: [P2PSIP] Concepts document: proposal for acti… Dean Willis
- Re: [P2PSIP] Concepts document: proposal for acti… Dean Willis
- Re: [P2PSIP] Concepts document: proposal for acti… Dean Willis
- Re: [P2PSIP] Concepts document: proposal for acti… Greger V. Teigre
- RE: [P2PSIP] Concepts document: proposalfor activ… marcin.matuszewski
- RE: [P2PSIP] Concepts document: proposal foractiv… marcin.matuszewski
- Re: [P2PSIP] Concepts document: proposal for acti… Philip Matthews
- RE: [P2PSIP] Concepts document: proposal foractiv… JiangXingFeng
- Re: [P2PSIP] Concepts document: proposalfor activ… Philip Matthews
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- Re: [P2PSIP] Concepts document: proposalfor activ… Salman Abdul Baset
- RE: [P2PSIP] Concepts document: proposal for acti… marcin.matuszewski
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- RE: [P2PSIP] Concepts document: proposalfor activ… Brian Rosen
- Re: [P2PSIP] Concepts document: proposal for acti… Philip Matthews
- Re: [P2PSIP] Concepts document: proposal foractiv… Dean Willis
- Re: [P2PSIP] Concepts document: proposalfor activ… Dean Willis
- RE: [P2PSIP] Concepts document: proposal for acti… Henry Sinnreich
- RE: [P2PSIP] Concepts document: proposal for acti… Henry Sinnreich
- Re: [P2PSIP] Concepts document: proposal for acti… Enrico Marocco
- Re: [P2PSIP] Concepts document: proposalfor activ… Greger V. Teigre
- RE: [P2PSIP] Concepts document: proposalfor activ… JiangXingFeng
- [P2PSIP] do we need a client protocol? Henry Sinnreich
- Re: [P2PSIP] do we need a client protocol? Alan Johnston
- Re: [P2PSIP] do we need a client protocol? Eunsoo Shim
- RE: [P2PSIP] do we need a client protocol? marcin.matuszewski
- RE: [P2PSIP] do we need a client protocol? David Barrett
- RE: [P2PSIP] do we need a client protocol? Henry Sinnreich
- RE: [P2PSIP] do we need a client protocol? David Barrett
- Re: [P2PSIP] do we need a client protocol? Philip Matthews
- RE: [P2PSIP] do we need a client protocol? marcin.matuszewski
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- Re: [P2PSIP] do we need a client protocol? Michal Giermasinski
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? HUANG Ping B
- RE: [P2PSIP] do we need a client protocol? Roy, Radhika R.
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? HUANG Ping B
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? marcin.matuszewski
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? HUANG Ping B
- RE: [P2PSIP] do we need a client protocol? Roy, Radhika R.
- Re: [P2PSIP] do we need a client protocol? Duan Chen
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? HUANG Ping B
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen
- RE: [P2PSIP] do we need a client protocol? HUANG Ping B
- RE: [P2PSIP] do we need a client protocol? Zheng Hewen