MIME-Version: 1.0
In-Reply-To: <CAN6NTqwR76PiBVwmmZ2JfFu+OkV_FQT7JiqYOp_w4N72QDWHtg@mail.gmail.com>
References: <CAOZSDgCw4HA05uE0d73cru3EfuOzAJ3Pdg2SsYZmY3f49+vc2w@mail.gmail.com>
 <CAN6NTqwR76PiBVwmmZ2JfFu+OkV_FQT7JiqYOp_w4N72QDWHtg@mail.gmail.com>
From: Richard Gibson <rgibson@dyn.com>
Date: Thu, 30 Mar 2017 11:04:12 -0400
Message-ID: <CAC94RYbuD2OUQxbim_VOdmzAgAPD+Z_jiN33i_AfxU2gGxZ+zQ@mail.gmail.com>
To: =?UTF-8?B?w5NsYWZ1ciBHdcOwbXVuZHNzb24=?= <olafur@cloudflare.com>
Cc: Anthony Eden <anthony.eden@dnsimple.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=001a1142fb22b6cf48054bf40270
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/v-ZK7UUIpowwI9JgTaofDuo_XAE>
Subject: Re: [DNSOP] New draft for ALIAS/ANAME type
Precedence: list

--001a1142fb22b6cf48054bf40270
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I don't think you can drop section 3.4 completely, but it should be updated
to acknowledge Refuse-Any
<https://tools.ietf.org/html/draft-ietf-dnsop-refuse-any-04#section-4>.
Only behavior 2 (HINFO synthesization) allows total ignorance of special
ALIAS behavior; every other (including conventional) needs modification to
deal with ANY queries against names at which ALIAS is the only RRSet.

On Thu, Mar 30, 2017 at 10:34 AM, =C3=93lafur Gu=C3=B0mundsson <olafur@clou=
dflare.com>
wrote:

> Anthony,
>
> Good writeup
>
> Section 3.4 is in conflict with Refuse-Any draft (in WGLC)
> IMHO there is no need to say that there is special processing for ANY
> query;  so drop section 3.4
>
> Olafur
>
>
> On Wed, Mar 29, 2017 at 9:51 AM, Anthony Eden <anthony.eden@dnsimple.com>
> wrote:
>
>> After attending the dnsop meeting on Monday I decided it was time I
>> submitted my first ID for review:
>>
>> https://datatracker.ietf.org/doc/draft-dnsop-eden-alias-rr-type/
>>
>> This draft describes the ALIAS/ANAME record (aka CNAME-flattening)
>> that numerous vendors and DNS providers are now supporting in
>> proprietary fashions. I hope that this draft will eventually lead to a
>> good mechanism for interop of ALIAS/ANAME records.
>>
>> Sincerely,
>> Anthony Eden
>>
>> --
>> DNSimple.com
>> http://dnsimple.com/
>> Twitter: @dnsimple
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

--001a1142fb22b6cf48054bf40270
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t think you can drop section 3.4 completely, but=
 it should be updated to acknowledge <a href=3D"https://tools.ietf.org/html=
/draft-ietf-dnsop-refuse-any-04#section-4">Refuse-Any</a>. Only behavior 2 =
(HINFO synthesization) allows total ignorance of special ALIAS behavior; ev=
ery other (including conventional) needs modification to deal with ANY quer=
ies against names at which ALIAS is the only RRSet.</div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Thu, Mar 30, 2017 at 10:34 AM, =
=C3=93lafur Gu=C3=B0mundsson <span dir=3D"ltr">&lt;<a href=3D"mailto:olafur=
@cloudflare.com" target=3D"_blank">olafur@cloudflare.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Anthony,=C2=A0<div><=
br><div>Good writeup=C2=A0</div><div><br></div><div>Section 3.4 is in confl=
ict with Refuse-Any draft (in WGLC)=C2=A0</div><div>IMHO there is no need t=
o say that there is special processing for ANY query; =C2=A0so drop section=
 3.4=C2=A0</div><div><br></div><div>Olafur</div><div><br></div></div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D"">=
On Wed, Mar 29, 2017 at 9:51 AM, Anthony Eden <span dir=3D"ltr">&lt;<a href=
=3D"mailto:anthony.eden@dnsimple.com" target=3D"_blank">anthony.eden@dnsimp=
le.com</a>&gt;</span> wrote:<br></span><div><div class=3D"h5"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">After attending the dnsop meeting on Monday I decided it =
was time I<br>
submitted my first ID for review:<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-dnsop-eden-alias-rr-type/=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr>o=
c/draft-dnsop-eden-alias-rr-t<wbr>ype/</a><br>
<br>
This draft describes the ALIAS/ANAME record (aka CNAME-flattening)<br>
that numerous vendors and DNS providers are now supporting in<br>
proprietary fashions. I hope that this draft will eventually lead to a<br>
good mechanism for interop of ALIAS/ANAME records.<br>
<br>
Sincerely,<br>
Anthony Eden<br>
<span class=3D"m_-9051819817375293335HOEnZb"><font color=3D"#888888"><br>
--<br>
DNSimple.com<br>
<a href=3D"http://dnsimple.com/" rel=3D"noreferrer" target=3D"_blank">http:=
//dnsimple.com/</a><br>
Twitter: @dnsimple<br>
<br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/dnsop</a><br>
</font></span></blockquote></div></div></div><br></div>
<br>______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
<br></blockquote></div><br></div>

--001a1142fb22b6cf48054bf40270--