Re: [BEHAVE] Review of draft-boucadair-behave-dns-a64-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BEHAVE] Review of draft-boucadair-behave-dns-a64-01



Dear Andrew,

Yes, this may solve the problem when the prefix used to build the IPv4-embedded IPv6 address is a WKP or an NSP belonging to the prefix managed by the underlying IP network provider. But this is not the exclusive case that we would have: the NAT64 box can be located in a remote realm.

Cheers,
Med
 

-----Message d'origine-----
De : behave-bounces at ietf.org [mailto:behave-bounces at ietf.org] De la part de Mark Andrews
Envoyé : dimanche 8 novembre 2009 23:34
À : Brian E Carpenter
Cc : Andrew Sullivan; behave at ietf.org
Objet : Re: [BEHAVE] Review of draft-boucadair-behave-dns-a64-01


One could also publish prefixes via DHCP and insert them into to address selection algorithms to de-preference these addresses.  This should work for internal use and a ISP supplying a NAT64.  It also provides a mechanism to push DNS64 back into the application for when DNSSEC is in use.

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org
_______________________________________________
Behave mailing list
Behave at ietf.org
https://www.ietf.org/mailman/listinfo/behave

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.