[arin-ppml] FW: IPv6 Non-connected networks

[Matthew Kaufman]

I was conflating the two threads. If you read my point about your /48  
(or /56 or whatever the "cheap and easy" size of GUA will be) of PI  
GUA as not being accepted by your (or any) ISP, then it might make  
more sense.

I agree with your point that you wouldn't split a PI block up just to  
leave a hole of local space in the middle.

Matthew Kaufman

(Sent from my iPhone, thank the poor UI for the top-posting)

On Mar 29, 2010, at 8:54 AM, Kevin Kargel <kkargel at polartel.com> wrote:

> That's an entirely different problem.  Sounds to me like you need a  
> different ISP.
>
> Nobody, especially me, is suggesting anyone announce a /119.  I am  
> not going to try to advertise a /28 of IPv4 space either.
>
> It is just like the IPv4 space you have now.  You cannot tell me  
> that every IPv4 address in your advertised space is routed and  
> reachable right now.  I know that I have specific addresses blocked  
> at my edge or otherwise blackholed and I have not broken up my BGP  
> announcements to account for them.  I suspect that if I ran a port  
> scan across your space some addresses would be unresponsive.
>
> It would be bad practice to break an IPv4 /19 (for example) into a  
> multitude of smaller blocks because of one IP address in the middle  
> that you didn't want to route.  It is the same for IPv6.
>
> And just like today, if I had a /22 that my ISP doesn't want to  
> advertise then I need to look for another ISP or get a bigger block.
>
> I still don't see the problem.
>
> Kevin
>
>
>
>
>> -----Original Message-----
>> From: Matthew Kaufman [mailto:matthew at matthew.at]
>> Sent: Monday, March 29, 2010 10:40 AM
>> To: Kevin Kargel
>> Cc: 'ppml at arin.net'
>> Subject: Re: [arin-ppml] FW: IPv6 Non-connected networks
>>
>> Kevin Kargel wrote:
>>> It's not injecting a /119..  you are already advertising a /32..   
>>> you
>> just weren't accepting traffic for that /119 before..
>>>
>>> Anyone have a problem with that?
>>>
>>> Kevin
>>>
>> The problem is that you weren't already advertising a /32. You were
>> hoping to advertise your /48, which is all the PI space you could get
>> and afford, but your ISP wouldn't let you. Just like they won't let  
>> you
>> announce the /119 either.
>>
>> Matthew Kaufman