IETF Logo Mail Archive

Re: [P2PSIP] Comments on draft-marocco-p2psip-interwork-01

Enrico Marocco <enrico.marocco@telecomitalia.it> Tue, 22 May 2007 08:17 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 1HqPYm-0007B5-S4; Tue, 22 May 2007 04:17:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqPYk-0007At-MS for p2psip@ietf.org; Tue, 22 May 2007 04:17:34 -0400
Received: from mailf.telecomitalia.it ([156.54.233.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqPYi-0000mG-H2 for p2psip@ietf.org; Tue, 22 May 2007 04:17:34 -0400
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 10:17:31 +0200
Received: from PTPXCH029BA020.idc.cww.telecomitalia.it ([156.54.240.46]) by ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 10:17:30 +0200
Received: from [127.0.0.1] ([163.162.180.246]) by PTPXCH029BA020.idc.cww.telecomitalia.it over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 10:17:29 +0200
Message-ID: <4652A758.7040809@telecomitalia.it>
Date: Tue, 22 May 2007 10:18:32 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Icedove 1.5.0.10 (X11/20070329)
MIME-Version: 1.0
To: JiangXingFeng <jiang.x.f@huawei.com>
Subject: Re: [P2PSIP] Comments on draft-marocco-p2psip-interwork-01
References: <000501c79c44$47423920$6905a40a@china.huawei.com>
In-Reply-To: <000501c79c44$47423920$6905a40a@china.huawei.com>
X-Enigmail-Version: 0.94.2.0
X-OriginalArrivalTime: 22 May 2007 08:17:29.0985 (UTC) FILETIME=[A3E8FF10:01C79C49]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
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 <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>
Content-Type: multipart/mixed; boundary="===============0327891936=="
Errors-To: p2psip-bounces@ietf.org

JiangXingFeng wrote:
> In Philip's draft-matthews-p2psip-bootstrap-mechanisms-00, a bootstrap
> mechanism named bootstrap server mechanism is proposed. It proposes the
> bootstrap server is a SIP registrar and proxy server. I have a question
> here, if the bootstrap server has all of UA contact locations, why not using
> conventional SIP directly? 

It hasn't.  It acts just as a front-end for the overlay, storing and
retrieving locations in the distributed database.

> So I think a Dynamic DNS may be an alterative choice for bootstrap server
> because of its generality. The problems that lies in DDNS mechanism are: 1.
> how does the method keep the consistence because of peers' churn. 2. Which
> subset of peers could be granted to register with DNS? If all peers has
> right to do registration with DNS on behalf of the overlay, DNS database
> will be populated with a lot of redundant data and receive a lot of request
> and will bring security threat to DNS.  

Registrations of peers -- proxy, bootstrap or whatever -- into DNS are
an open issue; it is critical if they are regulated by policies both too
restrictive and too permissive. The draft tries to point it out in
section 3.1.1 ("Insertion into DNS").

-- 
Ciao,
Enrico


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

v2.23.0 | Report a Bug | By Email