A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : DNS Multiple QTYPEs
Author : Ray Bellis
Filename: draft-bellis-dnsext-multi-qty
On 02/01/2018 09:27, internet-dra...@ietf.org wrote:
> Title : DNS Multiple QTYPEs
> Author : Ray Bellis
> Filename: draft-bellis-dnsext-multi-qtypes-05.txt
> Pages : 7
> Date: 2018-01-02
This was just a "keepalive" update, with no text changes.
Stephane Bortzmeyer wrote:
> On Mon, Dec 11, 2017 at 07:30:27AM -0800,
> Paul Hoffman wrote
> a message of 16 lines which said:
>
> > Some of the new terms added to the terminology-bis draft
> > (https://datatracker.ietf.org/doc/draft-ietf-dnsop-terminology-bis/)since
> > RFC 7719 can expose w
On 23 Dec 2017, at 11:59, Geoff Huston wrote:
On 22 Dec 2017, at 8:44 am, Ray Bellis wrote:
On 21/12/2017 15:36, Robert Story wrote:
I reread the draft today, and noticed that two things aren't
specified.
The first is the contents of the A/ RRSET returned, and the
second
is the TTL fo
> This answer doesn't seem to fully address Robert's and Ray's questions. Why
> use an A/ query if you aren't going to do anything with the result? If
> you are going to use A/, you have to tell resolvers what to return in the
> results. Using a new RRtype would have clearer semantics.
> On 3 Jan 2018, at 1:33 pm, Geoff Huston wrote:
>
>> This answer doesn't seem to fully address Robert's and Ray's questions. Why
>> use an A/ query if you aren't going to do anything with the result? If
>> you are going to use A/, you have to tell resolvers what to return in
>> the
