IETF Logo Mail Archive

Re: [DNSOP] ANAME in answer or additional section [issue #62]

Joe Abley <jabley@hopcount.ca> Wed, 12 June 2019 02:41 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 B30E4120089 for <dnsop@ietfa.amsl.com>; Tue, 11 Jun 2019 19:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 vsr79Wu40jvF for <dnsop@ietfa.amsl.com>; Tue, 11 Jun 2019 19:41:40 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 EE96512002F for <dnsop@ietf.org>; Tue, 11 Jun 2019 19:41:39 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id o13so13668502lji.5 for <dnsop@ietf.org>; Tue, 11 Jun 2019 19:41:39 -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; bh=LyQ9gDY8xNbJsUbIAs+zhHCfo1CLEVUoB/HLlV8u+aw=; b=ZGpfSt/Em2nZh24+C5ccndpHAgBWsMuLyYbus0L0uHnZYAFS0qXW1L1+hsCVLFhhiU hyENzDxQ/orGNJnmOdVLMa5os5e0NPBcCGLqNA017DEN1hihoyDa9MdNTQ1mWVp8gfnU EDi+IiKxtQQd/HDPxhCGyzLl44YZOlrcoKzKg=
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; bh=LyQ9gDY8xNbJsUbIAs+zhHCfo1CLEVUoB/HLlV8u+aw=; b=XMvjhZYob8QCUBkZtMmC7XPkxQOfJP7za0YrJz69+8LWThlf2/NsoxOb3DpmjWIhhg 5skgZk0FuSraQ7f+oK2MCFzYqG2T4+xbgQvIoZrZpgzPkm+8wUGv+Wzu0sVLYEBqjyiU AhNZo1AIK8IynGt4yCiwoj3F23PBQpyRd7uyzM7zpJZtX463KTe8ELo9dFLfJF7jERTA ilKkmLpRrCgK73kl0bOdVu4Dvu2okxb6hrkNIcH9t29+hnFdMXqqZcZpiOZz5Cju/i4D qp3ANWnnjM370BXbEmoq8U9eDMIjCwyxid+Li4wPr852Owu0gv85ABA7vf/Q+nr9T/c4 aIsA==
X-Gm-Message-State: APjAAAVNsgkneImkjqVdVNMGTxGpOZHK14hO510wo05GLg44BKpAmtFp csqn/W8EvFKTa19OqXA/NeMaaIMsL4gdo/SEs3d4tbgT96c=
X-Google-Smtp-Source: APXvYqzze96nDQRH6uESMB6DRiwLFjC4H5WnsvZPItVnw9UGGe0V7hukeNyhq+aXIbM70UtFWg/qoZXLxR7dPESBIR4=
X-Received: by 2002:a2e:9950:: with SMTP id r16mr8385851ljj.173.1560307298161; Tue, 11 Jun 2019 19:41:38 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 11 Jun 2019 19:41:37 -0700
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <3b136e34-7ec0-e144-2c2a-0885185ec2b1@pletterpet.nl> <20190612000459.GA60387@isc.org> <CAOZSDgCB5wmnYEP4Kf6v7v6tY=F=jwX3zFS04vCt5GmwOq07Sw@mail.gmail.com>
In-Reply-To: <CAOZSDgCB5wmnYEP4Kf6v7v6tY=F=jwX3zFS04vCt5GmwOq07Sw@mail.gmail.com>
Date: Tue, 11 Jun 2019 19:41:37 -0700
Message-ID: <CAJhMdTORCziZqzj-CSqNdztDK4HSEjAwz-Ye7mur86zyGbwnWw@mail.gmail.com>
To: Anthony Eden <anthony.eden=40dnsimple.com@dmarc.ietf.org>
Cc: Evan Hunt <each@isc.org>, Matthijs Mekking <matthijs@pletterpet.nl>, "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/90Qm0mTtIdlZncCSB49bF1AVA8A>
Subject: Re: [DNSOP] ANAME in answer or additional section [issue #62]
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: Wed, 12 Jun 2019 02:41:42 -0000

On Jun 11, 2019, at 20:11, Anthony Eden
<anthony.eden=40dnsimple.com@dmarc.ietf.org> wrote:

> I'm a fan of Michael's suggestion of using EDNS to signal that the authoritative should return ALIAS vs synthesizing. Any reason this won't work?

It won't work unless it's implemented. On a grand scale, then, it
won't work unless it's implemented everywhere. The combined lifting of
implementation, Interop and deployment is significant; is it worth it?


Joe

v2.23.0 | Report a Bug | By Email