IETF Logo Mail Archive

[P2PSIP] Next steps on draft-willis-p2psip-concepts-04

Spencer Dawkins <spencer@mcsr-labs.org> Fri, 20 April 2007 21:28 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 1Hf0eQ-0003td-TM; Fri, 20 Apr 2007 17:28:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hf0eP-0003tS-AG for p2psip@ietf.org; Fri, 20 Apr 2007 17:28:17 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hf0eO-0003ZL-3e for p2psip@ietf.org; Fri, 20 Apr 2007 17:28:17 -0400
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JGT00KKDFN3D4@usaga01-in.huawei.com> for p2psip@ietf.org; Fri, 20 Apr 2007 14:28:15 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JGT00FO1FN1AL@usaga01-in.huawei.com> for p2psip@ietf.org; Fri, 20 Apr 2007 14:28:15 -0700 (PDT)
Date: Fri, 20 Apr 2007 16:26:53 -0500
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: P2PSIP Mailing List <p2psip@ietf.org>
Message-id: <1e2101c78392$9dca8e70$ad600240@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [P2PSIP] Next steps on draft-willis-p2psip-concepts-04
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

Dear P2PSIP Concepts and Terminology draft authors,

I'm looking at draft-willis-p2psip-concepts-04 and seeing

9.  Open Issues

   Here are some open issues in this document:

   1.  The word "service" is being overloaded to refer both to what the
       overlay provides (distributed location service, distributed
       transport service) and what an individual peer or client
       provides.  How can we fix this?

   2.  Does P2PSIP provide a distributed location service or an
       alternative mechanism to RFC 3263?  The answer seems to be both,
       but what is the relationship between these?

Does this look like your current open issues list, post-Prague? I'm almost 
sure we have an open issue about clients, for instance...

How do you/we plan to move forward on this draft?

Thanks,

Spencer 



_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip

v2.23.0 | Report a Bug | By Email