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 ]
Jan Tuomi
tuomi at ventiro.se
Wed Mar 30 11:54:55 CEST 2011
On 30 mar 2011, at 11.08, Adrian Czapek wrote: > W dniu 2011-03-30 10:58, Tero Toikkanen pisze: >> 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. >> > http://www.ripe.net/ripe/docs/ripe-512#_8._IPv6_Provider > > Most important is the last sentence: > The PI assignment cannot be further assigned to other organisations. > > And according to IPRA, if you provide hosting services on your own infratructure to other companies, you are sub-allocating part of your PI address space to them, so you cannot use PI address space for that purpose. > > Regards > -- > Adrian > So what this means is that if a customer puts their server in my facility I am sub-allocating? To sub-allocate I have to be an LIR and request an own PA-space? For each customer I have to assign their own /64 and register it in the ripe-database? Setting up an SSL-webhost is also sub-allocating? so to set up an ssl-host I have to again allocate an own /64 for the host, register it in the database, set up VLANS and routing on the webserver and network equipment since its a different IP-network? this will cause a lot of problem with stateful inspection in the firewall because i need to use multiple default gateways on the same server. So in the end I have to set up a whole new webbserver for each customer who needs SSL to get things running smoothly? hmm.. seems that I have to forget about IPv6 and continue running IPv4 only.... // 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 -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4697 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20110330/9516758b/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 ]