From owner-nat@portmasters.com  Wed Feb 21 12:20:39 2001
Received: from linux2.portmasters.com (root@ns2.jakes.org [12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03449
	for <nat-archive@odin.ietf.org>; Wed, 21 Feb 2001 12:20:34 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1LH7F419020
	for nat-outgoing; Wed, 21 Feb 2001 11:07:15 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Message-ID: <20010221170628.16991.qmail@web1406.mail.yahoo.com>
Date: Wed, 21 Feb 2001 09:06:28 -0800 (PST)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: (NAT) Fwd: REMINDER-Internet-Draft Cut-off Dates for Minneapolis IETF
To: nat@portmasters.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: Pyda Srisuresh <srisuresh@yahoo.com>


--- Natalie Syracuse <nsyracus@cnri.reston.va.us> wrote:
> To: IETF-Announce: ;
> Subject: REMINDER-Internet-Draft Cut-off Dates for Minneapolis IETF
> Date: Wed, 21 Feb 2001 06:51:14 -0500
> From: Natalie Syracuse <nsyracus@cnri.reston.va.us>
> 
> 
> NOTE: There are two (2) Internet-Draft Cut-off dates
> 
> February 23: Cut-off for Initial Submissions (new documents)
> 
> All initial submissions(-00) must be submitted by Friday,
> February 23, 17:00 US-EST. Initial submissions received after this time
> will NOT be made available in the Internet-Drafts directory, and will have
> to be resubmitted.
> 
> As before, all initial submissions (-00.txt) with a filename beginning
> with a draft-ietf MUST be approved by the appropriate WG Chair prior to
> processing and announcing. WG Chair approval must be received by
> Monday, February 26.
> 
> Please do NOT wait until the last minute to submit.
> 
> Be advised: NO placeholders. Updates to initial submissions received
>             the week of February 23 will NOT be accepted.
> 
> March 2: FINAL Internet-Draft Cut-off
> 
> All revised Internet-Draft submissions must be submitted by Friday,
> March 2, 2001 at 17:00 US-EST. Internet-Drafts received after this time
> will NOT be announced NOR made available in the Internet-Drafts
> Directories.
> 
> We will begin accepting Internet-Draft submissions the week of the
> meeting, though announcements will NOT be sent until the IETF meeting
> is over.
> 
> Thank you for your understanding and cooperation. Please do not hesitate
> to contact us if you have any questions or concenrs.
> 
> FYI: These and other significant dates can be found at
>       http://www.ietf.org/meetings/cutoff_dates_50.html
> 


=====


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/
-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


From owner-nat@portmasters.com  Fri Feb 23 19:00:19 2001
Received: from linux2.portmasters.com (root@ns2.jakes.org [12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27203
	for <nat-archive@odin.ietf.org>; Fri, 23 Feb 2001 19:00:18 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1NNnFo14438
	for nat-outgoing; Fri, 23 Feb 2001 17:49:15 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Message-ID: <20010223234824.10077.qmail@web1403.mail.yahoo.com>
Date: Fri, 23 Feb 2001 15:48:24 -0800 (PST)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: (NAT) NAT WG meeting time
To: nat@portmasters.com
Cc: Scott Bradner <sob@harvard.edu>, Allison Mankin <mankin@east.isi.edu>,
        Matt Holdrege <matt@ipverse.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: Pyda Srisuresh <srisuresh@yahoo.com>

Folks,

We are meeting for an hour as follows on Tuesday 03/20
at 15:45. Do let Matt and I know if there is a specific
item you wold like to include in the Agenda. Thanks.

TUESDAY, March 20, 2001

1515-1545 Break (Refreshments provided) - Grand Ballroom Foyer
1545-1645 Afternoon Sessions III
APP     provreg         Provisioning Registry Protocol WG
APP     nntpext         NNTP Extensions WG
GEN     ccamp           Common Control and Measurement Plane WG
INT     itrace          ICMP Traceback WG
OPS     sming           Next Generation Structure of Management Information WG
SEC     pkix            Public-Key Infrastructure WG
TSV     nat             Network Address Translators WG

cheers,
suresh





__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/
-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


From owner-nat@portmasters.com  Mon Feb 26 18:26:52 2001
Received: from linux2.portmasters.com (root@[12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03833
	for <nat-archive@odin.ietf.org>; Mon, 26 Feb 2001 18:26:51 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1QNDfN03929
	for nat-outgoing; Mon, 26 Feb 2001 17:13:41 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Message-ID: <3A9AE2D3.5CC8802E@senie.com>
Date: Mon, 26 Feb 2001 18:12:19 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: nat@portmasters.com
Subject: (NAT) draft-ietf-nat-app-guide-04.txt
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: Daniel Senie <dts@senie.com>
Content-Transfer-Encoding: 7bit

The latest revision just hit the repository. The deadline for updates to
existing drafts is actually this Friday. If there are any issues or
problems with this draft, I can try to get another revision submitted
before then.

I'd like to get this draft put to bed (i.e. ready for last call) by the
time we leave Minneapolis. Please get me any final comments.

Dan

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.                    http://www.amaranth.com
-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


From owner-nat@portmasters.com  Wed Feb 28 07:37:52 2001
Received: from linux2.portmasters.com (root@[12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03969
	for <nat-archive@odin.ietf.org>; Wed, 28 Feb 2001 07:37:51 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1SCTv121366
	for nat-outgoing; Wed, 28 Feb 2001 06:29:57 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Date: Mon, 28 Feb 2000 12:32:14 +0000
From: Tao Huang <sztaohuang@lycos.co.uk>
To: nat <nat@portmasters.com>
Subject: (NAT) how to implement NAT in Mobile IP?
X-mailer: FoxMail 3.1 [eg]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <6AD3946754E@broadstone.shef.ac.uk>
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: Tao Huang <sztaohuang@lycos.co.uk>
Content-Transfer-Encoding: 7bit

Hi, everybody

I have a question, how does NAT implement in mobile IP?  is there any solution( or product ) available to implement NAT in Mobile IP? Is it possible?

I spent a long time on searching the information about it and found a lot of questions simily like this without any answer. 

Any informations are welcome.

Regards,
Tao Huang
sztaohuang@lycos.co.uk

-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


From owner-nat@portmasters.com  Wed Feb 28 11:36:39 2001
Received: from linux2.portmasters.com (root@[12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11950
	for <nat-archive@odin.ietf.org>; Wed, 28 Feb 2001 11:36:38 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1SGQwv22968
	for nat-outgoing; Wed, 28 Feb 2001 10:26:58 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Message-ID: <3A9D0B3B.2353BCB3@hursley.ibm.com>
Date: Wed, 28 Feb 2001 08:29:15 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Tao Huang <sztaohuang@lycos.co.uk>
CC: nat <nat@portmasters.com>
Subject: Re: (NAT) how to implement NAT in Mobile IP?
References: <6AD3946754E@broadstone.shef.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Since Mobile IP depends on globally routable addresses, there is
a fundamental problem here. RFC 2993 and 3027 don't mention Mobile IP,
as a case that NAT can't handle, but probably should.

Thomas Narten said to me in private mail long ago:

> [Mobile IP] Registration Request/Reply messages which are sent
> between the mobile host and home agent include IP addresses in the UDP
> payload. In some cases, these messages are covered by an authentication
> header, so even a mobile-IP aware NAT box couldn't twiddle the bits.

   Brian

Tao Huang wrote:
> 
> Hi, everybody
> 
> I have a question, how does NAT implement in mobile IP?  is there any solution( or product ) available to implement NAT in Mobile IP? Is it possible?
> 
> I spent a long time on searching the information about it and found a lot of questions simily like this without any answer.
> 
> Any informations are welcome.
> 
> Regards,
> Tao Huang
> sztaohuang@lycos.co.uk


-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


From owner-nat@portmasters.com  Wed Feb 28 12:00:18 2001
Received: from linux2.portmasters.com (root@[12.96.1.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13226
	for <nat-archive@odin.ietf.org>; Wed, 28 Feb 2001 12:00:17 -0500 (EST)
Received: (from majordomo@localhost)
	by linux2.portmasters.com (8.11.1/8.11.1) id f1SGqe723294
	for nat-outgoing; Wed, 28 Feb 2001 10:52:40 -0600
X-Authentication-Warning: linux2.portmasters.com: majordomo set sender to owner-nat@portmasters.com using -f
Message-ID: <3A9D2CC0.147B07C0@sun.com>
Date: Wed, 28 Feb 2001 17:52:17 +0100
From: gabriel montenegro <gab@sun.com>
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian E Carpenter <brian@hursley.ibm.com>
CC: Tao Huang <sztaohuang@lycos.co.uk>, nat <nat@portmasters.com>
Subject: Re: (NAT) how to implement NAT in Mobile IP?
References: <6AD3946754E@broadstone.shef.ac.uk> <3A9D0B3B.2353BCB3@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nat@portmasters.com
Precedence: bulk
Reply-To: gabriel montenegro <gab@sun.com>
Content-Transfer-Encoding: 7bit

If what you're asking is how to handle private addresses, you might want to read
the appendix in http://www.ietf.org/rfc/rfc3024.txt
The folks at the National Univ of Singapore (http://mip.ee.nus.edu.sg/) also had some work (RATS),
although that link seems to be broken now.

-gabriel

-
To unsubscribe, email 'majordomo@portmasters.com' with
'unsubscribe nat' in the body of the message.
List archive: <URL:http://www.portmasters.com/archives/>


