nanog mailing list archives
NAT64 and matching identities
From: "Justin M. Streiner" <streiner () cluebyfour org>
Date: Mon, 18 Nov 2013 15:06:52 -0500 (EST)
It's looking more and more like NAT64 will be in our future. One of the valid concerns for NAT64 - much like NAT44 - is being able to determine the identity of a given user through the NAT at a given point in time. How feasible this is depends on how robust/scalable $XYZ's translation logging capabilities are, and possibly how easily that data can be matched against a source of identify information, such as RADIUS accounting logs, DHCP lease logs, etc.
Other IPv6 transition mechanisms appear to be no less thorny than NAT64 for a variety of reasons.
I'm curious to see how others are planning to tackle (or already have tacked) this issue. Discussing vendor-specific solutions is fine, but I think keeping things as platform/vendor agnostic as possible for the time being would allow this thread to be more beneficial to a wider audience.
The floor is open... jms
Current thread:
- NAT64 and matching identities Justin M. Streiner (Nov 18)
- Re: NAT64 and matching identities Tom Taylor (Nov 18)
- Re: NAT64 and matching identities Paul WALL (Nov 18)
- Re: NAT64 and matching identities Lee Howard (Nov 19)
- Re: NAT64 and matching identities Andrew Sullivan (Nov 19)
- Re: NAT64 and matching identities Fred Baker (fred) (Nov 19)
- RE: NAT64 and matching identities Don Bowman (Nov 19)
- RE: NAT64 and matching identities Ian Smith (Nov 19)
- RE: NAT64 and matching identities Justin M. Streiner (Nov 19)
- Re: NAT64 and matching identities Lee Howard (Nov 20)
- Re: NAT64 and matching identities Gary E. Miller (Nov 20)
(Thread continues...)
- Re: NAT64 and matching identities Tom Taylor (Nov 18)