Re: [DNSOP] Fundamental ANAME problems

Joe Abley <jabley@hopcount.ca> Sat, 03 November 2018 19:04 UTC

Return-Path: <jabley@hopcount.ca>
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 263DB1286D9 for <dnsop@ietfa.amsl.com>; Sat, 3 Nov 2018 12:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 pW0JRjSeZV2s for <dnsop@ietfa.amsl.com>; Sat, 3 Nov 2018 12:04:21 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 614AC126F72 for <dnsop@ietf.org>; Sat, 3 Nov 2018 12:04:21 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id z80-v6so4540915ljb.8 for <dnsop@ietf.org>; Sat, 03 Nov 2018 12:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=X8PXtGMuNkk+BVBsA4NBeQ5F97ID7V4kGVYmNXUDOsA=; b=YwCpSi11/FvaY+9QOSQJhvd6RLzi94LWTLx7Rnto0Rn2byknggNQotTE/J8/JYYiRK SzDb6IFowN2f9KTJHr0oBCFAERoVM0C6BbHMXwKEK+hgvU/eVcFzbZSWM3ObEDYhTgRJ nb+LWXmHwx0vDDZa2BZTFrsJUZtRnQ0KNQzRQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=X8PXtGMuNkk+BVBsA4NBeQ5F97ID7V4kGVYmNXUDOsA=; b=LkZSGQqxnF4DAxMQji3K8AnfyM9+Tl4dE3iqGpMqnH5IrAfLdjYSCjtSgLBUprVvzr haMCbZLXlWvL28BBd1LMxt8DT6IGYGdlvuAPhOaUSv3hCVGREFKlcK+pKj6YYs/67a5a xKrRbWtpSWxAwJrWnDlxQdJ5agZnDYZtzLtkbgv5JxQ/gB1M8IHf/av26532qsi63wWF ///g4azV8JurkHP3nZ4uuHGn4ba9gylO02ZkFQstvw3laNVyR99/Wdo20QelPPofIapp mqMr0YVzFVixlNEV7bev0zTVFUmRMYSVbnIdJcYL3Kno5dYx5tS+rzWC+cO+Gd3R+Eo+ vDlw==
X-Gm-Message-State: AGRZ1gL8f/i0A0wJQXe4fELuflPIZK/sBzi7oS6q6FvHzuu1gcAqZIXJ aQ63FfjcUx35GiYZs1AXcLx+aDOl4RPutQtTym09mA==
X-Google-Smtp-Source: AJdET5fH7vUojH6cUwvF+CiwW8zDOZJeMrQZLXEWSYD1g/bumqBLg4En+OU9YRsS0vx72xAj4wqMThvajY+AlcyZ6bA=
X-Received: by 2002:a2e:92ca:: with SMTP id k10-v6mr10246073ljh.103.1541271859601; Sat, 03 Nov 2018 12:04:19 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Sat, 3 Nov 2018 12:04:18 -0700
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <CAH1iCirXYsYB3sAo8f1Jy-q4meLmQAPSFO-7x5idDufdT_unXQ@mail.gmail.com> <CA+nkc8C6yVT62cW5QP-ec2ZT7FY_n48Ecr=CLeE6FS_1duBO8g@mail.gmail.com>
In-Reply-To: <CA+nkc8C6yVT62cW5QP-ec2ZT7FY_n48Ecr=CLeE6FS_1duBO8g@mail.gmail.com>
Date: Sat, 3 Nov 2018 12:04:18 -0700
Message-ID: <CAJhMdTOwU88BkukodL_zXcK1=JenExX4HL46Zzbw=+btLbDG2A@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gpzY_kJ5x8_RgsbwDmj1xnp5wAM>
Subject: Re: [DNSOP] Fundamental ANAME problems
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 03 Nov 2018 19:04:23 -0000

On Nov 3, 2018, at 03:20, Bob Harold <rharolde@umich.edu>; wrote:

> My preference would be a *NAME record that specifies which record types it applies to.  So one could delegate A and AAAA at apex to a web provider, MX to a mail provider, etc.  That would also be valuable at non-apex names.  But I am happy to support ANAME as part of the solution.

I don't understand this suggestion.

Some use-cases (or even hypothetical examples) might help.


Joe