>>>>> "Aleksi" == Aleksi Suhonen <[email protected]> writes: Aleksi> Sorry for late response. It's the summer holiday season Aleksi> here. O:-)
Aleksi> On 07/06/2012 05:59 PM, Michael Richardson wrote:
>>
>>>>>>> "Aleksi" == Aleksi Suhonen<[email protected]> writes:
Aleksi> Within an hour, all the IPv4 addresses in the pool for our
Aleksi> NAT64 were registered to this one device.
>> Do I understand that you attempt to provide a single IPv4 address
>> 1:1 with a an internal IPv6 address? (NAT vs NAPT)
Aleksi> Yes. Stateless
Aleksi> NAT64. http://tools.ietf.org/html/rfc6144#section-3.2.1
okay, so every v6 device gets 1 IPv4.
I think that few people have enough IPv4 to do this, and your research
demonstrates the problems with trying to do that. I think that most
will do stateful NAPT64.
>> Can you tell me what your expiry time is for reclaiming the IPv4
>> address?
Aleksi> 2 hours. However, anything above 5 minutes will yield the
Aleksi> same result on today's Internet. And 5 minutes is too short.
>> Would IPv6 ping'ing the internal device help?
Aleksi> Hmm? Help with what? I'm not sure I understand you.
Would it help to expire the lease faster if you did a liveness check on
the IPv6 device.
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpfiuPcuTyAh.pgp
Description: PGP signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
