> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Christian Huitema > Sent: Thursday, October 28, 2010 6:29 PM > To: Fred Baker; Margaret Wasserman > Cc: Roger Marquis; NAT66 HappyFunBall > Subject: Re: [nat66] e2e New Version Notification > > > As Keith points out, to maintain Dynamic DNS AAAA records, the device > > has to be able to determine its own external addresses. If a static > > DNS configuration is maintained and privacy addresses do not > > periodically change (which kind of calls for Dynamic DNS), the DNS service > > can > be maintained centrally without the collusion of the addressed systems. > > Another possibility is for the internal system to consider the "external" > address > provided by NAT-66 as a "virtual interface", similar to what would be obtained > for example by a tunnel to the external gateway. That means the internal > systems could learn the available address through some configuration function.
That's what SAF is. > Centralized DHCP servers come to mind, e.g. a DHCPv6 option providing the > translation value. Yes, that's one valid SAF mechanism. -Dave > > -- Christian Huitema > > > > _______________________________________________ > nat66 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nat66 _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
