IETF Logo Mail Archive

Re: [DNSOP] Fwd: HTTPSSVC record draft

Joe Abley <jabley@hopcount.ca> Wed, 10 July 2019 00:35 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 1A069120098 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 17:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 GmHbt6pfNDAr for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 17:35:38 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 319F7120048 for <dnsop@ietf.org>; Tue, 9 Jul 2019 17:35:38 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id r9so256065ljg.5 for <dnsop@ietf.org>; Tue, 09 Jul 2019 17:35:37 -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=rZ/z0+8Vx0fGxF9Ntrnfi6ctJk7GP9MR0a70d9pxlsE=; b=EoZcGoH+TagY8GDD5ZerhVE7dYEjlaq+n4ZAr+PQzR4Bd/Dn2iJ3lk2UYhfRHMIPtU Iaz0KTvT4g0Dn5xrLc1dXQcBUHiYHlW5gKjMk/Ywus1lX5bCQWVcgr1A++yOs/CHeJxi OASzs+xp+u2B1cBCeW9LOczAKvOhv2TkiJOZc=
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=rZ/z0+8Vx0fGxF9Ntrnfi6ctJk7GP9MR0a70d9pxlsE=; b=izHK+yP0mNTwLSdIP2SU6nI0QCz/rhdqdHWU64VKHHOuHFWGSzTv7e75+P4TzJf5Fi JrMcIeatOlzlogKT99qhqqZl7yjN7OzTdO8PxODVpweVPh1yG8XPp0076kLoVkk/UYe4 cUHOTQ5KQzL1qUQLoy+9128mDtHQipprpBZtEiCQnR92v38JWr5b+5khM+2ErMUFf7b1 gXUUuv3EMS8kBuOwbGk+FEzyYpezmU00P38AnEsYdFjVCH8e2AWGf8aURTT8F+dUV38l HqrzL+XP9y5apyiZIgbJL4t4iQb0MzgXoIukFL50PcXOOiZkQQ4GlonpYU5UsNAJYqJK RIww==
X-Gm-Message-State: APjAAAUaOnmgwvdOQ+aQBPbmjpWP+2xmaQLFrNh9BlwlYtC3k0tilRQ1 wPyOQ698fzBFt3BPShi6jhtwe8CqDdaEQBDJ9Pzq+g==
X-Google-Smtp-Source: APXvYqwTSipJbz8/LBH/qgPDD+7tKDgsvMWL5nUeCTOyIMtStmZ/oCklA3+0BcGRLzOQsv1ump/jfM39vANRMPxWf8w=
X-Received: by 2002:a2e:b1c1:: with SMTP id e1mr15344195lja.228.1562718936270; Tue, 09 Jul 2019 17:35:36 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 9 Jul 2019 17:35:35 -0700
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <CAKC-DJikByP+wX-GoD6ntpUWTbr6ioJzB4i8nGQL4NtPWePL3g@mail.gmail.com> <CADyWQ+EA4e8ye9e8AWomrXko06cnT+izfqmK+fHLWGB5NBveLg@mail.gmail.com> <1845D2AE-4FF2-47B2-A01D-274401A23676@isc.org> <1745437.OzvAMyqktN@linux-9daj>
In-Reply-To: <1745437.OzvAMyqktN@linux-9daj>
Date: Tue, 09 Jul 2019 17:35:35 -0700
Message-ID: <CAJhMdTPu68vbfReCDSftS9ywVbjaZmTTgNQOpemG2uk4UbQoOA@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, Erik Nygren <erik+ietf@nygren.org>, Ray Bellis <ray@bellis.me.uk>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5uR8v5ANfeZUXqpErn3M0QUbJ20>
Subject: Re: [DNSOP] Fwd: HTTPSSVC record draft
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, 10 Jul 2019 00:35:39 -0000

On Jul 9, 2019, at 20:11, Paul Vixie <paul@redbarn.org> wrote:

> everything other than HTTPS can just use SRV.
>
> ANAME is (should be) toast(ed).

Didn't we get to this point by acknowledging that there was a gap
between now and the glorious future where SRV and unnamed alternatives
for HTTPS, and that the gap was already being filled by multiple,
different, ANAME-looking things?

The point of ANAME was to give us some multi-provider/Interop options
while the trucks roll, I thought. They are not fast trucks. It has
taken 23 years to get from RFC 2052 to here.


Joe

v2.23.0 | Report a Bug | By Email