>> Packets don't have customers, ISPs do. And in this case you're not a
>> customer of the ISP making the routing decision
>
> Incorrect. I am a customer of 3356. A residential customer, not a BGP
> customer. I'm paying them to route my packets too, and they're routing
> them poorly.
Oh, you s
> On Jan 22, 2024, at 21:34, Forrest Christian (List Account)
> wrote:
>
> I really really wish there were a couple of well-known and globally respected
> communities which you could set to say either "this is a route of last
> resort" or "this is my preferred route".
You're not the first
> On Jan 23, 2024, at 00:43, William Herrin wrote:
>
> On Mon, Jan 22, 2024 at 3:34 PM Alex Le Heux wrote:
>> This is perfectly reasonable routing _if you're 3356_
>>
>> In this profit-driven world, expecting 3356 to do something that's
>> unpro
> At which point Centurylink chooses 40676 7489 11875 11875 11875 11875
> 11875 11875 11875.
>
>> This certainly seems like a reasonable path selection, in the context that
>> 47787 is likely a 3356 customer.
>
> That's -why- 3356 chooses the paths. 40676 and 47787 are customers,
> 1299 is a p
Dear Colleagues,
The correct prefix and pingable address list for the Debogonising Project is:
prefix pinagble address
128.0.0.0/21128.0.0.1
128.0.24.0/24 128.0.24.1
Our apologies for the oversight.
Best regards,
Alex Le Heux
Policy Implementation Co-ordinator
RIPE NCC
On
Alex Le Heux
Policy Implementation Co-ordinator
RIPE NCC
is available in the
document "De-Bogonising New Address Blocks", which can be found at:
http://www.ripe.net/ripe/docs/ripe-351.html
Best regards,
Alex Le Heux
RIPE NCC
Policy Implementation Co-ordinator
ew Address Blocks", which can be found at:
http://www.ripe.net/ripe/docs/ripe-351.html
Best regards,
Alex Le Heux
RIPE NCC
8 matches
Mail list logo
