IETF Logo Mail Archive

Re: ike source port (was: issues with IKE that need resolution)

suresh@livingston.com (Pyda Srisuresh) Wed, 16 September 1998 16:19 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id MAA16231 for ipsec-outgoing; Wed, 16 Sep 1998 12:19:44 -0400 (EDT)
From: suresh@livingston.com
Message-Id: <199809161637.JAA21839@kc.livingston.com>
Subject: Re: ike source port (was: issues with IKE that need resolution)
To: bmanning@isi.edu
Date: Wed, 16 Sep 1998 09:37:54 -0700
Cc: suresh@livingston.com, crawdad@fnal.gov, ipsec@tis.com
In-Reply-To: <199809161627.AA02290@zed.isi.edu> from "bmanning@ISI.EDU" at Sep 16, 98 09:27:28 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

> 
> > > > To be clear, the NAT box Gabriel is refering to is a Host NAT server.
> > > > Host NAT server does not perform any address or port translation. 
> > > > Hope this helps.
> > > > 
> > > If so, then whence the term "NAT"?  Per RFC 1631 a NAT does address/port
> > > translation. 
> > > --bill
> > 
> > It is Host-NAT, not NAT.  A host in a private network, when connecting to 
> > end-hosts outside its realm, could adapt Host Network Address Translation 
> > to avoid network address translation of end-to-end packets. Such a host
> > is termed "Host NAT client". 
> > 
> > For details, I suggest, you refer NAR draft by Gabriel or the 
> > soon-to-be-posted draft-ietf-nat-terminology-01.txt. Thanks.
> > suresh
> 
> For some reason, I am having trouble pulling a local copy of the
> "soon-to-be-posted" draft-ietf-nat-terminology-01.txt :)
> 
> --bill
> 
It is not posted yet. It will be soon (in a couple of days).
Some minor editorial work is still under way. Thanks.

cheers,
suresh

v2.23.0 | Report a Bug | By Email