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/members-discuss@ripe.net/
[members-discuss] [ncc-announce] [GM] Publication of Draft Charging Scheme Models 2024
- Previous message (by thread): [members-discuss] [ncc-announce] [GM] Publication of Draft Charging Scheme Models 2024
- Next message (by thread): [members-discuss] [ncc-announce] [GM] Publication of Draft Charging Scheme Models 2024
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastien Brossier
sebastien at brossier.org
Wed Apr 19 12:18:59 CEST 2023
On 18/04/2023 16:37, Clement Cavadore wrote: > But AFAIK, RIPE NCC already does this kind of mechanism for ASN which > are not seen on the DFZ. They ask if it's in use, and why it's not seen > on the DFZ (and there are legit use case, for example for IXP route- > server ASN, or for out of internet routing domains). But changing the > billing rules for non-scarce resources seems a bit too rough, IMHO. It's not really about scarcity I think. RIPE NCC receives a lot of ASN requests per month and gets paid zero for that work, while having to continuously perform due diligence on all resources (think sanctions check). Kind regards, Sebastien Brossier
- Previous message (by thread): [members-discuss] [ncc-announce] [GM] Publication of Draft Charging Scheme Models 2024
- Next message (by thread): [members-discuss] [ncc-announce] [GM] Publication of Draft Charging Scheme Models 2024
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]