Re: Request for well-known URI: smart-configuration

Mark Nottingham <> Sun, 30 June 2019 23:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3F0E01201CD for <>; Sun, 30 Jun 2019 16:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=OPAHsJor; dkim=pass (2048-bit key) header.b=1YLMRbWm
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UHKl976NLjfY for <>; Sun, 30 Jun 2019 16:12:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E5D4F1201D3 for <>; Sun, 30 Jun 2019 16:12:54 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 0B18921448; Sun, 30 Jun 2019 19:12:53 -0400 (EDT)
Received: from mailfrontend2 ([]) by compute3.internal (MEProxy); Sun, 30 Jun 2019 19:12:53 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=d ZqMFtpioaFcj/2hzQhhvl+JhCX6/n6JElT0d5fd7+U=; b=OPAHsJorMhUk59Z2J xxE4LmvWaE9vnsrk4E8kGyc3uJt4jOOjdZ8rbMygNBxk6gvRaOuBoIt7EgBCk+My qKHeyc+spSBY8Jxm18zBEMj3XM0KFXKPyekk6sXoFjLs9sfszI0GbPnN0ZPcGoKJ hg7QzYx6JeXEakE5kuP7y5C9L0Bm2et0Ih58Eifk80M8opRnJBXlmbtoxiqhN5T+ VyvqokH3TUPwTUwFn+3lRCWV01OPpCN7T6xywGMGDillxZFrmY+57WEN+P2zfzB3 LLh0P/EzrY7Vdg8lB193Qrun7+DK7BLSaOC/ccMxd6jJ06KcRZ4IDLUyAjUswktm ERqmw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding: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=dZqMFtpioaFcj/2hzQhhvl+JhCX6/n6JElT0d5fd7 +U=; b=1YLMRbWmFKyhsI1furfD1nHkag1NAwEHRRL9uEQ2SFsIVAOJ/eN2gUecB pPjQOcaRr42UUwODs66xRpa0rOWbqbLWmmBBz06nr6uM8ZFn6oQiNveBxumroHTc /8m9DNTP3HF22v5fZAfW2pgruhIqOr2hqiQDPRwVpUc3LWDiacPi58ygrFrullLd jIHgWWwSd9sC49rpAbfKT7e/VG7G94FkKE9gExTI8Wlath4QlUMkYqpIXXmHnIKZ CdqAOm0oU//WWj2WtO8TMLApYSTuWdLaBytwHRd3LxWAe+ZiKJt4t666qdxzAazM LYm4fka07IEgDGFd1vvOTsLUT9UQg==
X-ME-Sender: <xms:80EZXZCzypoQ9iS6QZOqRMOUHIM3u_UlVmoqDWWFrdPm3K4Vw7H73A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrvdehgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hhlhejrdhorhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtnecukfhppedugeegrddu feeirddujeehrddvkeenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhoth drnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:80EZXe_LMyDicPcYwBGWf60Tfbx1UJiNUsLVkOhaTnJqLAu1wcX_lg> <xmx:80EZXR-XGLamozyUf976EjGT8hZTn1aTihCnlm3sOVW3kZ23UJcOBA> <xmx:80EZXde1nLt38XewMzgCZwfSjycvwQtmhuQgPK7YmG42dsW2W5uzbA> <xmx:9EEZXZmMby3LcHSeotpPrZD3PUrBg685zHWd3psDui2AEL_4mTVpzw>
Received: from (unknown []) by (Postfix) with ESMTPA id B5DB8380079; Sun, 30 Jun 2019 19:12:49 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Request for well-known URI: smart-configuration
From: Mark Nottingham <>
In-Reply-To: <>
Date: Mon, 1 Jul 2019 09:12:44 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Isaac Vetter <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 30 Jun 2019 23:12:58 -0000

Apologies for the delay.

Your document says:
  """Contrary to RFC5785 Appendix B.4, the .well-known path component may be appended even if the FHIR endpoint already contains a path component."""

RFC5785 Appendix B and RFC8615 (which obsoletes it) explain that this is bad practice, and not sanctioned use of well-known URIs. See RFC7320 (BCP190) for more information.

As a result, the registration request is denied. If that text is removed from the document, we can reconsider your request.

Additionally, the name "smart-configuration" is very generic; as per 8615, if a well-known resource is specific to an application, it should have a correspondingly specific name (e.g., "hl7-smart-configuration").


> On 24 May 2019, at 2:48 am, Isaac Vetter <> wrote:
> Hi wellknown-uri-reviewers!
> I’d like to request that the “smart-configuration” well-known URI name be registered. I’m making this request on behalf of the HL7 standards development organization in regards to the HL7 FHIR SMART App Launch specification. This implementation guide defines a well-known URI by which an application may discover a FHIR API server’s authorization and launch capabilities.  
> This specification has already gone through a round of balloting within HL7 and is currently published at the “Standard for Trial Use” level, which precedes a status of Normative. It would be nice if we could keep this name, and we probably should’ve registered it earlier.
> URI suffix: smart-configuration
> Change controller: I think that the correct answer is HL7 -
> Specification document:
> Isaac Vetter
> _______________________________________________
> wellknown-uri-review mailing list

Mark Nottingham