[ppml] IPv6 flawed?

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


>>>>> "Kevin" == Kevin Kargel <kkargel at polartel.com> writes:
    Kevin> I still don't understand the controversy about private IPv6 space.  My
    Kevin> IPv6 allocation is plenty big.  If I want a private section of it all I
    Kevin> have to do is set an access list for it in my edge routers denying
    Kevin> traffic for that subnet in or out of my network.  Voila, I have a
    Kevin> private network.

  Yes, and that's precisely what I want to do.
  (Except that most of the space will be initially private, with some if
possibly being accessible to some places to do exactly that... get
updates in an emergency, when some other internal update server is
broken)
  The problem is that I can't, under the current policy, even get a /48
of space, if I didn't previously qualify for a v4 allocation. 
  (This is greenfield deployment, which is one reason I can think about
just using IPv6...)

- -- 
Michael Richardson <mcr at xdsinc.net>
XDS Inc, Ottawa, ON             
Personal: http://www.sandelman.ca/mcr/ 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQDVAwUBRumTnu0sRu40D6vCAQKHcAYAgs/6ijzLIMRNwLShua/rNgVt1DyvBr6e
kzusATLc713iznynbVSE3RIGtmDglnegg6+RWmgLP/XnB51EK4sWE/6MktGvCtzm
gLQc03j0Llc13+6+cIcIeJFoLh+DV9Od+tIqpl7mpRqi2tiT888xZvir2xISemJZ
EUAw+8fnH+S783hRk8r7qrACdpEAv24BTtsUwnak1D/IG5RZWt+7exp8oSuVcMH3
t0D07V1tYMeImD0Q/2e0QyaIgem/SZE4
=5vay
-----END PGP SIGNATURE-----