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/[email protected]/
[ipv6-wg] IPv6 Implementation for an ISP
- Previous message (by thread): [ipv6-wg] IPv6 Implementation for an ISP
- Next message (by thread): [ipv6-wg] IPv6 Implementation for an ISP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lee Howard
lee at asgard.org
Mon Mar 11 18:44:26 CET 2019
If you have enough IPv4 address space, the easiest way to do IPv6 is to go dual-stack (both IPv4 and IPv6 to every customer), and then work on the transition technologies. Here's my "Learn IPv6 before lunch" reading list: https://www.retevia.net/recommended-reading-on-ipv6/ Here's a high-level guide for ISPs: https://datatracker.ietf.org/doc/rfc6782/ You may want to think about this as if your goal is run an IPv6-only access network, with translation to IPv4 at the edges where necessary. Let customers run dual-stack inside the home; so if a customer has devices in their home (alarm systems, smart TVs) that require IPv4, the home gateway can translate from IPv4 to IPv6, and if the destination is IPv4-only, you have a translator in your data center or peering point translating from IPv6 to IPv4. Jordi like 464xlat, but I like MAP-T (or MAP-E). Dual-stack Lite is also an option. In all of those cases, the hardest part seems to be getting support in the CPE. Here's a very short description of each: https://www.retevia.net/what-we-offer/ My experience is that most of your time will be spent working on your provisioning, monitoring, and support systems. Equipment generally supports IPv6, and you'll just have to read the manuals to find the right commands. Lee On 3/11/19 12:41 PM, Alessandro Valenza wrote: > > Hello, > > this is the first time I write in this mailing list. > > I have a question for you. > > I’m working for an ISP that obtained IPv4 (/22) and IPv6 (/29). I > would like to use IPv6. Could you suggest me some documents and some > manuals useful to implement IPv6, but avoiding problems for our > customers? > > In particular, I would like to avoid compatibility problems with VoIP > PBXs, network printers, alarm systems, etc ... > > In Italy only few ISPs provide IPv6 addresses and we would like to try > to reverse this negative trend compared to the rest of Europe. > > I hope you can help me understanding the advantages and opportunities > in investing in the direction of IPv6. > > Kind regards > > Alessandro > > Alessandro Valenza > Ufficio TLC > > > > Tel: *0571 1738257* <tel:0571%201738257> > Fax: *0571542536* <fax:0571542536> > > *www.enegan.it* <https://www.enegan.it/> > > CONFIDENZIALITÀ > Questo messaggio, inclusi gli eventuali allegati, è indirizzato solo > ai destinatari e può contenere informazioni riservate > e confidenziali. Se avete ricevuto il messaggio senza esserne un > destinatario, o un suo rappresentante autorizzato, la > presente comunicazione vale come formale divieto di diffusione del > contenuto del messaggio.Se avete ricevuto il messaggio > per errore, siete pregati di cancellarlo, assieme a tutti gli > allegati, dal vostro sistema e di informare > immediatamente il mittente. > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20190311/7a27b415/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image059076.jpg Type: image/jpeg Size: 4301 bytes Desc: not available URL: </ripe/mail/archives/ipv6-wg/attachments/20190311/7a27b415/attachment.jpg>
- Previous message (by thread): [ipv6-wg] IPv6 Implementation for an ISP
- Next message (by thread): [ipv6-wg] IPv6 Implementation for an ISP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]