[181045] in North American Network Operators' Group
Re: AS4788 Telecom Malaysia major route leak?
daemon@ATHENA.MIT.EDU (Mel Beckman)
Sun Jun 14 18:56:14 2015
X-Original-To: nanog@nanog.org
From: Mel Beckman <mel@beckman.org>
To: Raymond Dijkxhoorn <raymond@prolocation.net>
Date: Sun, 14 Jun 2015 22:56:06 +0000
In-Reply-To: <ECFDC678-2B2E-45CC-A71B-00DB03C7B98D@prolocation.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Raymond,
But you said "A simple 'sorry' would have done." Now you're asking for lots=
more detail. Why the change?
-mel beckman
> On Jun 14, 2015, at 2:32 PM, Raymond Dijkxhoorn <raymond@prolocation.net>=
wrote:
>=20
> Hello Mel,
>=20
> Must just be me then.=20
>=20
> I was most likely expecting a more in depth report. Strange things happen=
ed. Perhaps they could post a 'what exactly happened' since this wasnt a av=
erage route leak.=20
>=20
> Thanks,
> Raymond Dijkxhoorn
>=20
>> Op 14 jun. 2015 om 23:27 heeft Mel Beckman <mel@beckman.org> het volgend=
e geschreven:
>>=20
>> Raymond,
>>=20
>> They provided a "simple sorry":
>>=20
>> "We apologise for any inconvenience caused by the service disruption."
>>=20
>> It doesn't get much more simple than that.
>>=20
>> -mel beckman
>>=20
>>> On Jun 14, 2015, at 2:21 PM, Raymond Dijkxhoorn <raymond@prolocation.ne=
t> wrote:
>>>=20
>>> Hai!
>>>=20
>>> Mark, mistakes and oopses happen. No problem at all. I understand that =
completely. There is human faillure and this happenes.=20
>>>=20
>>> A simple 'sorry' would have done. Yet their whole message tells 'they d=
id ok' In my very limited view they did NOT ok. Did i misread?
>>>=20
>>> I am also very much looking how level3 is going to prevent things like =
this. But out of own experience they will not. We have seen before that the=
y implemented filtering based on customer lists. But not a per customer fil=
ter. They did this globally. So any l3 customer can announce routes of anot=
her l3 customer. While this can be changed this outage tells there is certa=
inly room for improvements.=20
>>>=20
>>> I hope people will learn from what happened and implement proper filter=
ing. Thats even more important then a message from a operator that didnt ev=
en understand fully what they caused to the internet globally.=20
>>>=20
>>> Thanks,
>>> Raymond Dijkxhoorn
>>>=20
>>>> Op 14 jun. 2015 om 23:04 heeft Mark Tinka <mark.tinka@seacom.mu> het v=
olgende geschreven:
>>>>=20
>>>>=20
>>>>=20
>>>>> On 14/Jun/15 22:55, Raymond Dijkxhoorn wrote:
>>>>> Hai!
>>>>>=20
>>>>> Wouw! This is what they came up with?!=20
>>>>>=20
>>>>> Hopefully Level3 will take appropriate measures. Its amazing. Really.=
=20
>>>>>=20
>>>>> 'Some internationally routes'=20
>>>>>=20
>>>>> Have they any idea what they did at all?
>>>>>=20
>>>>> Its amazing that with parties like that the internet still works as i=
s <tm> ...
>>>>=20
>>>> I wouldn't be as hard. Stuff happens - and as they said, during a
>>>> maintenance activity, they boo-boo'ed.
>>>>=20
>>>> Are Level(3) going to own up and say they should have had filters in
>>>> place? I certainly hope they do.
>>>>=20
>>>> But more importantly, are Level(3) going to implement the filters
>>>> against TM's circuit? Are they going to run around the network looking
>>>> for any additional customer circuits that need plugging? That's my
>>>> concern...
>>>>=20
>>>> Mark.
