RE: [midcom] Port preservation

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

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