This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] Follow up on RIPE67 IPv6 Only experiment
- Previous message (by thread): [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment
- Next message (by thread): [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ondřej Caletka
Ondrej.Caletka at cesnet.cz
Fri Jan 10 12:39:11 CET 2014
Dne 10.1.2014 10:05, Dan Wing napsal(a): > NAT64 works with host DNSSEC validation, provided that DNSSEC-validating host also does its own DNS64 function. The interaction of NAT64 with host DNSSEC validation is described in RFC6147. And it's worth noting that RFC 7050 finally adds ability for end host to discover whether NAT64 is used in the network and what prefix is used. This is quite handy information for endpoint to do the DNS64 on its own. -- Ondřej Caletka -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5563 bytes Desc: Elektronicky podpis S/MIME URL: </ripe/mail/archives/ipv6-wg/attachments/20140110/d70adab3/attachment.p7s>
- Previous message (by thread): [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment
- Next message (by thread): [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]