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/ripe-atlas@ripe.net/
[atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Previous message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Next message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sanjeev Gupta
ghane0 at gmail.com
Thu Mar 26 15:37:35 CET 2015
On Thu, Mar 26, 2015 at 9:31 PM, Roman Mamedov <rm at romanrm.net> wrote: > > NAT66 is not (and should not be) common, however there is no harm in doing > an > inobtrusive check to see if it's deployed, or to collect stats on the > scale of > such deployments. I am part of a team deploying IPv6 in S E Asia, for enterprises in their offices. As we do not have clarity on who the ISP will be, and this will change frequently till v6 availability stabilises, use of ULA is common. A NAT66 device is used much a normal IPv4 NAT gateway; the NAT66 means that if the upstream IPv6 prefix address changes, all the PCs do ot end up with new addresses. -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20150326/4d3eb5aa/attachment.html>
- Previous message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Next message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]