[e2e] NAT traversal for src+dst routing

[Joe Touch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jon Crowcroft wrote:
| File this under
| Truly Horrible Idea/Concept/Kludge (T.H.I.C.K.)
|
| reading some stuff recently about how MPLS can be used to do various
| traffic engineering hacks that "cannot" be done  with normal IP
| forwarding as it would need source+destination, which we "know" doesnt
| scale (if there's an algorithm for labels, i dont quite see why an
| algorithm for fast longest prefix packet classification doesnt just
| double in time/space for src+dst given both are in the FIB anyhow, but
| hey...)
|
| so i was also reading about various cute NAT traversal hacks (many
| aimed at allowing incoming SIP signaling for end-customer VOIP calls
| etc....

Many of these assume that the NAT conforms to a standard, notably one
that exposes
	a) the fact that there _is_ a NAT
	b) the fact that there are multiple machines behind a NAT

Both of these are things that some NAT users and many NAT designers want
to deliberately obfuscate.

I.e., cute traversal hacks work fine when the NAT _wants_ to be found,
but they fail exactly where - and why - most NATs are actually deployed,
IMO.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBilrmE5f5cImnZrsRAkDbAKDCSEjYOwco1dfC+LeCuKO1Z+kAUwCfTRmf
tZsiVfWxRQ+7LijGV+iOVws=
=UhgZ
-----END PGP SIGNATURE-----