[urn] Re: Request for Registration of the IATA URN Namespace (RFC 8141 Fast-Track Procedure)
worley@ariadne.com Fri, 07 August 2026 18:14 UTC
Return-Path: <dale.worley@comcast.net>
X-Original-To: urn@mail2.ietf.org
Delivered-To: urn@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C3C8812583667 for <urn@mail2.ietf.org>; Fri, 7 Aug 2026 11:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786126489; bh=mMbGzMA9xKSEV/IflZpmzQ3DS8lHqoJgC6TzbJ4s9kk=; h=From:To:Cc:Subject:In-Reply-To:Date; b=W/3pABnAe9PTeK3rU7oVIpFQjKfZ6aWjNCS2O6j/0C6TpjHfVzROXTASB770cKNFV 4excqmTT8nGOX9JAAuLN5J2VVtQNxJc3a5ST+qMDXnkIx8vq87iV/+pVdIn0EoAp3t zwlV5rG7vCZPmyeCWwIysE8luuKBPoqTQSDNAwHo=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.897
X-Spam-Level:
X-Spam-Status: No, score=-0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RAND_HEADER_MANY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMKCVZPxhYlL for <urn@mail2.ietf.org>; Fri, 7 Aug 2026 11:14:49 -0700 (PDT)
Received: from resqmta-h2p-567353.sys.comcast.net (resqmta-h2p-567353.sys.comcast.net [IPv6:2001:558:fd02:2446::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 10F5B12583660 for <urn@ietf.org>; Fri, 7 Aug 2026 11:14:48 -0700 (PDT)
Received: from resomta-h2p-555029.sys.comcast.net ([96.102.179.203]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h2p-567353.sys.comcast.net with ESMTPS id sLgRwBSmvUUcgsP5ewr0CM; Fri, 07 Aug 2026 18:14:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1786126482; bh=ZNnEscGzL4eaH2m/541UEu184bCThzzhse294m/76k8=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=c/LH/nhHhot4DGAkHCvrGyh2UetzhAs0+6HaoSfebN3VHle43gE/Jljb49ug/qCxs LjLNRuIsmTqZesI55HVqYuMBsjWqsgn4AoezVClNalPFxnBjZarDDHd8ztbSl04It/ w8L0bZKDlDYleq25dbu0ClNbgW1yAV1allL6+OcpBKEeUKD3AYXve/Owl1/AYeO5aP Vrq8TbL9YBqDVxfc6/IZ374qRq3mHekM8mrWVr4j5b+6qVs4/q61eXfTZQqegJXfh5 4aK5MpnPw+9G/VMnegqU+K5iqr/zNb1Z8NN6/018ShdyrwFhtyEo7skBdcwWAwwf51 Z5QIJlAYRSpFA==
Received: from hobgoblin.ariadne.com ([76.118.106.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-h2p-555029.sys.comcast.net with ESMTPSA id sP5bwKYaEDEa6sP5cwtpNT; Fri, 07 Aug 2026 18:14:41 +0000
Xfinity-QID: sP5bwKYaEDEa6sP5ewtpNn
Xfinity-Graffiti: 40600510206
Xfinity-Graffiti: 79903820500
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 677IEb86437083 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Fri, 7 Aug 2026 14:14:37 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 677IEboj437080; Fri, 7 Aug 2026 14:14:37 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to Dale.Worley@comcast.net using -f
From: worley@ariadne.com
To: Yan Sun <suny=40iata.org@dmarc.ietf.org>
In-Reply-To: <PAXPR05MB961429F625AAB60456FEFCEAA2D52@PAXPR05MB9614.eurprd05.prod.outlook.com> (suny=40iata.org@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Fri, 07 Aug 2026 14:14:37 -0400
Message-ID: <87v79l94s2.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfH75w/yT/sJ6+vGIElDIsZRk6slGK+j3r6mWfXUXFRI03IkQxsEc9V+mDk7W07nGNT9AmvgxqShn5AetnnFH1nxOAK1MYNXtZqciaAq5WnFfkXgct4VF xhFhsmRXn8VyICdAG34wK8Y7YBf41yubKFz647YH2OIRvE9VgScSPEH8MjCM7fjIJXAuvABiEPdyHNc1iHXX40FRkG5fg7BkRVOQYZtRAGSzo3/tcq7DndVp IKGsdZU/9hrN9IemxRdCpg==
Message-ID-Hash: GJ7VDOO2FESMNEBPLCVBXDBQIK23IXBT
X-Message-ID-Hash: GJ7VDOO2FESMNEBPLCVBXDBQIK23IXBT
X-MailFrom: dale.worley@comcast.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-urn.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: urn@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [urn] Re: Request for Registration of the IATA URN Namespace (RFC 8141 Fast-Track Procedure)
List-Id: "Discussion about Uniform Resource Names (URNs)." <urn.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/w5AEKrnl4iIWQqjllYS6lYXH4HM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Owner: <mailto:urn-owner@ietf.org>
List-Post: <mailto:urn@ietf.org>
List-Subscribe: <mailto:urn-join@ietf.org>
List-Unsubscribe: <mailto:urn-leave@ietf.org>
> URN Namespace Registration for the International Air Transport Association (IATA).pdf (217kB)]
The syntax of the NSS is given as just
iata-nss = {resource-type}:{resource-specific-string}
I think technically this may suffice, but it would help if more details
was given. The most interesting point is that it's very desirable to
specify that resource-type can't contain ":", as otherwise it isn't
always possile to extract the resource-specific-string without
possessing a complete list of resource-types.
And in many cases, registrants can determine that their NSSs will not
utilize the full range of characters allowed in NSSs. In particular,
many registrations eschew the use of percent-encoded characters.
In regard to documentation, the registration says "The authoritative
documentation for the iata namespace is maintained and published by
IATA." At this early stage, it may not be possible to provide more
detailed information, as how the documentation will be published may not
have been determined. But it is useful if some sort of indication of
how to discover the documentation is provided.
Dale