> From: Keith Moore <[EMAIL PROTECTED]> > I don't see what you're getting at. the outside sites may be running v4 > with a limited number of external addresses ... if they are running v6 > they will have plenty of external addresses. Not external *IPv4* addresses, they won't - which is what kind of addresses they need to communicate with other IPv4 sites. > if the remote sites are *only* running IPv4, having v6 locally won't > help much. ... it's generally true that if you're talking between a > v6-only and v4-only host you have to accept the limitations of NAT. That's the point I've been trying to make. Noel
- Re: draft-ietf-na... Masataka Ohta
- RE: draft-ietf-na... Brijesh Kumar
- Re: draft-ietf-na... Peter Deutsch in Mountain View
- Re: draft-ietf-na... Keith Moore
- Re: draft-ietf-na... Randy Bush
- RE: draft-ietf-na... mark.paton
- RE: draft-ietf-na... Randy Bush
- Re: draft-ietf-na... Keith Moore
- Re: draft-ietf-na... Masataka Ohta
- Re: draft-ietf-nat-protocol-compli... Eliot Lear
- Re: draft-ietf-nat-protocol-complications-0... J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complicati... Keith Moore
- Re: draft-ietf-nat-protocol-complications-0... Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-0... Sean Doran
- Re: draft-ietf-nat-protocol-complications-0... Sean Doran
- Re: draft-ietf-nat-protocol-complicati... Thomas Narten
- Re: draft-ietf-nat-protocol-complications-0... J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complicati... Tim Salo
- Re: draft-ietf-nat-protocol-complicati... Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-0... Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-0... Steven M. Bellovin