[ppml] NANOG IPv4 Exhaustion BoF
John Curran
jcurran at istaff.org
Fri Mar 7 11:47:47 EST 2008
- Previous message: [ppml] NANOG IPv4 Exhaustion BoF
- Next message: [ppml] NANOG IPv4 Exhaustion BoF
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 8:37 AM -0800 3/7/08, David Conrad wrote: >Ignoring the fact that the vast majority of customers will not be bringing their own blocks (they will instead be connecting via a (perhaps multi-layered) NAT and thus not contribute to the routing load), there will be back pressure on "transfers" of such long prefixes simply because they won't get you where you need to go. If the customers servers requiring unique addresses are covered by some PA assigned space, that's true. When ISP's can't find more address space to use for this purpose, then you'll see customer-provided blocks being routed instead or customers being turned down for IPv4 services, which will lead them to an ISP which will accept & try to route them... The ISP's who try not to pollute end up having to reject the new customer, and then again not accept their route when another ISP takes up the same customer. The ISP who takes the customer and tries to route them to the peers gets the revenue and simply redirects any connectivity blame to the well-behaved ISP for 'needlessly' filtering. (This, btw, is mirrors the dialog that went down during some of the earlier peering/filtering ISP wars...) /John
- Previous message: [ppml] NANOG IPv4 Exhaustion BoF
- Next message: [ppml] NANOG IPv4 Exhaustion BoF
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the PPML mailing list