From: Ted Lemon <mellon@fugue.com>
Message-Id: <69725356-F683-4FAF-A130-D08353D9169F@fugue.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_95344181-83BC-4AA9-911A-CADC452AA0B8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 17 Aug 2017 22:20:18 -0400
In-Reply-To: <CAH1iCip41ohOxKZdqEN-NOyRuv-d1knxuwR3LJNHOC+C6QJC3g@mail.gmail.com>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
To: Brian Dickson <brian.peter.dickson@gmail.com>
References: <CAH1iCiqr_9Om-jwRq6mLABH3cZ1D0qptLHVUQ1YtZn0ViQM=Mw@mail.gmail.com>
 <597FEBF7-7D11-4E50-9B79-63301914F75B@fugue.com>
 <CAH1iCip41ohOxKZdqEN-NOyRuv-d1knxuwR3LJNHOC+C6QJC3g@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_SZxe0388KuUG-1G_JR33TFVaPU>
Subject: Re: [DNSOP] Localhost - more reliable options?
Precedence: list


--Apple-Mail=_95344181-83BC-4AA9-911A-CADC452AA0B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

El 17 ag 2017, a les 21:54, Brian Dickson =
<brian.peter.dickson@gmail.com> va escriure:
> If you're trying to use "localhost", that means you're using some kind =
of name resolution, whether it be DNS, /etc/hosts, NIS+, or anything =
else.
> I'm suggesting that by using DNS, you can take advantage of what DNS =
has to offer, which includes potentially DNSSEC.

DNSSEC can't work, or even be used, if you are spoofing localhost.   If =
you used DNSSEC, the answer would fail validation.


--Apple-Mail=_95344181-83BC-4AA9-911A-CADC452AA0B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">El 17 ag 2017, a les 21:54, Brian Dickson &lt;<a =
href=3D"mailto:brian.peter.dickson@gmail.com" =
class=3D"">brian.peter.dickson@gmail.com</a>&gt; va =
escriure:<div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">If =
you're trying to use "localhost", that means you're using some kind of =
name resolution, whether it be DNS, /etc/hosts, NIS+, or anything =
else.</div><div style=3D"font-family: Helvetica; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D"">I'm suggesting that by using =
DNS, you can take advantage of what DNS has to offer, which includes =
potentially DNSSEC.</div></div></blockquote><br =
class=3D""></div><div>DNSSEC can't work, or even be used, if you are =
spoofing localhost. &nbsp; If you used DNSSEC, the answer would fail =
validation.</div><div><br class=3D""></div></body></html>=

--Apple-Mail=_95344181-83BC-4AA9-911A-CADC452AA0B8--