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/ipv6-wg@ripe.net/
"Special Application Addresses" (Was: Re: [ipv6-wg] RE: address-policy-wg (ipv6-wg digest, Vol 1 #271 - 11 msgs))
- Previous message (by thread): [ipv6-wg] RE: address-policy-wg (ipv6-wg digest, Vol 1 #271 - 11 msgs)
- Next message (by thread): "Special Application Addresses" (Was: Re: [ipv6-wg] RE: address-policy-wg (ipv6-wg digest, Vol 1 #271 - 11 msgs))
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at unfix.org
Fri Nov 25 19:02:04 CET 2005
peter.sherbin at bell.ca wrote: > My project requires a few millions of IPv6 addresses. Then a only need single IPv6 /64 (2^64 is more than a 'few million'). No RIR really has any business with you as you are an enduser according to the above description. > The application has to: > 1. avoid renumbering of the network Why? Your application should be able to use renumber easily using a form of management interface. Does this "network" get connected to the internet? > 2. keep allocated addresses for an extended period of time define "extended period of time". > Current ARIN allocation schema: ARIN -> LIR -> End User does not make much sence because to get addresses I: > - either have to become a LIR, which I may not necessarily want, or You say that you need a 'few million' addresses, but for what exact reason.... > - the entire application depends on fortunes of a third party (LIR), which is a prohibitive risk factor for the investment You also depend on the RIR's according to this which also is a risk factor > On the other side I am willing to "rent" addresses from a registry (ARIN) and return the allocation when it is no longer needed. > > Now, how do we change the current address allocation policy Follow the policy process and make a proposal. > which kills IPv6 in its cradle? That it doesn't rock your boat doesn't mean it is doing anything bad. Greets, Jeroen PS: You might want to delete unused parts of emails, sending 27kb of quoted email which you don't reference is useless. Also changing the subject helps identifying what you are actually mailing about. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 238 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ipv6-wg/attachments/20051125/fad956fa/attachment.sig>
- Previous message (by thread): [ipv6-wg] RE: address-policy-wg (ipv6-wg digest, Vol 1 #271 - 11 msgs)
- Next message (by thread): "Special Application Addresses" (Was: Re: [ipv6-wg] RE: address-policy-wg (ipv6-wg digest, Vol 1 #271 - 11 msgs))
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]