Re: [DNSOP] The Larger Discussion on Differences in Response Drafts

Marek Vavruša <mvavrusa@cloudflare.com> Thu, 18 August 2016 20:11 UTC

Return-Path: <mvavrusa@cloudflare.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D076112D98D for <dnsop@ietfa.amsl.com>; Thu, 18 Aug 2016 13:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiKRridT4sdq for <dnsop@ietfa.amsl.com>; Thu, 18 Aug 2016 13:11:29 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05C8B12D1A4 for <dnsop@ietf.org>; Thu, 18 Aug 2016 13:11:29 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id z8so1197050ywa.1 for <dnsop@ietf.org>; Thu, 18 Aug 2016 13:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=yBISi6Hg+NSy98/iyn9nDhecpDy6zDqOSS44D/6bZvE=; b=bHeCybEmS5t/ctTBTF49AMYyTC83cG1LE8/8EcrGd1ngBzLowz/BSl0mj/ll9RirCd 59yB4LA38wIUsOnyEI5xObV1NLHO64MoO0qxzWKSbSKw/h4ToxKKPpTP5HAvH3ckSVza sIl9L4IZjHQcg6eGicgixdZUL8SXOdgJZG7jA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=yBISi6Hg+NSy98/iyn9nDhecpDy6zDqOSS44D/6bZvE=; b=CvA5bbD6I89JEUQn9E2FbN6mi50ABV27Ja8jncTCaYB7Gb6WV7L30hQw67djHWd0IW E1wF9hdBCUm5P997zTN9TrTLQbySb7qXbs3cGfM6opHF6AK9ZIKoF0yh8XJLXEaKxa4+ Hxley5RQ65QcotnFJAXyQoVouVsHelQ2FLOjJaBRCY1cHKty93lei1dbRE1TRo4/vuW4 LVtfsNFXY1nVSbAuZcBfFAVOLheDQIxw9ASfKeVYULDZVNEdhtEzK/TUOrefioVBFOUC 3hiFMw0q5Kjm9LULiz5egGrT2/8v5b2CkHbPJ9ZVlLGEa/okyxEAB9vfI81R/JMw0Ys3 l1cA==
X-Gm-Message-State: AEkooutrI3H7iYVvK/QUdj2eruFB7JjBDnhKpkWFhTBLqEbD/vhiZfWcLhPt7LNdCEqZQm6gqxtyszn0XVUEyOKw
X-Received: by 10.129.39.200 with SMTP id n191mr3459331ywn.16.1471551088279; Thu, 18 Aug 2016 13:11:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.164.199 with HTTP; Thu, 18 Aug 2016 13:11:23 -0700 (PDT)
In-Reply-To: <52403FB3-2187-4E88-8909-E00483C9EF03@vpnc.org>
References: <DAE8C592-A5A6-4EDA-A100-67B7DD900C36@vpnc.org> <20160818175713.16299.qmail@ary.lan> <CAC=TB12PtSpU3_mL0+QdmJwqvfYm4go=fmtK80aRg7On6XgfHg@mail.gmail.com> <52403FB3-2187-4E88-8909-E00483C9EF03@vpnc.org>
From: Marek Vavruša <mvavrusa@cloudflare.com>
Date: Thu, 18 Aug 2016 13:11:23 -0700
Message-ID: <CAC=TB118Q+pqZDxf150ZS2uZatK1CjDuyEMP1atFaey=xVzn9Q@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AMPuMlifJUs6R_SP7hWUjan1jvQ>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] The Larger Discussion on Differences in Response Drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 20:11:31 -0000

On Thu, Aug 18, 2016 at 12:52 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On 18 Aug 2016, at 11:29, Marek Vavruša wrote:
>
>> Or SRV.
>
>
> I disagree that a user, when asking for a SRV record, doesn't know that it
> is likely that they would want the results for the information that comes
> back in the RDATA.

No question about that, but she doesn't know what the target name is.
Expressing "I want SRV type for this name, and A/AAAA for the SRV
record targets" is doable, at the cost of additional complexity on
both client and server.

>> These are cases where authoritative/resolver adding
>> interesting records as additionals works better.
>> Authoritatives have been doing that with extra SOA/NS in authority for
>> a while (for positive answers), but now
>> resolvers can hardly use them if these records are not secure.
>
>
> Security of additional data is important, but orthogonal to what can be
> asked for or pushed.
>
>> Regardless of which draft is going to be adopted,
>
>
> This thread is not about "which draft", it is about what is needed.

Thank you, I should have phrased that differently.

> --Paul Hoffman