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] 2007-01 New Policy Proposal (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Previous message (by thread): [address-policy-wg] 2007-01 New Policy Proposal (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Next message (by thread): [address-policy-wg] 2007-01 New Policy Proposal (Direct Internet Resource Assignments to End Users from the RIPE NCC)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Sat Apr 21 02:14:23 CEST 2007
Hay, Filiz Yilmaz schrieb: > PDP Number: 2007-01 > Direct Internet Resource Assignments to End Users from the RIPE NCC > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. [...] for the time being i DO NOT support the proposal as it is. Reasons: - The proposal lacks some nescessary (IMHO) details about the contract ect. (Wilfried pointed that out to some extent) I won't sing off on such a policy change without a descent view onto what it will mean in the reality if it concerns contractual issues. Vague policies are fine for technical stuff :) but not when it comes to contracts. - Explore other (LIR based?) options? While i'm perfectly fine with some kind of contractual relationship that allows the RIPE NCC (or a LIR?) to reclaim PI space/AS Numbers/etc. (for whatever reason), we don't really need to just copy the ARIN policy here, you know. With the actual situation in Russia - probably otherwhere too, it might make more sense to look into another concept, probably somehow like DENIC (.de ccTLD) handles it for Domains here (someone correct me if i talk rubbish here): (1) Contractual relationship is basically with the RIPE NCC, but maintained by a (local?) LIR under normal circumstances (2) Requests and payments are done through a LIR much like it is now (3) If the LIR is shut down the PI/AS/etc. customers get a - whatever - 90day notice from RIPE NCC to 'attach' their object to another LIR of their liking, or continue to pay RIPE directly (this might probably be way more expensive to make it unlikely to happen?). If the customer doesn't do that, RIPE NCC can revoke the assignment(s) after the grace period. (4) If the customer is not paying or not reachable, the LIR can "hand back" the assignment(s) to the RIPE NCC (==> basically continue with(3)) do i make any sense? :-) Note: this is a "2 o'clock in the morning idea" and not a fully fledged proposal of course. P.S.: The "no [sub-|re-]assignment clarification" is ok for me. -- ======================================================================== = Sascha Lenz SLZ-RIPE slz at baycix.de = = Network Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = ========================================================================
- Previous message (by thread): [address-policy-wg] 2007-01 New Policy Proposal (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Next message (by thread): [address-policy-wg] 2007-01 New Policy Proposal (Direct Internet Resource Assignments to End Users from the RIPE NCC)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]