Re: IPv4
Keith Moore <moore@cs.utk.edu> Fri, 03 August 2007 03:42 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGo3L-0006CB-Id; Thu, 02 Aug 2007 23:42:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGo3J-0006C5-Oa for ietf@ietf.org; Thu, 02 Aug 2007 23:42:13 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGo3J-0003St-E1 for ietf@ietf.org; Thu, 02 Aug 2007 23:42:13 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 79E271EE308; Thu, 2 Aug 2007 23:42:08 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (bes.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JsX1ILKp6Ws7; Thu, 2 Aug 2007 23:42:06 -0400 (EDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id 19E441EE2E8; Thu, 2 Aug 2007 23:42:03 -0400 (EDT)
Message-ID: <46B2A40B.50408@cs.utk.edu>
Date: Thu, 02 Aug 2007 23:42:03 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <198A730C2044DE4A96749D13E167AD3701341D9A@MOU1WNEXMB04.vcorp.ad.vrsn.com> <3D14522E-A054-4503-87E3-1F1937BDF1F4@muada.com>
In-Reply-To: <3D14522E-A054-4503-87E3-1F1937BDF1F4@muada.com>
X-Enigmail-Version: 0.95.2
OpenPGP: id=E1473978
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ietf@ietf.org
Subject: Re: IPv4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
> NAT isn't the only answer to the question "I can't get IPv4 addresses, > what do I do?" Using IPv6 and a proxy to reach the IPv4 world is much, > much cleaner. And it also works from v4 to v6. We really should start > advocating this as the preferred transition mechanism. NAT and proxies are not mutually exclusive. There are advantages to having a proxy that can forward TCP and UDP traffic from an outside address/port to an inside address/port and vice versa; there are also advantages to a NAT that can do the same thing on a per-packet level. But a good, explicit protocol and API for doing each would be welcome. It would also be useful if the forwarder/NAT had explicit means of communicating the "external" source and destination address/port to the "internal" host - say via the same control protocol used to establish and maintain the address binding. That would make it relatively easy to, say, have a server inside an IPv6-only network establish presence on an IPv4 network provided by an ISP, while still allowing the application to see the real IPv4 source address (say for logging or spam filtering). The main thing is to avoid having "transparent NAT" - i.e. NATs that automatically establish address bindings and start forwarding packets - in IPv6. A lot of where NAT bites is when it tries to second-guess what the application is doing. (that goes double for DNS ALG). I'm not nearly so worried about IPv4-to-IPv6 NATs when the applications are explicitly aware of the NAT and explicitly manage the binding, and where the NAT doesn't try to muck with DNS. Keith _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Ream-Specific IP (Was: IPv4) Eric Burger
- RE: Charging I-Ds Hallam-Baker, Phillip
- RE: Charging I-Ds Peter Sherbin
- RE: Charging I-Ds Hallam-Baker, Phillip
- Re: Charging I-Ds Douglas Otis
- RE: Charging I-Ds Bob Braden
- RE: Charging I-Ds Richard Shockey
- Re: Charging I-Ds Keith Moore
- Re: Charging I-Ds Iljitsch van Beijnum
- RE: Charging I-Ds michael.dillon
- RE: Charging I-Ds Noel Chiappa
- Re: Charging I-Ds Stephane Bortzmeyer
- IPv4 Hallam-Baker, Phillip
- Re: IPv4 Iljitsch van Beijnum
- Re: IPv4 Douglas Otis
- Re: IPv4 Keith Moore
- RE: IPv4 Hallam-Baker, Phillip
- Re: IPv4 Iljitsch van Beijnum
- RE: IPv4 michael.dillon
- A prediction (was Re: IPv4) Arnt Gulbrandsen
- Ream-Specific IP (Was: IPv4) Julien Laganier