From marka@isc.org  Fri Jul  8 05:48:53 2016
Delivered-To: bind9-bugs@bugs.isc.org
Subject: dns64 should exclude mapped v4 addresses by default.
X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.0
Return-Path: <marka@isc.org>
X-Original-To: bind9-bugs@bugs.isc.org
Date: Fri, 08 Jul 2016 15:48:48 +1000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org
Message-ID: <20160708054848.ABABB4DC144A@rock.dv.isc.org>
To: bind9-bugs@isc.org
From: "Mark Andrews" <marka@isc.org>
X-RT-Original-Encoding: ascii
content-type: text/plain; charset="utf-8"
X-RT-Interface: Email
Content-Length: 1175


We provide the mechanism (exclude) but don't populate exclude with a
default of ::ffff:0.0.0.0/96.

5.1.4.  Special Exclusion Set for AAAA Records

   Some IPv6 addresses are not actually usable by IPv6-only hosts.  If
   they are returned to IPv6-only querying agents as AAAA records,
   therefore, the goal of decreasing the number of failure modes will
   not be attained.  Examples include AAAA records with addresses in the
   ::ffff:0:0/96 network, and possibly (depending on the context) AAAA
   records with the site's Pref64::/n or the Well-Known Prefix (see
   below for more about the Well-Known Prefix).  A DNS64 implementation
   SHOULD provide a mechanism to specify IPv6 prefix ranges to be
   treated as though the AAAA containing them were an empty answer.  An
   implementation SHOULD include the ::ffff/96 network in that range by
   default.  Failure to provide this facility will mean that clients
   querying the DNS64 function may not be able to communicate with hosts
   that would be reachable from a dual-stack host.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org