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

Cullen Jennings <fluffy@cisco.com> Fri, 01 February 2008 04:42 UTC

Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E50B028C149; Thu, 31 Jan 2008 20:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level:
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cA-AjzYDpLun; Thu, 31 Jan 2008 20:42:59 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 287E428C180; Thu, 31 Jan 2008 20:42:59 -0800 (PST)
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8006328C187 for <p2psip@core3.amsl.com>; Thu, 31 Jan 2008 20:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhpDH4v+wVyJ for <p2psip@core3.amsl.com>; Thu, 31 Jan 2008 20:42:56 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id BC6C328C180 for <p2psip@ietf.org>; Thu, 31 Jan 2008 20:42:56 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 31 Jan 2008 20:44:30 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m114iU8n017355; Thu, 31 Jan 2008 20:44:30 -0800
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-5.cisco.com (8.12.10/8.12.6) with SMTP id m114iSqX004936; Fri, 1 Feb 2008 04:44:28 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <174701c85f78$24a386b0$44a36b80@cisco.com> <001501c86156$04a31ee0$2d09a40a@china.huawei.com> <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
Message-Id: <0B983815-ED15-419D-9F59-47EFC094995E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 31 Jan 2008 20:44:07 -0800
X-Mailer: Apple Mail (2.915)
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

On Jan 28, 2008, at 8:01 AM, Bruce Lowekamp wrote:

> But otherwise, the TURN
> protocol seems to work as is.  For the purposes of a TURN server, a
> NAT having endpoint independent mapping seems to be the only real
> requirement on the NAT

Agree on that but ...
I think the hard part we have not fully solved yet is how a peer that  
is thinking of being a TURN server is going to detect if this is the  
case or not.
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip
From p2psip-bounces@ietf.org  Thu Jan 31 23:02:12 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 130EC3A6840;
	Thu, 31 Jan 2008 23:02:12 -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 core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CIxaj8xREmA4; Thu, 31 Jan 2008 23:02:11 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2714D3A6812;
	Thu, 31 Jan 2008 23:02:11 -0800 (PST)
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C1E5E3A6812
	for <p2psip@core3.amsl.com>om>; Thu, 31 Jan 2008 23:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iZFh0adp2jkn for <p2psip@core3.amsl.com>om>;
	Thu, 31 Jan 2008 23:02:09 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id D61EE3A680A
	for <p2psip@ietf.org>rg>; Thu, 31 Jan 2008 23:02:08 -0800 (PST)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVJ007UNSY5PO@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:41 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVJ00BB2SXXCL@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:41 +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 <0JVJ00D9ESXX8W@szxml04-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:33 +0800 (CST)
Date: Fri, 01 Feb 2008 15:03:33 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
In-reply-to: <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
To: 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <002101c864a0$8f1ac3a0$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Thread-index: AchhxwRiKwoxy6LaSZ6TgKaHnj8wdgC2F6bg
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hi, Bruce:

Sorry for late response. See inline. 

--
Jiang XingFeng

> -----Original Message-----
> 
> > >
> > >   TURN client         STUN server          NAT  TURN server
> > >        |                   |                |      |
> > >  1.    |------give me a TURN address------->|----->|
> > >  2.    |                   |<--STUN Request--------|
> > >  3.    |                   |-STUN Response->|----->|
> > >  4.    |<-----here is your TURN address------------|
> > >
> 
> If we allow a TURN server to be behind a NAT, then the only change I
> would see necessary would that 1 and 4 would have to be routed over
> the overlay (a reload tunnel, for example).  But otherwise, the TURN
> protocol seems to work as is.  For the purposes of a TURN server, a
> NAT having endpoint independent mapping seems to be the only real
> requirement on the NAT as long as the two voice endpoints support ICE;
> the connectivity checks should take care of any form of filtering the
> NAT uses.

While TURN client in question gets its relayed address from the TURN server,
it will exchange them with its peer, say B. According to the connectivity
check in ICE, B and ICE will send message to try to find direct connection. 

So if B send the message destined to the relayed address first, it will be
filtered by the TURN server. Then TURN client sends a message destined to
the B's candidate, it will send the message through the TURN server. But in
the message 1 reached the TURN server in a hop-by-hop way, if the message is
sent directly to the TURN server, it will be filtered. If the message is
sent in a hop-by-hop way through the overlay, the immediate peer to the STUN
server may change over time, so the message may also be filtered. Am I
missing something? 


Regards!

JiangXingFeng

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip
From p2psip-bounces@ietf.org  Thu Jan 31 23:20:21 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 664AA3A6854;
	Thu, 31 Jan 2008 23:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TZ4rGDOHfaKW; Thu, 31 Jan 2008 23:20:20 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 946873A6811;
	Thu, 31 Jan 2008 23:20:20 -0800 (PST)
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85ED33A680A
	for <p2psip@core3.amsl.com>om>; Thu, 31 Jan 2008 23:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cJOcJkTgiq6A for <p2psip@core3.amsl.com>om>;
	Thu, 31 Jan 2008 23:20:18 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id 945DC3A6811
	for <p2psip@ietf.org>rg>; Thu, 31 Jan 2008 23:20:18 -0800 (PST)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVJ007A7TSEPO@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:50 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVJ00A6GTSDYC@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:50 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVJ00D38TSD8W@szxml04-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:49 +0800 (CST)
Date: Fri, 01 Feb 2008 15:21:49 +0800
From: Song Yongchao <melodysong@huawei.com>
In-reply-to: <0B983815-ED15-419D-9F59-47EFC094995E@cisco.com>
To: 'Cullen Jennings' <fluffy@cisco.com>om>,
	'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAFv5pjyAF5tIpzg0AE9h2Q8BAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AchkjSjvQqR3LNQzQrWRrcJxx0588gAEzSEA
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

See inline
> On Jan 28, 2008, at 8:01 AM, Bruce Lowekamp wrote:
> > But otherwise, the TURN
> > protocol seems to work as is.  For the purposes of a TURN server, a
> > NAT having endpoint independent mapping seems to be the only real
> > requirement on the NAT
> 
> Agree on that but ...
> I think the hard part we have not fully solved yet is how a peer that
> is thinking of being a TURN server is going to detect if this is the
> case or not.

In that case,each peer that is willing to be the TURN server must dialog
with several STUN servers with public address to detect its NAT mapping
type, only peers with public addresses or behind endpoint independent NATs
could be TURN servers. However, STUN servers may be behind NAT either, in
the worst case, it may be behind the same outermost NAT with the peer, and
these STUN servers response different reflexive addresses with the public
STUN servers. So, in that case STUN servers must be classified in to public
addressed and non-public addressed, and the peer willing to be the TURN
server must dialog with public addressed STUN servers to detect its NAT
mapping type.

For the simplicity, I think we should only admit peers with public addresses
to be the TURN servers at the first step.

> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> http://www.ietf.org/mailman/listinfo/p2psip

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip