IETF Logo Mail Archive

Re: [DNSOP] On painting the draft-ietf-dnsop-svcb-httpssvc bikeshed

Ted Lemon <mellon@fugue.com> Tue, 19 November 2019 10:53 UTC

Return-Path: <mellon@fugue.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 1D62D120903 for <dnsop@ietfa.amsl.com>; Tue, 19 Nov 2019 02:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 9W7uXMrNSHAP for <dnsop@ietfa.amsl.com>; Tue, 19 Nov 2019 02:53:01 -0800 (PST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 99806120289 for <dnsop@ietf.org>; Tue, 19 Nov 2019 02:53:01 -0800 (PST)
Received: by mail-qt1-x82f.google.com with SMTP id y39so24115546qty.0 for <dnsop@ietf.org>; Tue, 19 Nov 2019 02:53:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=D/n6loejbAMkSHNHDQrmy08vzMZfAdTxAGh75PmxK4E=; b=jZNKbzKGBEzZoDEEhNUtd+AtdZtQlAb0WLbzJ669yy62+eVQLUxuH6u/NDESztitOr 5HQcnTzFDATewZYrvFOpaaBei/RrsFlU0VCmNagzVE+uZ5WXRWovviLoqzLpmuKzx5X5 gsKoM/2QEnyP9CEN6TTae03jr05cU9MnBhuTlJWCCoJgaCiA9fti2AP4fiG0JlNGQORJ hwvN72CadNR3VGK335T6fOmXmdBw5sJDYorVG35CPhdC1kY7T8eHuRnthwLXcEHZ68jK OTzWi3oepIGfbvZpjAkTEaA5LVRGjGN3ujnxcrfFskNkleHrCMU8QSvpSHllhNlpK9YP 29wQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=D/n6loejbAMkSHNHDQrmy08vzMZfAdTxAGh75PmxK4E=; b=c6vqblbBPi3t8sJs4lSYrAfDz77HSFX15Nkm4IJICE0gMb7OFSFFq6Z0aTVThd5yXb mlvzCcptBymuz3BER9EEw1oXVr95NAa+o6oqtlBsaLgdtRyWRIVBduHroTyKh4j2Kx4l hkPcrhTwm3r7pMQX7UdiOfiGf2GTiPLPHCWIPglhaUDfpyCxOjbR0QqySazmNdVI/KFw uEEt8X27+RpbwaYdOCsT3g0kTGxXpJ25ktBWwbLtWLhM7mUEOEj9pVW1JKuOd5gZpxsj Kl5DSVKTOUBUXIK9x9mhQS9s3r2y6Lz8DrzAY7RQNMYn4zTEuifrS6NxPczLAdbjY2ZO ehNg==
X-Gm-Message-State: APjAAAWmITJzuOJbTSZ8KJmio7JU+Lj66COZHDfC95iVNAqewaRpmM/v JDI7K7If6CDQKS+vsRJJ8BjmmTSTf7C7Ew==
X-Google-Smtp-Source: APXvYqyayJru6mvMQctS2OBPqnpxV030oQbDxPKrDr1+zCuMYBPNCM0ZveQ6qUab9Yw6kU0uagLrtQ==
X-Received: by 2002:ac8:22c4:: with SMTP id g4mr31816964qta.45.1574160780448; Tue, 19 Nov 2019 02:53:00 -0800 (PST)
Received: from ?IPv6:2601:18b:300:36ee:9125:6a16:b164:3b45? ([2601:18b:300:36ee:9125:6a16:b164:3b45]) by smtp.gmail.com with ESMTPSA id n20sm10014879qkn.118.2019.11.19.02.52.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Nov 2019 02:52:59 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 19 Nov 2019 05:52:58 -0500
Message-Id: <C0EB3842-E9BE-4D9A-8041-5E8891A91706@fugue.com>
References: <a9faada9-1002-5a12-ed63-c96ded8133ca@nic.cz>
Cc: dnsop@ietf.org
In-Reply-To: <a9faada9-1002-5a12-ed63-c96ded8133ca@nic.cz>
To: Petr Špaček <petr.spacek@nic.cz>
X-Mailer: iPad Mail (17E177)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ppF-zZ0yOTzMGFEPsTd8SgY5bcA>
Subject: Re: [DNSOP] On painting the draft-ietf-dnsop-svcb-httpssvc bikeshed
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: Tue, 19 Nov 2019 10:53:06 -0000

On Nov 19, 2019, at 5:50 AM, Petr Špaček <petr.spacek@nic.cz> wrote:
> Please keep RR type name as one lexical unit!
> 
> Constructing the name from multiple tokens ("SVCB" "-" "HTTPS") will trigger all sorts of bugs all over the place. For example the venerable dnspython.org library would require rework before it would be able to support the new type named "SVCB-HTTPS".
> 
> What about SVCBWEB or WEBSVCB?
> 
> Or shorter SVC + WEBSVC?

I think it’s good to keep the protocol in the name, but agree with the syntax issue.  Given that http is dead, why not just HTTPSVC or HTTPSVCB?  There’s never going to be a competing no-TLS version of the RRtype.

v2.23.0 | Report a Bug | By Email