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] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Previous message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Next message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
michael.dillon at bt.com
michael.dillon at bt.com
Tue Nov 25 21:14:42 CET 2008
> http://www.ripe.net/ripe/policies/proposals/2006-01.html I don't like this. >IPv6 Provider Independent (PI) Assignments: >To qualify for an IPv6 PI address space, an organisation must: >a) not be an IPv6 LIR; >b) demonstrate that it will be multihomed (for example by showing contracts of the peering partners) "For example" should not be in a policy sentence like this. This sentence style encourages the writer to be too brief. If it is really necessary to include examples of what constitutes a "demonstration" of multihoming, then it should be enumerated like this: 1) faxing the first page and signature page of contracts of peering partners 2) asking peering partners to send supporting email direct to RIPE 3) faxing orders for peering interconnect circuits 4) providing a letter from a signing officer of the organization stating that it will be multihoming in the near future >c) meet the requirements of the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region" This is awful. The policies described in the referenced document basically boil down to requiring the end user to have a contractual relationship with an LIR or with RIPE. Could we not say simply: c) provide a faxed copy of the first page and signature page of the signed end user contract with an LIR or RIPE. >The prefix will be assigned by the RIPE NCC directly to the End User Organisations upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. >The minimum size of the assignment is a /48. Organisations requesting a larger assignment (shorter prefix) must provide documentation justifying the need for additional subnets. >Additional assignments may also be made when there is a technical need demanding this or usage justified. When possible, these further assignments will be made from an adjacent address block. >Assignments will be allocated from a separate 'designated block' to facilitate filtering practices. >The PI assignment cannot be further assigned to other organisations. --Michael Dillon
- Previous message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Next message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]