[ppml] Proposed Policy: IPv4 Micro-allocations for anycast services

[Leo Bicknell]

I like the concept behind this policy, that is to say we shouldn't
make it hard to deploy anycast services.

My concern though is does the policy as written open up the floodgates
and/or create loopholes with great abound.  Meeting the requirements
as listed is not hard.  What happens if people end up not using
these blocks for anycast services, but rather just as unicast blocks?
Does the community really want to open up anycast to a wide spectrum
of people, when the technique is full of pitfalls (for instance,
TCP applications don't always work so well)?  If someone has multiple
services out of the same POP's, can each service have any anycast block,
or only one per company?

I haven't yet formed a full opinion one way or the other, but I do
think some tigher controls would make me much happer, personally.

-- 
       Leo Bicknell - bicknell at ufp.org - CCIE 3440
        PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request at tmbg.org, www.tmbg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20050810/f86c9be8/attachment.sig>