IPv6 residential service: What prefix, static, dynamic, extra cost ?
Hi all, I’m trying to make a table to compare the way actual IPv6 services to residential customers are being provissioned mainly in EU, but I will do to the same also in other regions. I’m happy to make a single “table” with all the information that I can collect and publish it so others can make use of it, and keep it updated, may be in some URL, etc. So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that? Please state the ISP name, country and if you have a URL or document that state this service, other options, etc. If you’re not yet providing the service, but it will happen soon and the “model” for this has been already defined, please let me know as well! Hopefully I can get a lot of anwers! Private or in the list, I’m fine either way. Thanks! Regards, Jordi PD: In my opinion it should be /48 by default, static and opt-in to dynamic, no extra charge on top of the Internet service price, but I know many ISPs will not agree :-( Here just trying to collect the info in a single place. ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
On Wed, May 18, 2016 at 8:45 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
PD: In my opinion it should be /48 by default, static and opt-in to dynamic, no extra charge on top of the Internet service price, but I know many ISPs will not agree :-( Here just trying to collect the info in a single place.
[Disclaimer] I've not been involved in ISP business for a while] but... why /48? /56 would give 256 subnets. ought to be enough for anybody IMHO (unless your definition of 'residential customer' is quite different from mine...) -- SY, Jen Linkova aka Furry
Jen and all, Gather 'round kids, Grandpa has a story! At 2016-05-18 20:56:13 +0200 Jen Linkova <furry13@gmail.com> wrote:
On Wed, May 18, 2016 at 8:45 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
PD: In my opinion it should be /48 by default, static and opt-in to dynamic, no extra charge on top of the Internet service price, but I know many ISPs will not agree :-( Here just trying to collect the info in a single place.
[Disclaimer] I've not been involved in ISP business for a while] but... why /48? /56 would give 256 subnets. ought to be enough for anybody IMHO (unless your definition of 'residential customer' is quite different from mine...)
I was at a meeting way back in the 20th century - either my first or second time at an IETF, IIRC. There was a discussion amongst RIR-types about the default prefix size. Someone proposed the /48 and said that we need to have the same size for every assignment, so that it is easy for customers to move between providers, and to avoid establishing the difference between 'residential customer' and other customers that you are describing. Even at the time I thought it was a bit cheeky to be establishing policy like this, but the idea was not criticized at the meeting. (I also suggested that we don't really need to use 8-bit boundaries even, but was told via some hand-waving arguments about ASICs that this was absolutely necessary.) ¯\_(ツ)_/¯ Cheers, -- Shane
...another flash-back to the previous millennium below. On 2016-05-19 10:18, Shane Kerr wrote:
Jen and all,
Gather 'round kids, Grandpa has a story!
So this from a Grand-Grand-Pa :-)
At 2016-05-18 20:56:13 +0200 Jen Linkova <furry13@gmail.com> wrote:
On Wed, May 18, 2016 at 8:45 PM, JORDI PALET MARTINEZ [...] I was at a meeting way back in the 20th century - either my first or second time at an IETF, IIRC.
And I remember a late-night meeting amongst the RIR Folks (in Bangkok, iirc), when we tried to come up with a distribution policy which would be a compromise between the different points of view in the 5 regions. It turned out that we were successful in the end. One of the arguments in favour of a uniform prefix length (/48 per 'site') was the support for easy renumbering support in DNS. Anyone remembers the A6 RR type and the level of abstraction/indirection it would have offered? Alas, this beast is extinct by now. RIP...
There was a discussion amongst RIR-types about the default prefix size. Someone proposed the /48 and said that we need to have the same size for every assignment, so that it is easy for customers to move between providers, and to avoid establishing the difference between 'residential customer' and other customers that you are describing. Even at the time I thought it was a bit cheeky to be establishing policy like this, but the idea was not criticized at the meeting. (I also suggested that we don't really need to use 8-bit boundaries even, but was told via some hand-waving arguments about ASICs that this was absolutely necessary.)
I, too, think that this was mostly hand-waving. The only boundary I do consider essential is alignment with the 4bit hex digits of the external representation, in order to have aligned reverse DNS delegation points. FWIW, Wilfried
¯\_(ツ)_/¯
Cheers,
-- Shane
On Wed, 18 May 2016, Jen Linkova wrote:
On Wed, May 18, 2016 at 8:45 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
PD: In my opinion it should be /48 by default, static and opt-in to dynamic, no extra charge on top of the Internet service price, but I know many ISPs will not agree :-( Here just trying to collect the info in a single place.
[Disclaimer] I've not been involved in ISP business for a while] but... why /48? /56 would give 256 subnets. ought to be enough for anybody IMHO (unless your definition of 'residential customer' is quite different from mine...)
My opinion is that anything between /56 and /48 is fine. As far as I know, current RIPE policy gives the ISP the option to without motivation, ask for enough IPv6 addresses to offer each customer a /48 and I'd like to keep it that way. But you're correct, it seems most deployments are going for /56 for no more reason than that it "should work for everybody". Of course /48 works as well as it's a superset of /56. I'm not going to give anyone who gives everybody a /48 a hard time and I don't want RIPE to do it either. -- Mikael Abrahamsson email: swmike@swm.pp.se
Hi, On Thu, May 19, 2016 at 10:19:07AM +0200, Mikael Abrahamsson wrote:
My opinion is that anything between /56 and /48 is fine. As far as I know, current RIPE policy gives the ISP the option to without motivation, ask for enough IPv6 addresses to offer each customer a /48 and I'd like to keep it that way.
Right. The reason why the address policy isn't fixed at "customer = /48" anymore is because Geoff Huston did some math, "back then", and came to the conclusion that IPv6 might actually be not sufficiently large if - every residential customer receives one or more /48s (multiple ISPs) - RIR->LIR policy has very liberal HD ratio (so for large blocks you get 1:10000 or worse utilization ration) - every human on earth gets access to the Internet so the policy was changed to make this a local decision, and sort of recommend a /56 (but /48 is OK, and counted as "256 customers with /56" when judging utilization) (and tightened HD ratio somewhat). With-no-hats, I think a /56 for residential is good enough, especially with homenet coming to replace the old DHCP-PD hierarchical model where you could end up with prefix shortage if you have router cascades, due to protocol inflexibility ("/56 router delegating /60 -> delegating /64 and then?"). With homenet, 250 subnets in the home would "just work" given a /56, and I'm too narrow-minded to imagine deployments that need more *subnets*. Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
On 19/May/16 10:19, Mikael Abrahamsson wrote:
My opinion is that anything between /56 and /48 is fine. As far as I know, current RIPE policy gives the ISP the option to without motivation, ask for enough IPv6 addresses to offer each customer a /48 and I'd like to keep it that way.
+1.
But you're correct, it seems most deployments are going for /56 for no more reason than that it "should work for everybody". Of course /48 works as well as it's a superset of /56. I'm not going to give anyone who gives everybody a /48 a hard time and I don't want RIPE to do it either.
+1. Mark.
On Thu, May 19, 2016 at 10:19 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
PD: In my opinion it should be /48 by default, static and opt-in to dynamic, no extra charge on top of the Internet service price, but I know many ISPs will not agree :-( Here just trying to collect the info in a single place.
[Disclaimer] I've not been involved in ISP business for a while] but... why /48? /56 would give 256 subnets. ought to be enough for anybody IMHO (unless your definition of 'residential customer' is quite different from mine...)
My opinion is that anything between /56 and /48 is fine. As far as I know, current RIPE policy gives the ISP the option to without motivation, ask for enough IPv6 addresses to offer each customer a /48 and I'd like to keep it that way.
But you're correct, it seems most deployments are going for /56 for no more reason than that it "should work for everybody". Of course /48 works as well as it's a superset of /56. I'm not going to give anyone who gives everybody a /48 a hard time and I don't want RIPE to do it either.
Oh, don't get me wrong - I'm not going to give anyone a hard time for assigning /48 for households. I was asking only because I've spent some time recently on various v6 address plans and by default I'm assigning /56, so I'm just wondering if I'm missing anything and there is any good reason for assigning /48 (the only reason I can think of is 'one day that site might want to be multihomed...'). -- SY, Jen Linkova aka Furry
On 18/May/16 20:45, JORDI PALET MARTINEZ wrote:
Hi all,
I’m trying to make a table to compare the way actual IPv6 services to residential customers are being provissioned mainly in EU, but I will do to the same also in other regions.
I’m happy to make a single “table” with all the information that I can collect and publish it so others can make use of it, and keep it updated, may be in some URL, etc.
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
Please state the ISP name, country and if you have a URL or document that state this service, other options, etc.
If you’re not yet providing the service, but it will happen soon and the “model” for this has been already defined, please let me know as well!
Hopefully I can get a lot of anwers! Private or in the list, I’m fine either way.
We are currently delivering IPv6 to wholesale and enterprise customers today, but looking at residential delivery options. For us, for the home, we are considering a /56 by default. Still undecided on whether it will be dynamic or static, but the provisioning of either would be dynamic. We are leaning to dynamically-assigned static IPv6 subnets. No additional charges for IPv6 addresses or connectivity. We don't charge customers for IPv4 addresses. Our region is primarily Africa. Hope this helps. Mark.
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
A related question that is not on the list above: 6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'? Of course, most residential customers probably don't care. But I mention it as both a DNS and IPv6 geek. It's something to consider. Colin
Hi Jordi, That could be a useful list to have somewhere, thanks for that.
On 19 May 2016, at 00:22, Colin Petrie <colin@spakka.net> wrote:
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
A related question that is not on the list above: 6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
Of course, most residential customers probably don't care. But I mention it as both a DNS and IPv6 geek. It's something to consider.
Would it be a lot of work to add 2 or 3 columns regarding the IPv4 support? 7) Do you still provide native IPv4 support? 7a) globally routable address? yes/no, static/dynamic? 7b) NAT444 (CGN) or DS-lite 7c) NAT64 or 464-Xlat Groet, Marco
Hi Jordi,
That could be a useful list to have somewhere, thanks for that.
On 19 May 2016, at 00:22, Colin Petrie <colin@spakka.net> wrote:
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
A related question that is not on the list above: 6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
Of course, most residential customers probably don't care. But I mention it as both a DNS and IPv6 geek. It's something to consider.
Would it be a lot of work to add 2 or 3 columns regarding the IPv4 support?
7) Do you still provide native IPv4 support? 7a) globally routable address? yes/no, static/dynamic? 7b) NAT444 (CGN) or DS-lite 7c) NAT64 or 464-Xlat
Still early, sorry for the reply to self. Maybe it is useful if it is organised based on type of network: wireless/wireline and/or carrier (cable, DSL, wifi, GSM). There might be differences in type of service based on the carrier. Marco
Hi Colin, Marco, Very good points. I think to make it easy, I’m going to create an online survey, not sure if today or tomorrow, I will have the time to make it. I will post the link on the list. Regards, Jordi -----Mensaje original----- De: ipv6-wg <ipv6-wg-bounces@ripe.net> en nombre de Marco Hogewoning <marcoh@marcoh.net> Responder a: <marcoh@marcoh.net> Fecha: jueves, 19 de mayo de 2016, 7:40 Para: Colin Petrie <colin@spakka.net> CC: <ipv6-wg@ripe.net> Asunto: Re: [ipv6-wg] IPv6 residential service: What prefix, static, dynamic, extra cost ?
Hi Jordi,
That could be a useful list to have somewhere, thanks for that.
On 19 May 2016, at 00:22, Colin Petrie <colin@spakka.net> wrote:
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
A related question that is not on the list above: 6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
Of course, most residential customers probably don't care. But I mention it as both a DNS and IPv6 geek. It's something to consider.
Would it be a lot of work to add 2 or 3 columns regarding the IPv4 support?
7) Do you still provide native IPv4 support? 7a) globally routable address? yes/no, static/dynamic? 7b) NAT444 (CGN) or DS-lite 7c) NAT64 or 464-Xlat
Still early, sorry for the reply to self.
Maybe it is useful if it is organised based on type of network: wireless/wireline and/or carrier (cable, DSL, wifi, GSM). There might be differences in type of service based on the carrier.
Marco
********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
On 19 May 2016, at 8:18, JORDI PALET MARTINEZ wrote:
Very good points. I think to make it easy, I’m going to create an online survey, not sure if today or tomorrow, I will have the time to make it.
Jordi, Are you interested in pre-production/pilot status, or only production services? Are you happy to have some customer responses as well? If yes to either of the above, I guess you'll need a corresponding status tag. Best regards, Niall O'Reilly
Hi Niall, Yes, please, any input is welcome, but wait a day or so. I’m setting up a limesurvey to make it easier to everyone to respondo on-line. I will include as many suggestions as I’m getting, and the people will be able to answer only to those questions they like, including your suggestion to be able to indicate if it is a piloto or comercial, and those from David Ponzone about the CPE features, core network, software. I will include also some questions about if it is dual-stack (with public or private IPv4), if NAT444, DS-LITE, 6RD, MAP-E/T, 464XLAT, others, are being used, etc. Any further inputs are welcome! Regards, Jordi -----Mensaje original----- De: ipv6-wg <ipv6-wg-bounces@ripe.net> en nombre de Niall O'Reilly <niall.oreilly@ucd.ie> Responder a: <niall.oreilly@ucd.ie> Fecha: jueves, 19 de mayo de 2016, 9:34 Para: Jordi Palet Martinez <jordi.palet@consulintel.es> CC: <ipv6-wg@ripe.net> Asunto: Re: [ipv6-wg] IPv6 residential service: What prefix, static, dynamic, extra cost ?
On 19 May 2016, at 8:18, JORDI PALET MARTINEZ wrote:
Very good points. I think to make it easy, I’m going to create an online survey, not sure if today or tomorrow, I will have the time to make it.
Jordi,
Are you interested in pre-production/pilot status, or only production services?
Are you happy to have some customer responses as well?
If yes to either of the above, I guess you'll need a corresponding status tag.
Best regards,
Niall O'Reilly
********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
At 19 may 2016, 10:04 JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
Any further inputs are welcome!
For some more useful hints about applying IPv6 technologies and subnetting sizes, please take a look at this wiki page and its references: https://en.wikipedia.org/wiki/IPv6_subnetting_reference <https://en.wikipedia.org/wiki/IPv6_subnetting_reference>
Perhaps you could also include some more columns about the devices/softwares used to deliver IPv6: -CPE (ie: SLAAC, DHCPv6, DS-Lite, etc…) -core network (ie: Cisco ASR1000 NAT64 feature, etc…) -software (ie: PowerDNS for DNS64, etc…) I agree it’s sometimes sensible information as it may be the outcome of a long and painful work but some people may be willing to share that as it would promote those vendors and those specific softwares and it could send a message to those who are late in the game. David Ponzone Direction Technique email: david.ponzone@ipeva.fr <mailto:david.ponzone@ipeva.fr> tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr <blocked::http://www.ipeva.fr/> - www.ipeva-studio.com <blocked::http://www.ipeva-studio.com/> Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.
Le 19 mai 2016 à 09:18, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> a écrit :
Hi Colin, Marco,
Very good points. I think to make it easy, I’m going to create an online survey, not sure if today or tomorrow, I will have the time to make it.
I will post the link on the list.
Regards, Jordi
-----Mensaje original----- De: ipv6-wg <ipv6-wg-bounces@ripe.net> en nombre de Marco Hogewoning <marcoh@marcoh.net> Responder a: <marcoh@marcoh.net> Fecha: jueves, 19 de mayo de 2016, 7:40 Para: Colin Petrie <colin@spakka.net> CC: <ipv6-wg@ripe.net> Asunto: Re: [ipv6-wg] IPv6 residential service: What prefix, static, dynamic, extra cost ?
Hi Jordi,
That could be a useful list to have somewhere, thanks for that.
On 19 May 2016, at 00:22, Colin Petrie <colin@spakka.net> wrote:
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided? 2) Is that prefix static or dynamic? 3) In case is dynamic, there is a chance for static? 4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)? 5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
A related question that is not on the list above: 6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
Of course, most residential customers probably don't care. But I mention it as both a DNS and IPv6 geek. It's something to consider.
Would it be a lot of work to add 2 or 3 columns regarding the IPv4 support?
7) Do you still provide native IPv4 support? 7a) globally routable address? yes/no, static/dynamic? 7b) NAT444 (CGN) or DS-lite 7c) NAT64 or 464-Xlat
Still early, sorry for the reply to self.
Maybe it is useful if it is organised based on type of network: wireless/wireline and/or carrier (cable, DSL, wifi, GSM). There might be differences in type of service based on the carrier.
Marco
********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company
This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
*********************************************************************************************************** Le service MailSecure d'IPeva confirme l'absence de virus et de spam dans ce message. ***********************************************************************************************************
On 19/May/16 07:37, Marco Hogewoning wrote:
Would it be a lot of work to add 2 or 3 columns regarding the IPv4 support?
From our side:
7) Do you still provide native IPv4 support?
Yes.
7a) globally routable address? yes/no, static/dynamic?
Globally routable. Static or dynamic will be supported.
7b) NAT444 (CGN) or DS-lite
No.
7c) NAT64 or 464-Xlat
Yes. Mark.
On 18/05/16 20:45, JORDI PALET MARTINEZ wrote:
So here are the questions for actual IPv6 services providers to residential customers: 1) What prefix size is provided?
/48
2) Is that prefix static or dynamic?
Static
3) In case is dynamic, there is a chance for static?
n/a
4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)?
n/a
5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
Both static v4 an v6 are part of the standard service
Please state the ISP name, country and if you have a URL or document that state this service, other options, etc.
XS4ALL, The Netherlands Not sure about a URL that states this service specifically, some basic info is here (in dutch): https://www.xs4all.nl/technologie.htm And Colin's bonus questions:
6) Can the customer delegate reverse DNS for the assigned IPv6 prefix? 6a) If the prefix is static, can they use an NS delegation? 6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
The answer to all of these is: Not (yet) implemented. Timo --------------- XS4ALL Techteam
On 2016-05-18 20:45, JORDI PALET MARTINEZ wrote:
Hi all,
I’m trying to make a table to compare the way actual IPv6 services to residential customers are being provissioned mainly in EU, but I will do to the same also in other regions.
I’m happy to make a single “table” with all the information that I can collect and publish it so others can make use of it, and keep it updated, may be in some URL, etc.
Hi, I'm not sure what hat I'm wearing while writing this, but I'm going to ask anyway: what if there was a wiki, perhaps provided by the RIPE NCC, to let people add this info themselves? That'd scale a bit better and would be updateable as things change. Maybe I'm ignorant and there is one already. BTW I'd add a "periodic change interval" (ie. 24h, 1w, ...) column if the prefix is dynamic. Cheers, Robert
On Thu, 19 May 2016, Robert Kisteleki wrote:
BTW I'd add a "periodic change interval" (ie. 24h, 1w, ...) column if the prefix is dynamic.
As far as I know, there are a few different versions here. There is also both the question of WAN side and LAN side prefix. WAN side typically done using RAs or static. LAN side typically done using PD or static. 1. Prefix changes each time connection goes down/up. 1b Mechanism in is forced in certain time intervals. 1c with spatial overlap (graceful change) or abrupt break. 2. Prefix is really the same for the lifetime of the customer contract. 3. Prefix is the same until for instance the ISP PE router is changed, or the DHCP server is changed, or there is a DHCP scope change. This typically happens 0-2 times per year (semi-static). 4. Prefix is handed out by DHCPv6-PD or it's statically configured. I probably forgot something, but at least all of these should be defined on the wiki. Btw, I think wiki is a great idea, and we should list the different variants (we need to identify all of them before hand). -- Mikael Abrahamsson email: swmike@swm.pp.se
Hi Jordi,
1) What prefix size is provided?
/56
2) Is that prefix static or dynamic?
Static, delegated using DHCPv6-PD
3) In case is dynamic, there is a chance for static?
n/a
4) Any extra cost for having it static, or having a bigger prefix (i.e., /48 instead of /56)?
n/a
5) If the customer has already a static IPv4 with a monthly charge, is still IPv6 static prefix being charged on top of that?
n/a (IPv4 is static, no monthly charge)
6) Can the customer delegate reverse DNS for the assigned IPv6 prefix?
Not at the moment
6a) If the prefix is static, can they use an NS delegation?
n/a
6b) If the prefix is dynamic, can they consistently DNAME it to a customer-hosted zone that contains PTRs for 'some-subnet-size'?
n/a
7) Do you still provide native IPv4 support?
Yes
7a) globally routable address? yes/no, static/dynamic?
yes, static
7b) NAT444 (CGN) or DS-lite
No
7c) NAT64 or 464-Xlat
No
Please state the ISP name,
Solcon
country
NL Cheers, Sander
participants (15)
-
Colin Petrie -
David Ponzone -
Gert Doering -
Jen Linkova -
JORDI PALET MARTINEZ -
Marco Hogewoning -
Mark Tinka -
Michiel Klaver -
Mikael Abrahamsson -
Niall O'Reilly -
Robert Kisteleki -
Sander Steffann -
Shane Kerr -
Timo Hilbrink -
Wilfried Woeber