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]/
[ncc-services-wg] [policy-announce] 2012-08 New Policy Proposal (Publication of Sponsoring LIR for Independent Number Resources)
- Previous message (by thread): [ncc-services-wg] [policy-announce] 2012-08 New Policy Proposal (Publication of Sponsoring LIR for Independent Number Resources)
- Next message (by thread): [ncc-services-wg] [policy-announce] 2012-08 New Policy Proposal (Publication of Sponsoring LIR for Independent Number Resources)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at netability.ie
Mon Oct 15 20:51:14 CEST 2012
On 15/10/2012 16:27, Sascha Luck wrote: > "The RIPE resource allocation and assignment policy documents require > that Internet number resources be registered 'via a public registry > documenting address space allocation and assignment' and notes that > 'this is necessary to ensure uniqueness and to provide information for > Internet troubleshooting at all levels'." > > Invalid, the resources are registered with the RIR, not the sponsoring > LIR. 'this is necessary to ensure uniqueness and to provide information for Internet troubleshooting at all levels' means that if some information is hiding, then information is not being provided for Internet troubleshooting at all levels. Look, the point of BCP12 is good housekeeping and one of the ways we have on the Internet of implementing good housekeeping is to keep stuff out in the open, not hiding away information in a back room. BCP12 is not a BCP because it contains a whole pile of bad practice, or because that advice is in any way out of date. This is current recommended policy for all Internet object registration. > "This mechanism provides a simple means for End Users to identify with > which sponsoring organisation they have a contractual link, in the case > this information is unknown to the End User." > > Accepted, but the end-user can easily find this information by > contacting the RIPE NCC. Last time I looked, the RIPE NCC service region contained about a billion people, and there were 28000 PI blocks. This doesn't scale. Let's automate it and get a cheaper RIPE NCC which isn't spending money answering stupid questions which can just as easily be answered by a computer. > "This policy simplifies the mechanism for verification and co-ordination > between sponsoring organisations when an End User wishes to transfer > resources from one sponsoring organisation to another." > > Unneccessary, as the actual decision and verification is done by the NCC > anyway. Knowing which organisation you're going to be dealing with in advance will cut down significantly on time and general overhead when dealing with transfers. I.e. you can make prior contact with the remote LIR and have stuff arranged in advance and things will go smoothly. Again: this proposal is about making life easy and better and more consistent with the existing policies which we use. Manual intervention is a pain and inconsistent with this improvement. Nick
- Previous message (by thread): [ncc-services-wg] [policy-announce] 2012-08 New Policy Proposal (Publication of Sponsoring LIR for Independent Number Resources)
- Next message (by thread): [ncc-services-wg] [policy-announce] 2012-08 New Policy Proposal (Publication of Sponsoring LIR for Independent Number Resources)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]