Re: [BEHAVE] p2p applications using STUNT and EIM NATs for TCP

Dan Wing <dwing@cisco.com> Thu, 20 June 2013 03:50 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC02021E8086 for <behave@ietfa.amsl.com>; Wed, 19 Jun 2013 20:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.573
X-Spam-Level:
X-Spam-Status: No, score=-110.573 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4UziJ1S-3rNe for <behave@ietfa.amsl.com>; Wed, 19 Jun 2013 20:50:13 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0074021E8084 for <behave@ietf.org>; Wed, 19 Jun 2013 20:50:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4327; q=dns/txt; s=iport; t=1371700213; x=1372909813; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=5TN4Zeuc9bqx3WgNXvNSAh8rDGNNb7q2ds1jhZTf2Y4=; b=ixUVGtSOVLZVXM4X+B8A5lGJUTUoQ83CQN7kIgJMV6Ctpf3+cmVZHjlv Ot09sABZCzr/h9jsQhg8tK+cxfG5pK7lc8TLlcylhUjMH30t/FOP9F/Eg anIFTwaY8re/b3UUCxXrpe7bKXQTHch55X4uOnTkKABy5koRV1Mc4qnWO s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8FAIZ7wlGrRDoJ/2dsb2JhbABagwkxty+IOn0WdIIjAQEBAwEBAQFqAQsFCwsEQicwBhOICAUNvBWPQgcWgmphA4kgjiGBKZAbgy8c
X-IronPort-AV: E=Sophos; i="4.87,901,1363132800"; d="scan'208,217"; a="83945365"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 20 Jun 2013 03:50:12 +0000
Received: from sjc-vpn3-98.cisco.com (sjc-vpn3-98.cisco.com [10.21.64.98]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5K3oB2t029788; Thu, 20 Jun 2013 03:50:11 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_F8DEFBCA-523A-4EEF-BBD9-70E9CE77A714"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <cede1171c9c67a89094bab7eeadcadfa@cacaoweb.org>
Date: Wed, 19 Jun 2013 20:50:11 -0700
Message-Id: <6728C5CA-F1DD-4564-A218-E4809BF92B6F@cisco.com>
References: <cede1171c9c67a89094bab7eeadcadfa@cacaoweb.org>
To: <ivan@cacaoweb.org>
X-Mailer: Apple Mail (2.1508)
Cc: Behave <behave@ietf.org>
Subject: Re: [BEHAVE] p2p applications using STUNT and EIM NATs for TCP
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 03:50:17 -0000

On Jun 18, 2013, at 10:25 AM, ivan c <ivan@cacaoweb.org> wrote:

> Hello,
> 
> Does any of you has examples of applications that use a STUNT server together with an EIM NAT for TCP?
> 
> This is the single purpose (besides the convenience of the implementation) of having an EIM NAT in the first place: performing port prediction with the help of a STUNT server.
> 
I don't think you mean 'port prediction' where the software is trying to guess the next-used port ("predicting"), but I believe you mean learning the external IP address and TCP port (by talking to a TCP server on the Internet) and communicating that learned address/port to a rendezvous server of some kind (DNS server, SIP server, game server, whatever).

> Surprisingly, I am not aware of any applications that rely on that. All the p2p applications that I know of use different techniques for TCP Hole Punching or use other alternatives, such as UPnP, port forwarding, etc.
> 
I found this discussion of folks utilizing TCP hole punching (as I summarized above) for their projects, http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/d82f5cd9-b33c-4ea6-aeef-e489750021e4/tcp-simultaneous-open-for-tcp-hole-punching.

-d


> It would be important to somewhat quantify the usage of this technique in the wild.
> 
>  
> --
> 
> Ivan Chollet
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave