[address-policy-wg] 2014-03 "Remove Multihoming Requirement for AS Numbers Assignments" take #4
- Previous message (by thread): [address-policy-wg] 2014-03 "Remove Multihoming Requirement for AS Numbers Assignments" take #4
- Next message (by thread): [address-policy-wg] 2014-03 "Remove Multihoming Requirement for AS Numbers Assignments" take #4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue Aug 11 12:32:53 CEST 2015
On Tue, 11 Aug 2015, Job Snijders wrote: > I've noted as an argument opposing this proposal: "An adversary could > try to deplete the pool of available ASNs." If someone has a workable > suggestion how to resolve that in policy, I am all ears, but I wouldn't > mind a pragmatic approach where we just trust our community and deal > with issues if and when they arise. Cap the number of ASNs handed out until the policy is evaluated. RIPE is allowed to hand out $NUMBER ASNs under this policy, when $NUMBER/2 has been reached, please come back and tell us how it went. If $NUMBER is in the 10k-50k range, and we're talking 32bit ASNs, we haven't used up a huge amount of this limited resource. Also, having an ASN costs money per year, right? So if someone wants to sit on 1000 ASNs, this will actually cost significant money? -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] 2014-03 "Remove Multihoming Requirement for AS Numbers Assignments" take #4
- Next message (by thread): [address-policy-wg] 2014-03 "Remove Multihoming Requirement for AS Numbers Assignments" take #4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]