nanog mailing list archives
Re: de-peering for security sake
From: Valdis.Kletnieks () vt edu
Date: Mon, 18 Jan 2016 00:21:22 -0500
On Sun, 17 Jan 2016 19:39:52 -0500, bzs () theworld com said:
How about if backed by an agreement with the 5 RIRs stating no new resource allocations or transfers etc unless a contract is signed and enforced? Or similar.
Then they'd just resort to hijacking address space. Oh wait, they already do that and get away with it.... (And a threat of withholding IP address space from long-haul providers isn't as credible - they have much less need for publicly routed IP addresses than either eyeball farms or content farms, so you'll have to find some other way to motivate them to not accept a hijacked route announcement...)
Attachment:
_bin
Description:
Current thread:
- Re: de-peering for security sake, (continued)
- Re: de-peering for security sake Ca By (Jan 16)
- Re: de-peering for security sake Owen DeLong (Jan 16)
- Re: de-peering for security sake Valdis . Kletnieks (Jan 16)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Dan Hollis (Jan 17)
- Re: de-peering for security sake Ca By (Jan 17)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Doug Barton (Jan 17)
- Re: de-peering for security sake Dan Hollis (Jan 17)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Valdis . Kletnieks (Jan 17)
- Re: de-peering for security sake bzs (Jan 18)
- Re: de-peering for security sake Michael O'Connor (Jan 19)
- Re: de-peering for security sake bzs (Jan 19)
- Re: de-peering for security sake Colin Johnston (Jan 20)
- Re: de-peering for security sake Valdis . Kletnieks (Jan 16)
- Re: de-peering for security sake Owen DeLong (Jan 16)