[Uri-review] [IANA #1274073] RE: Registration request for "at" URI scheme
Sabrina Tanamal via RT <iana-issues@iana.org> Fri, 23 June 2023 23:28 UTC
Return-Path: <iana-shared@icann.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C575C151064 for <uri-review@ietfa.amsl.com>; Fri, 23 Jun 2023 16:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.647
X-Spam-Level:
X-Spam-Status: No, score=-6.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pn3SiBCtcUhV for <uri-review@ietfa.amsl.com>; Fri, 23 Jun 2023 16:28:04 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71998C151060 for <uri-review@ietf.org>; Fri, 23 Jun 2023 16:28:04 -0700 (PDT)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 56F59E17B6; Fri, 23 Jun 2023 23:28:04 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 40CF04B0F8; Fri, 23 Jun 2023 23:28:04 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <iana-issues@iana.org>
Reply-To: iana-issues@iana.org
In-Reply-To: <rt-5.0.3-64346-1687528128-988.1274073-37-0@icann.org>
References: <RT-Ticket-1274073@icann.org> <RT-Ticket-1274420@icann.org> <RT-Ticket-1273521@icann.org> <8b8310fe-20d1-f58e-79b6-b0ac6955e6c@robocracy.org> <rt-5.0.3-1170961-1685657461-1271.1273521-37-0@icann.org> <8ef414c0-5f18-781b-50c9-7872785ddad2@robocracy.org> <078629d6-394e-36cf-e3fb-6fc90c71c77e@ninebynine.org> <rt-5.0.3-1995293-1686071481-1760.1274420-3-0@icann.org> <c04b3a97-9d93-4193-199f-34a3240684cd@ninebynine.org> <rt-5.0.3-64346-1687528128-988.1274073-37-0@icann.org>
Message-ID: <rt-5.0.3-97087-1687562884-1920.1274073-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1274073
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
To: GK@ninebynine.org
CC: uri-review@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 23 Jun 2023 23:28:04 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/-AXIRSsH0zERZZMPb_m4NXLg8a8>
Subject: [Uri-review] [IANA #1274073] RE: Registration request for "at" URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jun 2023 23:28:08 -0000
Hi Graham, We've added the note below to the "at" entry's "Description" field: https://www.iana.org/assignments/uri-schemes Best regards, Sabrina Tanamal Lead IANA Services Specialist On Fri Jun 23 13:48:48 2023, GK@ninebynine.org wrote: > Hello IANA, > > In my role as URI scheme reviewer, I would like to request addition of > the > following reviewer note to the provisional registry entry for the "at" > URI > scheme. My proposal (modulo minor text changes) has been circulated > to the > URI-review list, and no objections were raised. > > (I anticipate this will follow the same administrative pattern as the > notes > created for, e.g., 'dhttp', 'swid', etc.) > > Thanks, > > #g > > > [[ > > ## IANA reviewer note (dated 2023-06-23) > > The 'at' URI scheme has been provisionally registered under the “first > come first > served” policy set out in RFC 7595. This means that the scheme has > not been > formally reviewed in the IETF, and is not recommended by the IETF for > general > use on the open Internet. > > There has been some discussion of this scheme on the IETF URI-review > list > [R1,R2], and there is a considerable degree of concern that the scheme > name 'at' > could be a cause of confusion, or conflict with other common uses of > the term > 'at'. For these reasons, it has been suggested that the name > 'atproto' or 'atp' > might be more suitable. This could turn out to be an impediment to a > subsequent > request for permanent registration of this scheme name. > > This note is intended to draw attention to potential problems that > might arise > if this scheme were to be used widely on the open Internet, and does > not of > itself constitute a position by the IETF or IANA on the considerations > raised. > > [R1]https://mailarchive.ietf.org/arch/msg/uri- > review/x3LbUP7_DOlEFCH84QvZdRU74Js/ > (refers to all messages in thread) > > [R2]https://mailarchive.ietf.org/arch/msg/uri-review/uGgzryN- > wG9PzrQU06bd4_zlW3s/ > (refers to all messages in thread) > > ]] > > > On 06/06/2023 18:11, IANA Protocol Parameter Requests via RT wrote: > > To whom it may concern: > > > > This is an automatically generated message to notify you that we have > > received your request, and it has been recorded in our ticketing > > system with a reference number of 1274420. To check the status > > of your request, please see: > > > > https://tools.iana.org/public-view > > > > If you have any problems accessing this page, please contact > > iana@iana.org. > > > > There is no need to reply to this message right now. IANA staff will > > review your message shortly. > > > > If this message is in reply to a previously submitted ticket, it is > > possible that the previous ticket has been marked as closed. As we > > review this ticket, we will also review previous correspondence and > > take appropriate action. > > > > To expedite processing, and ensure our staff can view the full > > history > > of this request, please make sure you include the follow exact text > > in > > the subject line of all future correspondence on this issue: > > > > [IANA #1274420] > > > > You can also simply reply to this message, as this tag is already in > > the subject line. > > > > Thank you, > > > > The Internet Assigned Numbers Authority > > iana-prot-param@iana.org > > > > ------------------------------------------------------------------------- > > Hi, > > > > As IANA reviewer, I propose to request addition of the following note > > to this > > registration. > > > > I'm posting here for information and comment before I make a formal > > request to IANA. > > > > #g > > > > > > [[ > > > > ## IANA reviewer note > > > > This scheme has been provisionally registered under the “first come > > first > > served” policy set out in RFC 7595. This means that the scheme has > > not been > > formally reviewed in the IETF, and is not recommended by the IETF for > > general > > use on the open Internet. > > > > There has been some discussion of this scheme on the IETF URI-review > > list > > [R1,R2], and there is a considerable degree of concern that the > > scheme name 'at' > > could be a cause of confusion, or conflict with other common uses of > > the term > > 'at'. For these reasons, it has been suggested that the name > > 'atproto' or 'atp' > > might be more suitable. This could turn out to be an impediment to a > > subsequent > > request for permanent registration of this scheme name. > > > > This note is intended to draw attention to potential problems that > > might arise > > if this scheme were to be used widely on the open Internet, and does > > not of > > itself constitute a position by the IETF or IANA on the > > considerations raised. > > > > [R1] https://mailarchive.ietf.org/arch/msg/uri- > > review/x3LbUP7_DOlEFCH84QvZdRU74Js/ > > (refers to all messages in thread) > > > > [R2] https://mailarchive.ietf.org/arch/msg/uri-review/uGgzryN- > > wG9PzrQU06bd4_zlW3s/ > > (refers to all messages in thread) > > > > ]] > > > > > > > > On 01/06/2023 23:59, bnewbold@robocracy.org wrote: > >> Hi Dave, > >> > >> What do you think of an addition like: > >> > >> --- > >> > >> Disambiguation Note > >> This URI scheme has no association with the 'at' command line > >> utility for > >> scheduling program execution. > >> > >> --- > >> > >> --bryan > >> > >> On Thu, 1 Jun 2023, Dave Thaler wrote: > >> > >>> In my opinion it would be helpful to include a Note since this > >>> registration > >>> doesn't follow the "SHOULD" (which is ok since its not a MUST) in > >>> RFC 7595: > >>> " Schemes SHOULD NOT use names that are either very general > >>> purpose or > >>> associated in the community with some other application or > >>> protocol." > >>> > >>> since "at", is a well known (e.g., see > >>> https://linux.die.net/man/1/atapplication, > >>> https://learn.microsoft.com/en-us/windows- > >>> server/administration/windows-commands/at, > >>> etc.) application for scheduling job execution. > >>> > >>> It would be helpful to acknowledge this to avoid confusion. > >>> > >>> Dave > >> _______________________________________________ > >> Uri-review mailing list > >> Uri-review@ietf.org > >> https://www.ietf.org/mailman/listinfo/uri-review
- [Uri-review] [IANA #1273521] Registration request… Sabrina Tanamal via RT
- Re: [Uri-review] [IANA #1273521] Registration req… Dave Thaler
- Re: [Uri-review] [IANA #1273521] Registration req… bnewbold
- Re: [Uri-review] [IANA #1273521] Registration req… Graham Klyne
- [Uri-review] [IANA #1274073] RE: Registration req… Sabrina Tanamal via RT