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/address-policy-wg@ripe.net/
[address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
- Previous message (by thread): [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
- Next message (by thread): [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Tue May 10 09:30:43 CEST 2011
> I am a bit surprised that the whole discussion is around only this part > of the equation. What about the added benefit of the routing security > this policy and subsequently deployed and adopted system can add? > > Today, your network can be taken down by a simple misconfiguration or > malicious attack without any court order. not "can be." essentially, every day someone's prefix is mis-announced by someone else. some have been bad enough to make the press or nanog. most are unintentional. some are malicious. you don't have to swollow the pill that lets you see black helicopters to see this problem. you just have to be a network operator, not a wannabe net lawyer. randy
- Previous message (by thread): [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
- Next message (by thread): [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]