At Fri, 7 Apr 2017 18:11:39 +,
Evan Hunt wrote:
> Here's the new ANAME draft I mentioned last week.
>
> This is similar to existing non-standard approaches (ALIAS records,
> CNAME-flattening, etc) but also sends the ANAME record to the resolver so
> that, if the resolver understands the ANAME
Thank you Evan and Petr fro your comments. I thought I would be able to
provide you some text this week... but I am running late. I will send you
some text next week.
I agree with your comments, and will make my best to address them. I also
came with other requirements.
Yours,
Daniel
On Fri, Apr
i think we can't use something in a standard that doesn't have a
canonical format. if there is a F(name) that produces a minimal I18N
result which is the same as any other F(name) that would look the same
or mean the same if written, then we should outlaw on-the-wire strings
that are not in that ca
On Thu, Apr 13, 2017 at 02:41:20PM -0400, Viktor Dukhovni wrote:
> What I should have said is that the variant with the upper case
> first letter is invalid (as opposed to being "different") in
> IDNA2008. This is IMHO a poor user interface, so running code
> will generally go with UTS#46 (increas
> On Apr 13, 2017, at 7:30 AM, dnsop-requ...@ietf.org wrote:
>
> Well, IIRC they sensibly converged on a case-folded normal form
> that ensures that https://Духовный.org maps to the same underlying
> wire-form domain as https://духовный.org, i.e. both result in
> queries for xn--b1adqpd3ao5c.org.
Hi Bob,
Thanks you for the clarifications, I have updated my local copy with all
your comments.
Yours,
Daniel
[1]
https://github.com/mglt/draft-mglt-dnsop-dnssec-validator-requirements/blob/master/draft-mglt-dnsop-dnssec-validator-requirements.xml
On Fri, Apr 7, 2017 at 7:35 PM, Daniel Migault
On Thu, Apr 13, 2017 at 02:39:36AM +, Viktor Dukhovni wrote:
>
> Well, IIRC they sensibly converged on a case-folded normal form
> that ensures that https://Духовный.org maps to the same underlying
> wire-form domain as https://духовный.org, i.e. both result in
> queries for xn--b1adqpd3ao5c.o
Hello,
On 13 Apr 2017, at 11:53, Lanlan Pan wrote:
Hi Peter,
one question, will authoritative server return multiple ANAME RRs for
the
same domain at one dns query ?
for example,
www.example.com ANAME us.www.example.com
www.example.com ANAME cn.www.example.com
or return only one selec
Hi Peter,
one question, will authoritative server return multiple ANAME RRs for the
same domain at one dns query ?
for example,
www.example.com ANAME us.www.example.com
www.example.com ANAME cn.www.example.com
or return only one selected ANAME RR for one domain ? (based on
authoritative's
On 11 Apr 2017, at 17:54, Tony Finch wrote:
When an ANAME record is present at a DNS node and a query is
received
by an authoritative server for type A or , the authoritative
server returns the ANAME RR in the answer section.
Wouldn't it be safer to put the ANAME in the additional
10 matches
Mail list logo