User-Agent: Microsoft-MacOutlook/10.10.3.181015
Date: Tue, 06 Nov 2018 21:07:04 +0700
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: Christian Huitema <huitema@huitema.net>,
 Congxiao Bao <congxiao@cernet.edu.cn>,
 <mohamed.boucadair@orange-ftgroup.com>,
 Dave Thaler <dthaler@microsoft.com>, Xing Li <xing@cernet.edu.cn>,
 <spencerdawkins.ietf@gmail.com>, <dwing@cisco.com>,
 <huitema@microsoft.com>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>,
 <behave@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID: <84FEE0D5-0BC2-4C35-9991-05F1E724B143@consulintel.es>
Thread-Topic: [BEHAVE] [Technical Errata Reported] RFC6052 (5547)
References: <20181106085323.07C1BB80008@rfc-editor.org>
 <27516408-05B3-4C08-B40E-B01E44525AB5@gmail.com>
 <5a5d6ac6-2d9a-96ee-118d-3601e47804cc@huitema.net>
 <0F8964C5-7C2F-4C90-854A-D1ADF02D7C08@gmail.com>
 <75370789-566F-4187-8374-719E40D59D31@consulintel.es>
 <FBAAB5CB-2AC4-43B1-A931-15E75662B7EF@gmail.com>
In-Reply-To: <FBAAB5CB-2AC4-43B1-A931-15E75662B7EF@gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/xCh3vDdzwLxIfxpVmBUj5ZDTY2g>
Subject: Re: [BEHAVE] [Technical Errata Reported] RFC6052 (5547)
Precedence: list

Totally agree and is the case that I call "foreign DNS" in draft-ietf-v6ops=
-nat64-deployment, but I was meaning that, as most of the NAT64 deployments=
 use the WKP, changing among them doesn't break, so at least we "break less=
".

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: Fred Baker <fredbaker.ietf@gmail.com>
Fecha: martes, 6 de noviembre de 2018, 20:52
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: Christian Huitema <huitema@huitema.net>, Congxiao Bao <congxiao@cernet.=
edu.cn>, <mohamed.boucadair@orange-ftgroup.com>, Dave Thaler <dthaler@micro=
soft.com>, Xing Li <xing@cernet.edu.cn>, <spencerdawkins.ietf@gmail.com>, <=
dwing@cisco.com>, <huitema@microsoft.com>, "Mirja Kuehlewind (IETF)" <ietf@=
kuehlewind.net>, <behave@ietf.org>, RFC Errata System <rfc-editor@rfc-edito=
r.org>
Asunto: Re: [BEHAVE] [Technical Errata Reported] RFC6052 (5547)

   =20
   =20
    > On Nov 6, 2018, at 7:16 PM, JORDI PALET MARTINEZ <jordi.palet@consuli=
ntel.es> wrote:
    >=20
    > The advantage I see with a WKP is that you can roam to another NAT64 =
(and/or DNS64) without changing configs, and also, that you may ignore the =
prefix discovery mechanism (I've seen this coded in some places), if you pr=
esume that the WKP is the "default" one ...
   =20
    That, of course, is exactly the problem with RFC 7050. If you are using=
 the preferred resolver, you get one prefix, and if you're using 8.8.8.8 (a=
s many do), you get another. A Well Known Prefix is a great way to pick the=
 wrong one, or one that doesn't exist.
    -----------------------------------------------------------------------=
---------
    Victorious warriors win first and then go to war,
    Defeated warriors go to war first and then seek to win.
         Sun Tzu
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.