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] Fwd: Suggestions on a new asn assignment policy
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue Aug 11 14:03:04 CEST 2015
On Tue, 11 Aug 2015, David Huberman wrote: > If at some point in the future, the NCC or community discovers some > child has abused the system and taken an absurd number of ASNs, the NCC > has the power to revoke the ASNs under sections 6.3, 9.3, and 9.4 of the > RIPE NCC Standard Service Agreement. I just read 6.3, 9.3 and 9.4. I don't see which of these I would be in violation of if I went to RIPE NCC and asked for 10k ASNs "because I need them" under the proposed new policy of just recording reason. With the proposed policy of just recording reason given, I don't see how the resources can be revoked (because I have given reason and those reasons have been registered by RIPE NCC), at least not referring to 6.3, 9.3 and 9.4. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]