From mailman-admin@ietf.org  Wed Jan  1 10:15:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06881
	for <nat-archive@lists.ietf.org>; Wed, 1 Jan 2003 10:15:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01FNmJ29886
	for <nat-archive@lists.ietf.org>; Wed, 1 Jan 2003 10:23:48 -0500
Date: Wed, 01 Jan 2003 10:23:48 -0500
Message-ID: <20030101152348.32165.73403.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: nat-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, nat-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for nat-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
nat@ietf.org                             qLLL      
https://www1.ietf.org/mailman/options/nat/nat-archive%40lists.ietf.org


From nat-admin@ietf.org  Tue Jan 21 09:44:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01366
	for <nat-archive@lists.ietf.org>; Tue, 21 Jan 2003 09:44:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEwKJ21953;
	Tue, 21 Jan 2003 09:58:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEueJ21881
	for <nat@optimus.ietf.org>; Tue, 21 Jan 2003 09:56:40 -0500
Received: from icecom (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01218
	for <nat@ietf.org>; Tue, 21 Jan 2003 09:38:33 -0500 (EST)
From: roy@ice.co.cr
Received: from ice.co.cr (localhost [127.0.0.1])
 by icecom.ice.co.cr (iPlanet Messaging Server 5.2 HotFix 1.02 (built Sep 16
 2002)) with ESMTP id <0H92000VQJFCGD@icecom.ice.co.cr> for nat@ietf.org; Tue,
 21 Jan 2003 08:40:24 -0600 (CST)
Received: from [208.165.63.35] by icecom.ice.co.cr (mshttpd); Tue,
 21 Jan 2003 08:40:24 -0600
Date: Tue, 21 Jan 2003 08:40:24 -0600
To: nat@ietf.org
Message-id: <454d70e3.70e3454d@ice.co.cr>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.02 (built Sep 16 2002)
Content-type: multipart/mixed; boundary="Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)"
Content-language: en
X-Accept-Language: en
Priority: normal
Subject: [NAT] Nat parameters
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-Transfer-Encoding: 7BIT

Hi!

Just needed a hint of how many sessions of private IP Addr to a PUBLIC IP Addr should I considere when sizing my nat services m-to-1 scenarios?

Thanks a million to you all



--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)
Content-type: text/x-vcard; name=roy.vcf; charset=windows-1252
Content-disposition: attachment; filename=roy.vcf
Content-description: Card for <roy@ice.co.cr>
Content-Transfer-Encoding: 7BIT

begin:vcard
n:Campos;Roy
fn:Roy Campos
tel;cell:+ 506 381 5881
tel;fax:+ 506 276 5790
tel;home:+ 506 381 5881
tel;work:+ 506 243 6200
url:www.ice.co.cr
org:Instituto Costarricense de Electricidad;UENVA
adr:;;Avenida 2da Calle 1era;San Jose;San Jose;1000;Costa Rica
version:2.1
email;internet:roy@ice.co.cr
title:Consultoria IP
end:vcard


--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)--
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From nat-admin@ietf.org  Tue Jan 21 10:29:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02439
	for <nat-archive@lists.ietf.org>; Tue, 21 Jan 2003 10:29:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LFj9J25550;
	Tue, 21 Jan 2003 10:45:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LFhqJ25387
	for <nat@optimus.ietf.org>; Tue, 21 Jan 2003 10:43:52 -0500
Received: from dgesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02335
	for <nat@ietf.org>; Tue, 21 Jan 2003 10:25:47 -0500 (EST)
Received: from dgismtp06.wcomnet.com ([166.38.58.89])
 by firewall.wcom.com (Iplanet MTA)
 with ESMTP id <0H9200HHULKKKK@firewall.wcom.com> for nat@ietf.org; Tue,
 21 Jan 2003 15:26:44 +0000 (GMT)
Received: from dgismtp06.wcomnet.com by dgismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H9200G01LFDK2@dgismtp06.wcomnet.com>; Tue,
 21 Jan 2003 15:26:44 +0000 (GMT)
Received: from ws041v4569 ([166.35.139.149])
 by dgismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H9200GGVLK388@dgismtp06.wcomnet.com>; Tue,
 21 Jan 2003 15:26:27 +0000 (GMT)
Date: Tue, 21 Jan 2003 09:26:40 -0600
From: "Christopher A. Martin" <christopher.a.martin@wcom.com>
Subject: RE: [NAT] Nat parameters
In-reply-to: <454d70e3.70e3454d@ice.co.cr>
To: roy@ice.co.cr, nat@ietf.org
Message-id: <009201c2c161$7f2317f0$0a00a8c0@ws041v4569>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This is really dependant on the hardware platform and physical resources
available to it. 

IMHO, you have a theoretical max of 65535, and if you have any
specialized services (www,smtp,sip,h323,etc.) that require pools for
inbound connections for instance, then it will need to be worked around
for that too. It all depends on what you will be offering with the
product and sizing accordingly. I would recommend a configurable range
and a static range (for those specialized services and possible port
forwarding, for example).

Chris

-----Original Message-----
From: nat-admin@ietf.org [mailto:nat-admin@ietf.org] On Behalf Of
roy@ice.co.cr
Sent: Tuesday, January 21, 2003 8:40 AM
To: nat@ietf.org
Subject: [NAT] Nat parameters


Hi!

Just needed a hint of how many sessions of private IP Addr to a PUBLIC
IP Addr should I considere when sizing my nat services m-to-1 scenarios?

Thanks a million to you all



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


From mailnull@www1.ietf.org  Tue Jan 21 10:42:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01368
	for <nat-archive@odin.ietf.org>; Tue, 21 Jan 2003 09:44:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LF2DN22125
	for nat-archive@odin.ietf.org; Tue, 21 Jan 2003 10:02:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEwKJ21953;
	Tue, 21 Jan 2003 09:58:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEueJ21881
	for <nat@optimus.ietf.org>; Tue, 21 Jan 2003 09:56:40 -0500
Received: from icecom (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01218
	for <nat@ietf.org>; Tue, 21 Jan 2003 09:38:33 -0500 (EST)
From: roy@ice.co.cr
Received: from ice.co.cr (localhost [127.0.0.1])
 by icecom.ice.co.cr (iPlanet Messaging Server 5.2 HotFix 1.02 (built Sep 16
 2002)) with ESMTP id <0H92000VQJFCGD@icecom.ice.co.cr> for nat@ietf.org; Tue,
 21 Jan 2003 08:40:24 -0600 (CST)
Received: from [208.165.63.35] by icecom.ice.co.cr (mshttpd); Tue,
 21 Jan 2003 08:40:24 -0600
Date: Tue, 21 Jan 2003 08:40:24 -0600
To: nat@ietf.org
Message-id: <454d70e3.70e3454d@ice.co.cr>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.02 (built Sep 16 2002)
Content-type: multipart/mixed; boundary="Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)"
Content-language: en
X-Accept-Language: en
Priority: normal
Subject: [NAT] Nat parameters
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-Transfer-Encoding: 7BIT

Hi!

Just needed a hint of how many sessions of private IP Addr to a PUBLIC IP Addr should I considere when sizing my nat services m-to-1 scenarios?

Thanks a million to you all



--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)
Content-type: text/x-vcard; name=roy.vcf; charset=windows-1252
Content-disposition: attachment; filename=roy.vcf
Content-description: Card for <roy@ice.co.cr>
Content-Transfer-Encoding: 7BIT

begin:vcard
n:Campos;Roy
fn:Roy Campos
tel;cell:+ 506 381 5881
tel;fax:+ 506 276 5790
tel;home:+ 506 381 5881
tel;work:+ 506 243 6200
url:www.ice.co.cr
org:Instituto Costarricense de Electricidad;UENVA
adr:;;Avenida 2da Calle 1era;San Jose;San Jose;1000;Costa Rica
version:2.1
email;internet:roy@ice.co.cr
title:Consultoria IP
end:vcard


--Boundary_(ID_3ZJawIkWn89GXINyn/6cJA)--
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From mailnull@www1.ietf.org  Tue Jan 21 11:27:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02441
	for <nat-archive@odin.ietf.org>; Tue, 21 Jan 2003 10:29:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0LFkrx25629
	for nat-archive@odin.ietf.org; Tue, 21 Jan 2003 10:46:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LFj9J25550;
	Tue, 21 Jan 2003 10:45:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LFhqJ25387
	for <nat@optimus.ietf.org>; Tue, 21 Jan 2003 10:43:52 -0500
Received: from dgesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02335
	for <nat@ietf.org>; Tue, 21 Jan 2003 10:25:47 -0500 (EST)
Received: from dgismtp06.wcomnet.com ([166.38.58.89])
 by firewall.wcom.com (Iplanet MTA)
 with ESMTP id <0H9200HHULKKKK@firewall.wcom.com> for nat@ietf.org; Tue,
 21 Jan 2003 15:26:44 +0000 (GMT)
Received: from dgismtp06.wcomnet.com by dgismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H9200G01LFDK2@dgismtp06.wcomnet.com>; Tue,
 21 Jan 2003 15:26:44 +0000 (GMT)
Received: from ws041v4569 ([166.35.139.149])
 by dgismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H9200GGVLK388@dgismtp06.wcomnet.com>; Tue,
 21 Jan 2003 15:26:27 +0000 (GMT)
Date: Tue, 21 Jan 2003 09:26:40 -0600
From: "Christopher A. Martin" <christopher.a.martin@wcom.com>
Subject: RE: [NAT] Nat parameters
In-reply-to: <454d70e3.70e3454d@ice.co.cr>
To: roy@ice.co.cr, nat@ietf.org
Message-id: <009201c2c161$7f2317f0$0a00a8c0@ws041v4569>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This is really dependant on the hardware platform and physical resources
available to it. 

IMHO, you have a theoretical max of 65535, and if you have any
specialized services (www,smtp,sip,h323,etc.) that require pools for
inbound connections for instance, then it will need to be worked around
for that too. It all depends on what you will be offering with the
product and sizing accordingly. I would recommend a configurable range
and a static range (for those specialized services and possible port
forwarding, for example).

Chris

-----Original Message-----
From: nat-admin@ietf.org [mailto:nat-admin@ietf.org] On Behalf Of
roy@ice.co.cr
Sent: Tuesday, January 21, 2003 8:40 AM
To: nat@ietf.org
Subject: [NAT] Nat parameters


Hi!

Just needed a hint of how many sessions of private IP Addr to a PUBLIC
IP Addr should I considere when sizing my nat services m-to-1 scenarios?

Thanks a million to you all



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



