RE: [P2PSIP] Choice of STUN peer or TURN peer

JiangXingFeng <jiang.x.f@huawei.com> Mon, 28 January 2008 02:33 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 1JJJo7-000576-1h; Sun, 27 Jan 2008 21:33:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJJo5-00056R-Iy for p2psip@ietf.org; Sun, 27 Jan 2008 21:33:09 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJJo5-0004w2-3a for p2psip@ietf.org; Sun, 27 Jan 2008 21:33:09 -0500
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JVC005ZQ1Q149@szxga02-in.huawei.com> for p2psip@ietf.org; Mon, 28 Jan 2008 10:32:26 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JVC00ANZ1Q1SA@szxga02-in.huawei.com> for p2psip@ietf.org; Mon, 28 Jan 2008 10:32:25 +0800 (CST)
Received: from j36340 ([10.164.9.45]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JVC00N0D1Q13P@szxml04-in.huawei.com> for p2psip@ietf.org; Mon, 28 Jan 2008 10:32:25 +0800 (CST)
Date: Mon, 28 Jan 2008 10:32:24 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <174701c85f78$24a386b0$44a36b80@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <001501c86156$04a31ee0$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMAAECZOQAArhadAAEYVQEAB3Nztw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

> It seems useful to phase this for p2p-sip:  initially, just have
> p2p-sip nodes advertise their TURN servers if the p2p-sip node
> is not behind a NAT.
> 
> Once we know how to have p2p-sip TURN servers qualify their
> NAT's p2p-friendlyness, then can have p2p-sip nodes advertise
> those TURN servers, too.  If we make fast progress on a document
> that describes the qualification procedure, and running code
> that shows it works, we should be good to go.  No?


Yes. It is same to what I have in mind. First of all, we should determine
the p2psip node is not behind a NAT. 

Regard

JiangXingFeng



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