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/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Previous message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Next message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tero Toikkanen
Tero.Toikkanen at nebula.fi
Wed Mar 30 10:58:58 CEST 2011
Hi, As far as I'm concerned, there seems to be a strange discrepancy between IPv4 PI and IPv6 PI. Apparently Janne has already successfully obtained IPv4 PI and has now requested IPv6 PI, declaring the same intended use. Could someone please point out where in the policy documents it says one can use IPv4 PI for hosting, but not IPv6 PI? I'm having a hard time finding such terms. ____________________________________ Tero Toikkanen Nebula Oy From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Jan Tuomi Sent: 30. maaliskuuta 2011 11:25 To: address-policy-wg at ripe.net Subject: [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why? Hi, A have made a request for a IPv6 PI / 48 allocation for my hosting facility. I am mostly hosting shared services, but I also have a lot of Co-located services for my customers. I am already multihomed to have redundancy from two ISPs for IPv4 and I am going to setup the IPv6 Network the same way. My ASN is 196704, and I am multihoming trough IP-Only (AS12552) and Telenor (AS8434). My sponsoring LIR says that I can get an assignment from their PA-space right away, BUT then I would not be multi-homed, so that is NOT an option. The answer I get from you (RIPE) is: You mentioned that several of the subnets will be used to provide services to your customers (LEON Hosting, Co-location/Dedicated servers). Unfortunately current IPv6 address assignment and allocation policy does not permit the use of IPv6 PI address space for these services. At this time IPv6 PI address space cannot be used for any service where a customer would receive a subnet of IP space (including a single IP). Therefore it cannot be used for colocation services, dedicated servers, SSL certificates etc. There is currently a discussion on exactly this subject within the RIPE community. Ventiro AB are welcome to sign up for the mailing list and join the discussion. You can find the mailing list here: http://www.ripe.net/ripe/mail/ripe-lists/address-policy-wg I need to be multihomed because i feel its safer to have redandancy from separate upstreams with separate infrastructure than buying the redundancy from one provider. My business is to keep servers running in my hosting facility, part of them owned by me, part of them owned by the customers. Some servers are shared among several customers, some are dedicated to one customer only. With todays technology as far as I know I must have separate IPs for SSL-enabled services. Is it RIPEs hidden agenda to put small hosting facilitys out of business with IPv6 and force all customers to use the bigger ISPs? When I requested my IPv4 PI allocation, I was already planning to also run with IPv6 to be prepared for the future and somehow try to help with the transition to IPv6, so people dont have the arguments that we dont use IPv6 because there is no services, its now so much services from a global point of view, but it wouldnt be IPv4 only.... So what should I do? What are my options? // Janne _______________________ V E N T I R O ______ Janne Tuomi, tuomi at ventiro.se Tel: +46-11-36 52 00 GSM: +46-70-224 6000 Fax: +46-11-36 52 05 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20110330/bb841f9f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5179 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20110330/bb841f9f/attachment.p7s>
- Previous message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Next message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]