Re: nearing completion for HTTPS RR type (and SVCB RR type)

Martin Thomson <> Thu, 25 June 2020 03:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 748FB3A1253 for <>; Wed, 24 Jun 2020 20:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.749
X-Spam-Status: No, score=-7.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=T2iykB3l; dkim=pass (2048-bit key) header.b=uwfWdpIb
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hDAwtbeZ6Jt8 for <>; Wed, 24 Jun 2020 20:28:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 357153A1252 for <>; Wed, 24 Jun 2020 20:28:20 -0700 (PDT)
Received: from lists by with local (Exim 4.92) (envelope-from <>) id 1joIWA-0005a2-FD for; Thu, 25 Jun 2020 03:25:38 +0000
Resent-Date: Thu, 25 Jun 2020 03:25:38 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1joIW9-0005Yz-2v for; Thu, 25 Jun 2020 03:25:37 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1joIW7-0004An-AT for; Thu, 25 Jun 2020 03:25:36 +0000
Received: from compute2.internal (compute2.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id 8A99BAEB for <>; Wed, 24 Jun 2020 23:25:22 -0400 (EDT)
Received: from imap2 ([]) by compute2.internal (MEProxy); Wed, 24 Jun 2020 23:25:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=7ebFjd8xcw4wNtxOmgfpeqMaRQhTlSS 9GxPN7frivW4=; b=T2iykB3lxC/7eLs5mtE4hKbaBXyCIXQei18anGkq/puIn56 HIYiQtVxGD4xN1nyhHRH2jvOXFdHwIA1tmySFA969EehYmL0uY2dxeBlnSR55JcE sNhCh7k0Q2g/R2ZhQ6TzeNUeUXTJ7PNVHn+O3fEOYI6xva10IZYe9+m9ZMODEs5I 1FApQT2qUUnrG0GOe7MvpG4Wp2bGRFFPdr1UTJVpYf3tU8ZnOkV2xmQqzoPKaBV7 h+4dXLoVXJ9VEjfob2pgpyUdSNmAJfLLipN9jfxMlqrtOz7ucWtdEZg+/UHak+ek R/EUvHZ2ooLbSstzdCqK/e9QGLCX5NQT3mWRigg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=7ebFjd 8xcw4wNtxOmgfpeqMaRQhTlSS9GxPN7frivW4=; b=uwfWdpIb8SZtdhH5AHPF/D 8fy/AuBc/IXhPeqCUylDGi+Vj7T/sRK0q6yUcQqgui1VpWsnXdznvvroFcPxJvAf Y4WI8KRd8tBLvzxJPx6oXQvVuvrHBDH+qc7Juh9fpJfCCPulMFwx7pa402MY2NWv eJ3Re2x1R7+1mxdvi2m2FbxnlBpQ7iztho8IV6kXhTnk8L3qIM7kvtxBACOL0aG4 UUQhniGQs6TiQbK5romBTgZ2VYzrzb/7G85YE+vcU8N1+XH4TI4yfeC+coqSkZCY ut0Vr1MSLgm9DuVib+J9aymfZ4GoLNAx1VDh4BT7VRT75lcLmtKhRZAwXotMJRTQ ==
X-ME-Sender: <xms:IRn0Xgww9ulUvDnJmDSVChCq3DdDojeQLkWj2uP7nidDRsz5DZtc6A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudekkedgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeekteeuieektdekleefke evhfekffevvdevgfekgfeluefgvdejjeegffeigedtjeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvg ht
X-ME-Proxy: <xmx:IRn0XkRZA8gnSTeCTuV5NcgJcq60kZPuwOGn9qkfXO38iqnD34SWqA> <xmx:IRn0XiVysGWyQp_CPcKVGNTN702F2XrSDruridxQypmc-SfVjgXIng> <xmx:IRn0XuhDrWdgSG1CAcMJ6fYoodCTl5dUaBDku3ziDsmu1K9bm6TIIg> <xmx:Ihn0XixFwb3Z2-U010Q3jGm9tjOdHi1HEvfx0HdkrvlbkKrlJ1nctg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DC8FCE00A8; Wed, 24 Jun 2020 23:25:21 -0400 (EDT)
X-Mailer: Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-543-gda70334-fm-20200618.004-gda703345
Mime-Version: 1.0
Message-Id: <>
In-Reply-To: <>
References: <> <> <> <>
Date: Thu, 25 Jun 2020 13:25:01 +1000
From: "Martin Thomson" <>
Content-Type: text/plain
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: 1joIW7-0004An-AT 143c9bb51a560f362ff4968a4dccd0c8
Subject: Re: nearing completion for HTTPS RR type (and SVCB RR type)
Archived-At: <>
X-Mailing-List: <> archive/latest/37826
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

On Thu, Jun 25, 2020, at 12:20, Ben Schwartz wrote:
> SVCB is designed for use with URIs, so a scheme is required. (Section 
> 10, "The scheme SHOULD have an entry in the IANA URI Schemes 
> Registry".) URIs that concern a domain name presumably have an 
> "authority" in their URI that contains a "host", and might contain a 
> "port".

I think that you have (correctly) scoped this to services that are identified by a URI that also has an authority containing a domain name.  However, the port part is not central.  What is central is that these are services and not origins.

The core definition of SVCB does not depend on the classic web origin concept.  This is largely because inclusion of a port number is not central to the definition.  Though it does establish a pattern for extending the attr-label with _port, that is a per-scheme choice.