-----BEGIN PGP SIGNED MESSAGE-----
"Jon" == Jon Allen Boone <ipmonger(_at_)delamancha(_dot_)org> writes:
>> IPv6 and IPv4 allocation policies are different.
>>
>> We just had this thread on NANOG. I think it's v6 policy myth
>> month, or something :-)
>>
Jon> And non-ISPs [the folks whom some think IPv6 can successfully
Jon> be deployed w/out help from the ISPs] get them exactly how?
a) from their ISP. IPv6 contains no provider-independant addressing
at this point.
b) by using 6to4, they get their own /48.
If your ISP doesn't have IPv6, then they won't have addresses, so
you'll need a tunnel solution anyway. 6to4 is very good for this.
One successful method that I've used is to get a tunnel from he.net,
set up the BGP listening, and use that tunnel for all 2001: addresses.
Run your own 6to4 converter at the edge.
(Better to get a geographically significant tunnel, which I do elsewhere)
That way, one routes through the tunnel to the 6bone, sending one's
2002: sourced data, which others then send back using whatever their
topologically closest 6to4 router. The irony is that, given sparse IPv6
network, 6to4 addresses most closely follow the topology, since they
follow the IPv4 network.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr(_at_)xelerance(_dot_)com http://www.sandelman.ottawa.on.ca/mcr/
|device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQZ1cGYqHRg3pndX9AQFBjgP+Jl2px3sK/iPOb7lBdxdFQu46wV6Kb1GJ
QXn3Wsq/lAQgGathSpgQGaqwYI2/bqJykp72ow73Hcq6M9woLNBlsRFr/emQ5QGx
NdUxhWj2mFWh+jAeaTwOXzqGwaJXYn2qx7j4+hpeuXUN7IFVkfPxG1Woix2Nd436
k9RJ2X49No0=
=TkvV
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf