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

Isaac Vetter <> Fri, 28 June 2019 15:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A305120455 for <>; Fri, 28 Jun 2019 08:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qyzQjC8lNrJV for <>; Fri, 28 Jun 2019 08:08:04 -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 6E0DD120440 for <>; Fri, 28 Jun 2019 08:08:04 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id x5SF7bPI020357; Fri, 28 Jun 2019 10:08:00 -0500
Received: from ( []) by with ESMTP id 2tdmu0r2mt-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 28 Jun 2019 10:08:00 -0500
Received: from (2620:72:0:8e27::5a) by (2620:72:0:8e27::4e) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 28 Jun 2019 10:07:58 -0500
Received: from ([fe80::68f4:7afe:de1f:62]) by ([fe80::68f4:7afe:de1f:62%4]) with mapi id 15.01.1779.002; Fri, 28 Jun 2019 10:07:58 -0500
From: Isaac Vetter <>
To: "" <>, "" <>
Subject: RE: Request for well-known URI: smart-configuration
Thread-Topic: Request for well-known URI: smart-configuration
Thread-Index: AdURhPkUEjdhyEw0QSa0FOP+b6FZhwcPXlvA
Date: Fri, 28 Jun 2019 15:07:58 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: [2620:72:0:8e27::16]
Content-Type: multipart/alternative; boundary="_000_21d6890833414b5786af46e17c0cd124epiccom_"
MIME-Version: 1.0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906280176
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: Fri, 28 Jun 2019 15:08:08 -0000

Hi iesg, wellknown-uri-reviewers,

I'm hoping to register the "smart-configuration" well-known URI name. Any updates?

Please let me know how I can help.


Isaac Vetter

> Registration requests that are undetermined for a period longer than 21 days can be brought to the IESG's attention (using the mailing list) for resolution.

From: Isaac Vetter
Sent: Thursday, May 23, 2019 11:48 AM
To: '' <>
Subject: Request for well-known URI: smart-configuration

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<>h/>. 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