[107246] in North American Network Operators' Group
RE: Revealed: The Internet's well known BGP behavior
daemon@ATHENA.MIT.EDU (Boyd, Benjamin R)
Thu Aug 28 11:36:16 2008
Date: Thu, 28 Aug 2008 10:36:05 -0500
From: "Boyd, Benjamin R" <Benjamin.R.Boyd@windstream.com>
To: <eric@spaethco.com>, "Jon Lewis" <jlewis@lewis.org>, <nanog@merit.edu>
Errors-To: nanog-bounces@nanog.org
We've encountered the same diligence with LVL3, especially after
acquisitions where records haven't been updated yet. Although a little
annoying it's quite refreshing.
=20
>-----Original Message-----
>From: Eric Spaeth [mailto:eric@spaethco.com]=20
>Sent: Thursday, August 28, 2008 1:41 AM
>To: Jon Lewis; nanog@merit.edu
>Subject: Re: Revealed: The Internet's well known BGP behavior
>
>Jon Lewis wrote:
>>> At 11:32 PM 27-08-08 -0500, John Lee wrote:
>>>
>>> They didn't have control of any routers other than their own. What=20
>>> they had to find is a single clueless upstream ISP that would allow=20
>>> them to announce prefixes that didn't belong to them.
>>
>> Clueless or big and inattentive? AFAIK, Level3 will accept anything=20
>> from me...as long as I put it in one of the IRRs the day=20
>before I plan=20
>> to announce it.
>
>Working for a company that has been steadily growing through=20
>acquisition, we have actually run into this problem a couple times=20
>before. I'm not sure if we hit the lottery, but our upstream=20
>providers=20
>(including LVL3) have definitely intervened when we've moved=20
>netblocks from a company that doesn't match our name into our=20
>facilities to be advertised under our ASNs. I'm not sure how=20
>diligent or widespread the validation checks are, but at least=20
>on occasion they do occur.
>
>-Eric
>
>
>
***************************************************************************=
************
The information contained in this message, including attachments, may conta=
in=20
privileged or confidential information that is intended to be delivered onl=
y to the=20
person identified above. If you are not the intended recipient, or the pers=
on=20
responsible for delivering this message to the intended recipient, Windstre=
am requests=20
that you immediately notify the sender and asks that you do not read the me=
ssage or its=20
attachments, and that you delete them without copying or sending them to an=
yone else.
