*> *> The problem is not to make applications "NAT aware" or "NAT friendly". The *> problem is to make applications "IP address unaware". What is an *> application doing exchanging and using names for things 2 layers below it? *> Sounds like a design for trouble if I ever heard of one. I don't believe this argument, John. The IP address is (part of) the transport layer end point address, something that an application can reasonably be expected to know about in the existing Internet architecture. Bob Braden
- Re: IP network address assign... John Stracke
- Re: IP network address assign... Matt Holdrege
- Re: IP network address assign... Keith Moore
- Re: IP network address assign... Bill Manning
- Re: IP network address assign... Tripp Lilley
- Re: IP network address assign... Brian E Carpenter
- Re: IP network address assign... Keith Moore
- Re: IP network address assignment... Randy Bush
- Re: IP network address assign... Matt Crawford
- Re: IP network address assignments/allocations inf... Valdis . Kletnieks
- Re: IP network address assignments/allocations informat... Bob Braden
- Re: IP network address assignments/allocations inf... Brian E Carpenter
- RE: IP network address assignments/allocations informat... Michael Welzl
- Re: IP network address assignments/allocations informat... Bob Braden
- Re: IP network address assignments/allocations informat... Tony Dal Santo
- Re: IP network address assignments/allocations informat... J. Noel Chiappa
- Re: IP network address assignments/allocations inf... Jon Crowcroft
- RE: IP network address assignments/allocations informat... Ian King
- Re: IP network address assignments/allocations inf... Perry E. Metzger
- Re: IP network address assignments/allocations informat... J. Noel Chiappa