North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: YouTube IP Hijacking

  • From: Barry Greene (bgreene)
  • Date: Mon Feb 25 10:05:53 2008
  • Authentication-results: sj-dkim-1; [email protected]; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
  • Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=885; t=1203951082; x=1204815082; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; [email protected]; z=From:=20=22Barry=20Greene=20(bgreene)=22=20<[email protected] com> |Subject:=20RE=3A=20YouTube=20IP=20Hijacking |Sender:=20; bh=nqtVi3PETkfQ75bbYXDiUzXGVtqlsIx6FBIW/VE0ht8=; b=fM8zDHXzz2F04NRu0Z927cJHdKatwJP5nvorh7rbrjB3hXTaFcxqHwb20x 9dlZJe50Rv0MxDJUqi14Oiih59MMg3GUZZ1O22LauqQyiGLOnRx5ThkdPyTZ HDk9SK4PqTEKfYmxddZmoKtHbkEsFIdviyvTG7aUm8hQ7vLZpEBkU=;
 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Steven M. Bellovin
> How about state-of-the-art routing security?
> 
> Seriously -- a number of us have been warning that this could happen.
> More precisely, we've been warning that this could happen 
> *again*; we all know about many older incidents, from the 
> barely noticed to the very noisy.  (AS 7007, anyone?)  
> Something like S-BGP will stop this cold.
> 
> Yes, I know there are serious deployment and operational 
> issues.  The question is this: when is the pain from routing 
> incidents great enough that we're forced to act?  It would 
> have been nice to have done something before this, since now 
> all the world's script kiddies have seen what can be done.

BCPs stops this problem. soBGP may make it easier.