RE: [midcom] Port preservation

"Yutaka Takeda" <takeday@pcrla.com> Sat, 24 April 2004 00:27 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24926 for <midcom-archive@odin.ietf.org>; Fri, 23 Apr 2004 20:27:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHAoS-0003bz-Rm for midcom-archive@odin.ietf.org; Fri, 23 Apr 2004 20:14:33 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3O0EWQU013860 for midcom-archive@odin.ietf.org; Fri, 23 Apr 2004 20:14:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHAjE-0002CH-M4; Fri, 23 Apr 2004 20:09:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHAcw-00089b-Lp for midcom@optimus.ietf.org; Fri, 23 Apr 2004 20:02:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23873 for <midcom@ietf.org>; Fri, 23 Apr 2004 20:02:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BHAcu-0001Eo-OI for midcom@ietf.org; Fri, 23 Apr 2004 20:02:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BHAc2-0000yY-00 for midcom@ietf.org; Fri, 23 Apr 2004 20:01:43 -0400
Received: from 67.105.118.114.ptr.us.xo.net ([67.105.118.114] helo=mail.kmerl.com) by ietf-mx with esmtp (Exim 4.12) id 1BHAbV-0000cg-00 for midcom@ietf.org; Fri, 23 Apr 2004 20:01:09 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [midcom] Port preservation
x-mimeole: Produced By Microsoft Exchange V6.0.6249.0
Date: Fri, 23 Apr 2004 17:00:38 -0700
Message-ID: <B002AA5B97382E40935F83502A566F20010CB1@mail.kmerl.com>
Thread-Topic: [midcom] Port preservation
Thread-Index: AcQph0E+s1u4TWDDQ9C7T5Z7UvgXTAAAo7Qg
From: Yutaka Takeda <takeday@pcrla.com>
To: Pyda Srisuresh <srisuresh@yahoo.com>, Midcom <midcom@ietf.org>, stun@www.vovida.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

I see.

There is one more question.
Looking at the Cullen's STUN test result, all the port preservation 
NATs are of a cone NAT as primary behavior. Do you think there is
a reason for that? I mean, if it is 'desirable' to have a certain
port number on the NAT, and a host can talk to *multiple* hosts on 
the port number...?

Thanks,
Yutaka


> -----Original Message-----
> From: Pyda Srisuresh [mailto:srisuresh@yahoo.com]
> Sent: Friday, April 23, 2004 4:04 PM
> To: Yutaka Takeda; Midcom; stun@www.vovida.org
> Subject: Re: [midcom] Port preservation
> 
> 
> Port preservation is desirable in some limited cases where 
> applications and
> protocols require a certain number to be used for source 
> and/or destination.
> ex: IKE-v1 assumes UDP port 500 on both src and dest.
> 
> cheers,
> suresh
>  
> --- Yutaka Takeda <takeday@pcrla.com> wrote:
> > 
> > Does anyone know what the real motivation for NAT designers to 
> > implement the port preservation[1] is? Is there an actual service 
> > or application that depends on this behavior? I just realized that 
> > I know such NATs exist but why...
> > 
> > [1]
> > 
> http://www.ietf.org/internet-drafts/draft-jennings-midcom-stun
> -results-00.txt
> > 
> > Yutaka
> > 
> > _______________________________________________
> > midcom mailing list
> > midcom@ietf.org
> > https://www1.ietf.org/mailman/listinfo/midcom
> 
> 
> =====
> 
> 

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