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/[email protected]/
[address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Sat Aug 16 16:34:19 CEST 2014
On Sat, Aug 16, 2014 at 03:50:56PM +0200, Gert Doering wrote: > On Sat, Aug 16, 2014 at 04:33:57PM +0300, Saku Ytti wrote: > > I personally would want to see YRC implemented, 1EUR/year/resource, > > 4294967296 EUR annual revenue will make it possible to finance > > sufficient long AS number for Nick's use cases. > > Unfortunately, APWG has no formal say in this, as everything related > to money is for the members to decide, and it seems sufficient LIRs > wanted "no extra costs for AS numbers!" to lobby for the removal > from the charging scheme... (we had "50 EUR per AS/year" in it) > > One would need to personally propose this to the board so they can include > it in the new charging scheme drafts, *and* get enough members to actually > vote for it... As author I wholeheartedly agree with the two main concerns Nick raises, we described this concern in the Rationale section B. Going forward I see two possible paths, and would appreciate feedback on either. 1) We add a clause to the policy that the policy only takes effect if either in 2014 or 2015, a yearly recurring cost is associated with AS Number assigments. Until then RIPE-525 remains in effect as is. 2) We limited the number of AS Number assignments per LIR to one thousand. This currently values an AS Number assignment at roughly 2 euros, which in my opinion would be a fine number. This approach would have both an abuse-dampening and a garbage collection effect. Thoughts? Kind regards, Job
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]