[ipv6-wg] IPv6 questions regarding ripe and address ranges

Hello,
 
My name is Ralph and i'm researching the options for IPv6 within my
company. From previous contact with the ripe i've understood that there
are 3 ways to get IPv6 ranges:
- ISP assigned, i don't like this option because of renumbering issues
when transferring to a different ISP
- Ripe member, this way my organisation will become a member and can
request own adresses based upon need
- PI assigned, coming (hopefully) this year
 
My company has several locations on several continents, which raises the
following questions:
-If we would become a ripe member, how would we deal with IPv6 range
requests outside the ripe "juristiction", like in north america?

-It is my understanding that the ripe member policy assigns /32sh and no
/48sh which, from my standpoint, seems a bit unnecessary because there
will be equal number of routing entries because we will require one
range per location no matter the prefix. From what i've learned so far
this could basically result in a /32 for a 100-user location which
cannot be the goal, even though i might be stuck in IPv4 ways.
 
- Isn't it possible to get a /32 and allow us to divide it between our
sites with /48sh (and allowing them to advertise /48sh globally)?
 
Sincerely,
Ralph Peeters


This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ipv6-wg/attachments/20090317/a3f581f7/attachment.html>