Re: [midcom] Port preservation
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Tue, 27 April 2004 16:28 UTC
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10456 for <midcom-archive@odin.ietf.org>; Tue, 27 Apr 2004 12:28:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIVMK-0000iF-07 for midcom-archive@odin.ietf.org; Tue, 27 Apr 2004 12:23:00 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RGMxQ9002734 for midcom-archive@odin.ietf.org; Tue, 27 Apr 2004 12:22:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIV21-0003wT-Be; Tue, 27 Apr 2004 12:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIUrI-0000nO-HH for midcom@optimus.ietf.org; Tue, 27 Apr 2004 11:50:56 -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 LAA08419 for <midcom@ietf.org>; Tue, 27 Apr 2004 11:50:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIUrE-0007LR-VE for midcom@ietf.org; Tue, 27 Apr 2004 11:50:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIUqJ-0007J2-00 for midcom@ietf.org; Tue, 27 Apr 2004 11:49:55 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1BIUpc-0007EL-00 for midcom@ietf.org; Tue, 27 Apr 2004 11:49:12 -0400
Received: from dynamicsoft.com ([63.113.46.158]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i3RFmnus019250; Tue, 27 Apr 2004 11:48:49 -0400 (EDT)
Message-ID: <408E80CF.5080909@dynamicsoft.com>
Date: Tue, 27 Apr 2004 11:48:31 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Chris@sip1.com
CC: 'Cullen Jennings' <fluffy@cisco.com>, 'Yutaka Takeda' <takeday@pcrla.com>, 'Midcom' <midcom@ietf.org>, stun@www.vovida.org
Subject: Re: [midcom] Port preservation
References: <004e01c42c5d$191c4400$6402a8c0@HOME2>
In-Reply-To: <004e01c42c5d$191c4400$6402a8c0@HOME2>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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: 7bit
I think you are confusing two things. One is a client behind a nat speaking to a server on the public side. There, I think there are very, very few cases where the source port means anything (IKE is the only identified one there). The other case is a server running behind the NAT (i.e., on the private side), which is what you are talking about below. In such a case, I think you would use port forwarding configuration on the nat, and so port preservation on dynamically created bindings isnt applicable. -Jonathan R. Christopher A. Martin wrote: > I guess I should also state the port that I am describing is a listening > port (which is often also the source port) of the server being NATted, > while I am at it. > > -----Original Message----- > From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] On Behalf Of > Christopher A. Martin > Sent: Tuesday, April 27, 2004 8:09 AM > To: 'Cullen Jennings'; 'Jonathan Rosenberg' > Cc: 'Yutaka Takeda'; 'Midcom'; stun@www.vovida.org > Subject: RE: [midcom] Port preservation > > Ya, clients typically do use random ports, I am only speaking from a > server standpoint (Enterprises don't typically static nat a client). > > :) > > Chris > > -----Original Message----- > From: Cullen Jennings [mailto:fluffy@cisco.com] > Sent: Tuesday, April 27, 2004 12:37 AM > To: Chris@sip1.com; Jonathan Rosenberg > Cc: 'Yutaka Takeda'; Midcom; stun@www.vovida.org > Subject: Re: [midcom] Port preservation > > On 4/26/04 7:00 PM, "Christopher A. Martin" <chris@sip1.com> wrote: > > >>For clarity, common server ports in this example would be HTTP, SMTP, >>FTP, etc. > > > Well for TCP, the NATs don't muck with ports at all. The clients I have > for > HTTP, SMTP, FTP, also use source ports different than the destination > ports > so that the clients don't have to open a port under 1024 which would > require > them to be running as root. > > > > > _______________________________________________ > midcom mailing list > midcom@ietf.org > https://www1.ietf.org/mailman/listinfo/midcom > -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom
- [midcom] Port preservation Yutaka Takeda
- Re: [midcom] Port preservation Pyda Srisuresh
- RE: [midcom] Port preservation Yutaka Takeda
- Re: [midcom] Port preservation Cullen Jennings
- RE: [midcom] Port preservation Pyda Srisuresh
- RE: [midcom] Port preservation Christopher A. Martin
- Re: [midcom] Port preservation Jonathan Rosenberg
- RE: [midcom] Port preservation Christopher A. Martin
- RE: [midcom] Port preservation Christopher A. Martin
- Re: [midcom] Port preservation Cullen Jennings
- Re: [stun] Re: [midcom] Port preservation Cullen Jennings
- RE: [midcom] Port preservation Christopher A. Martin
- RE: [midcom] Port preservation Christopher A. Martin
- Re: [midcom] Port preservation Jonathan Rosenberg
- RE: [midcom] Port preservation Christopher A. Martin
- RE: [midcom] Port preservation Christopher A. Martin
- RE: [midcom] Port preservation Yutaka Takeda