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

Bob Harold <rharolde@umich.edu> Tue, 19 November 2019 14:40 UTC

Return-Path: <rharolde@umich.edu>
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 B7A3412084B for <dnsop@ietfa.amsl.com>; Tue, 19 Nov 2019 06:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=umich.edu
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 Z0cdncSALgJa for <dnsop@ietfa.amsl.com>; Tue, 19 Nov 2019 06:40:28 -0800 (PST)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 30E261200B1 for <dnsop@ietf.org>; Tue, 19 Nov 2019 06:40:27 -0800 (PST)
Received: by mail-lf1-x12e.google.com with SMTP id f18so4912197lfj.6 for <dnsop@ietf.org>; Tue, 19 Nov 2019 06:40:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C+83WGng3oBk6ZNDUqMMAEBvlGTAcHjYn21BKp1mShQ=; b=DWWPvB5RZMjgcW95cylstBg4YYk+ZQpwbAQvOjhtfIaZ4/dFOFpWUgE0wQvA5q0TFp 7d8Vs9hXhYPcSbhPuQGNLK2OSx/f220+TKbEyNNcIO3iClNBndCva7PXlWfyu0WZ4vDL RG1pSwltII/dJJXPCeR38xGJVGXxZ6zQgfNqk00vcnQj2JOqZBt9LxHmIRvJl7etvu8o sbsySGJcIw5/SEi2aauZxOEVAsPTOQ7LnEZRbKx2mmfwBayX52Y0vnKt+1oACLeCI9Cb FLipNYFleRUngXEU16JO4leU0KPrryRRvst+VXgW5EfwMuFiAPqhhEFmHUm9aPsvUFCQ Ikpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=C+83WGng3oBk6ZNDUqMMAEBvlGTAcHjYn21BKp1mShQ=; b=K3cfOCyaJ9CB0uIpzNSYcacto1M3H9Nnqtvvnm6lpDPWc9J4NTPvO/sAYfX6q1858k eNChReo7VM2/RRM+plyaM2n0t2l6E/S3lucn/uKE4EcDtdU3Tzf4Gf5EW2lxQY1U1ozo 1tbyn40QzUg4uagauFVFaQqzSujRhif1y7xoIYA03EGCAFSQ+z6yC3vaUY85JSR4if0I 1fFvht4pQx9J5qUmSvTIJVTo5WnASD0vguy3DhZarR00MCO/hKwgFR/Ljz0eoU8bPlix jq1D9Fjyr7ik8LhZISIkqcr70LByeFUR1DYtgtrX/XLYpCfuAxst1bS2I+dGt3NAHVYg ieLg==
X-Gm-Message-State: APjAAAU89r4vLUTZrv4FNlBJBIHfBfgGg0AAMbbb9OGd9ph9ol9QK5Wl fy2Uj/qG35eCpE7sP1a7RzQDnUEh20g3szzIOySx0sfx
X-Google-Smtp-Source: APXvYqz3H46BDugvll0HUGDMH4Aw8W8aDfUscyH8iqLAh52ppdFc0RWhl3OnIzeIeTN2BUOOx1CT1cJUvU+Sj06eK3s=
X-Received: by 2002:a05:6512:1c3:: with SMTP id f3mr4161137lfp.25.1574174426051; Tue, 19 Nov 2019 06:40:26 -0800 (PST)
MIME-Version: 1.0
References: <DDA7EA96-5B03-4F03-83DE-AFEC82A74DA7@apple.com> <CAKC-DJhX6gZh2pRqfc8n-NanZ1ESjCemyOifsBD22LJ6aTiPxw@mail.gmail.com>
In-Reply-To: <CAKC-DJhX6gZh2pRqfc8n-NanZ1ESjCemyOifsBD22LJ6aTiPxw@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
Date: Tue, 19 Nov 2019 09:40:14 -0500
Message-ID: <CA+nkc8AgnMcnWfWsrPY2xb8mZg9fJHkjCdakU-a+zrLJq1r34A@mail.gmail.com>
To: Erik Nygren <erik+ietf@nygren.org>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007ad2d00597b40bbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Z5lkjO2a9LhpzBBlKunkgxgHW9k>
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 14:40:32 -0000

On Tue, Nov 19, 2019 at 8:32 AM Erik Nygren <erik+ietf@nygren.org> wrote:

> Some of my current leanings:
>
> SVCB and HTTPB  (SVCB and HTTPSB)
>
> Of even shorter:  "SB" and "HSB"
>
> (I also prefer SVCHTTPS over HTTPSSVC as the latter is way too easy to
> leave out one of the S's.)
>
> I'd considered just calling "SVCB" as "B" but that makes it harder to
> search for.
> This is also why "HTTP" or "HTTPS" are dispreferred is that they are hard
> to search for.
>
> HTTP(S) is more than just the Web which is why I'd be disinclined to use
> WEB in the name.
>
>   Erik
>
>
> On Tue, Nov 19, 2019 at 5:39 AM Tommy Pauly <tpauly=
> 40apple.com@dmarc.ietf.org> wrote:
>
>> Hello DNSOP,
>>
>> In the interest of getting this spec ready to go, I want to start our
>> bikeshed on the RRTYPE name. We need a stable name that we all can live
>> with.
>>
>> I'll start. Please chime in!
>>
>> Since it seems that many people like SVCB, and many don't like HTTPSSVC
>> (too many repeated SS's!), I suggest using:
>>
>> SVCB (referred to as "Service Binding")
>>
>> SVCB-HTTPS (referred to as"Service Binding for HTTPS")
>>
>>
>> Best,
>> Tommy
>>
>
Perhaps:

SVCB and SVCH ?

-- 
Bob Harold