Colin,
On Aug 30, 2007, at 11:11 PM, Colin Alston wrote:
For running dual-stack, you don't need public IPv4 addresses.
I thought that at a bare minimum, you needed public IPv4 addresses
for the NAT gateways and any public facing IPv4 services.
In a world where people need IPv6 facing services, it doesn't
matter whether you are using private or public IPv4 for connecting
core infrastructure.
Well, yes. However, if we're in a world where people need IPv6
facing services, then we're done. The problem is that people who can
only obtain IPv6 addresses from their registry will most likely still
need to gain access to or provide IPv4 services for the foreseeable
future. One possible solution is for the ISP to provide a single
public IPv4 address to customers for a NAT gateway as well as offer
IPv4 hosting services, aggregating multiple customers' services on a
single IPv4 address. Another option would be for ISPs to simply
require their customers to come with whatever IPv4 addresses they
need. Note that the former is a better choice from the perspective of
the routing system.
Regards,
-drc
_______________________________________________
rpd mailing list
[email protected]
https://lists.afrinic.net/mailman/listinfo.cgi/rpd