This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/bcop@ripe.net/

[bcop] Indosat (AS4761) BGP Hijack

Next message (by thread): [bcop] Indosat (AS4761) BGP Hijack

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Blake WILLIS BWILLIS at neotelecoms.com
Thu Apr 3 15:49:22 CEST 2014

On 3 Apr 2014, at 1:45 PM, IP TAC wrote:

> Dear Partner,
>  
> The problem caused by misconfig by our third-party support.
> We already have plan to prevent the problem exist in the future if any misconfig happen again.
> We apologize for the inconvenience.

Greetings,

May I take this opportunity to suggest that you (& anyone else listening that doesn't already have two levels of prevention on their BGP customers)
implement a BGP max-prefix setting on your customer peer-groups to prevent this sort of incident in the future (in addition to using per-customer prefix filters)?

Plenty of networks are rolling out IPv6; <A HREF="http://en.wikipedia.org/wiki/Resource_Public_Key_Infrastructure">RPKI</A> may take longer...

Best regards,
---
 Blake Willis
 Consulting Network Architect

Next message (by thread): [bcop] Indosat (AS4761) BGP Hijack

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ BCOP Archives ]