Re: [DNSOP] SVCB without A/AAAA records at the service name

Paul Vixie <paul@redbarn.org> Fri, 15 January 2021 08:48 UTC

Return-Path: <paul@redbarn.org>
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 AD1D23A10D3 for <dnsop@ietfa.amsl.com>; Fri, 15 Jan 2021 00:48:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.162
X-Spam-Level:
X-Spam-Status: No, score=-2.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VmILXctfcCGR for <dnsop@ietfa.amsl.com>; Fri, 15 Jan 2021 00:48:17 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7B923A10D4 for <dnsop@ietf.org>; Fri, 15 Jan 2021 00:48:15 -0800 (PST)
Received: from [IPv6:2001:559:8000:c9:1984:9dec:95a3:b4ee] (unknown [IPv6:2001:559:8000:c9:1984:9dec:95a3:b4ee]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 8EA15C3F02; Fri, 15 Jan 2021 08:48:13 +0000 (UTC)
To: Martin Thomson <mt@lowentropy.net>
Cc: dnsop@ietf.org
References: <2e1054a0-5a7a-4d62-92a1-095217af82bb@www.fastmail.com>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <0d9e09a0-6644-34c2-3699-19b1ca49dec7@redbarn.org>
Date: Fri, 15 Jan 2021 00:48:11 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.44
MIME-Version: 1.0
In-Reply-To: <2e1054a0-5a7a-4d62-92a1-095217af82bb@www.fastmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_m_jYp5KwSYEshfRziKsFTV7kHU>
Subject: Re: [DNSOP] SVCB without A/AAAA records at the service name
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: Fri, 15 Jan 2021 08:48:23 -0000


Martin Thomson wrote on 2021-01-14 15:43:
> ...
> 
> The SVCB draft basically mandates a fallback to A/AAAA.  I think that
> this is not universal and that this should instead be made an
> option.
> 
> For HTTP, the fallback is necessary.  For a new protocol, a fallback
> could be undesirable.  Especially if you want to deploy that protocol
> using a service name on which you have already deployed HTTP.  If you
> don't want your HTTP servers getting connection attempts for the new
> protocol, the fallback is more nuisance than useful.

i see what you mean and i agree.

vixie