Received: from mail-ej2-x10.google.com (mail-ej2-x10.google.com [IPv6:2a00:1450:4864:34::10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 68EA73F for ; Thu, 17 Sep 2026 11:51:14 +0000 (UTC) Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=mQNBGNMT; arc=pass ("google.com:s=arc-20260327:i=1"); dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx.ietf.org: domain of ted.ietf@gmail.com designates 2a00:1450:4864:34::10 as permitted sender) smtp.mailfrom=ted.ietf@gmail.com Received: by mail-ej2-x10.google.com with SMTP id a640c23a62f3a-c254f6c7a4aso102973866b.0 for ; Thu, 17 Sep 2026 04:51:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1789645873; cv=none; d=google.com; s=arc-20260327; b=TcIYsMQy2O+FCjpgQ5fQZNIjTg99B3mfw8wEm/J8NAW53p3MOfzLfSXp+YPManNYlo bUTo22ekJabmJizrtEK+7lspwlgEI/BjBFvMMy5rv4N+QmLRkjWSesrUM++yL3ewONg5 DY6RH9WS5lxENOoqZg6Q8x/XllXGvVqlP8Y6v9+uv0msYNcIqwTGdkD5V630JWy5fSbV RoCfHkvj2hRVy+lgbfIK/7ja6Zm0kO8MmHpc2AvDA7tBOOmaLy17MIGF4C3LStYGGn/A 7rEHdoMA4iPorFY/m9JlpJkp1+FrZjPF0KCkw+/ZxuE7t31Ngk91QhVNW87/QsciQqSp tvXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=NcfInq05xuyWoFHrl2gsx4xuKCHyl58UEDKQtKqRXsw=; fh=MxOevYy6GH87xUnQt+1ngDilkHfK1lidkAvcxOvtNj4=; b=eTeX2WaC1kgelYGvhXCWY7aVEbMBEhhozUDbSE7kAo303vabgXo5UYwHNNziskvmql Ki46KeAMaui6pWLrk7sw5FmVEq5Vfvw0yBsFA16dx9JMT27eT64E2oMs42o+kgtKvzbp EHC7rTvzoT3q8bzOqj8oAunPlyIAF025g4dz2PLbX5TT+xaMh9PvoTp2mhzduWTndA59 QeaLzYKwuksVdIEWq28XrpTqzKaPtaQktTJCmeEWIXcGIWTM8oRQ5b7cK/vTvbDoWJdd 6Fh+YyaIF5BT8jIuBggunuaSGtKXuXAIkul3SUBkdNxxXB+aVPfRoX/xRCeDVqwKzWGe pfzA==; darn=ietf.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1789645873; x=1790250673; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=NcfInq05xuyWoFHrl2gsx4xuKCHyl58UEDKQtKqRXsw=; b=mQNBGNMTELKbVMRQYpqkpYr34R1Oa6vegGM138S/lcaE7GUYHK3e0IyVN1+oTFSj+8 kC2S0SzmUdHrt5LhjaGviwGwTXnjqOc7UvnM0EdlYFZrlWVl1riImeWwiFTbCmmIw19x OiYcdHJCENgR3czBOndDNfCsR6dKrtslcaZXHi5bZadcrl1nTKwk0z6aGCYw0pdQYGDZ o0y1UgQ2SdvUNo3rcVV7zRlIOv0wOlKq1FQMX+KULzSPueSFoQU6LtV/PGJZpatlehMw ddEUVGQgeML/auNlkFUrEOgDKQCO2y5HRcNm3iJd54XQJeDej93GGnr3ElpCL8SvuL5A 5xcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1789645873; x=1790250673; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=NcfInq05xuyWoFHrl2gsx4xuKCHyl58UEDKQtKqRXsw=; b=iqNQ0EJsGpHgStqYIPbd8lGUUq4EQ/S6HNkZC/MncZBvq2uBnClkEVQ9hvpX7yEALZ wwtaMX2ov6k9fXd2Mtf/qRlsXQTONj4qZi70/kfUf08tiz0tmLtbEUUoR777fnVno8cc Cbnh9cta4NcWDimShFY0UR+GblfyLsuciaIMfRwoTJ2a7IvlYJYc6jdwIlAlErb8MUNa mKegsDX3t3y6JOtwSrjjSLWLgqcHZDKvJeN/gbkE1UHklIKEKxCr7HeF+rkko8d/RTye wTaiGMINV3GcQhxnSiReaVDKcW4oSwzXQaT0GDjWEierqdDfsR7rThTnvCvMYCgS/5gZ vhGA== X-Forwarded-Encrypted: i=1; AKwUvBx4jSHQMfabMCzYL4DD5cC0A/A6vH/Gn61f2ln/GfNxxiP1nM3oL5kep8aa6WCi0cenyAk=@ietf.org X-Gm-Message-State: AFuF++nNK08seD0fGvIwcyzjHxhSwE0AIMKA9LMV1LbxhM2HqAWsp6y1 dPMSW+UPOy41mBowpVcrgdHGhF2YiZHcYUpFWEe+lirgVEl0xLpNHhg5CmDRHygdFMFkHjDKfuo KnnpFjEKRDUX5RUzOl8QxvzS/z6C5rJs= X-Gm-Gg: AYBFou31z/JJ8F+047nGImBTm/C0M1hUJp3kmiiTJKZGzNa4b/YjlE4oSxlqvZ5mFj/ kM6Q0LgYaRMCXcw25/s/isM+OWbAgFSmdYSfnGkOsErdG8czrkOv2U8e5M+1Rc276Or1xGp/IrD hx983ZLueN6jFhnyQNPB1DWtBPNuye+5ZZhkURs1s402AcFSQ+qaB4qgrc+wRQmE4Jglg6d6ZJJ BKizMJDc7vsB78IoZgmpOVnoE3xoiZBMpK0Dg2Gbw0ebANypcIO5sjFbRq12IskVucetP/MQrk6 PqT/yS1LOMO8aH2c0W8XHAc8PvkDQDm6nJ5+TtiaWzloQgaS8EGWaG0W/b8y6B9iBj7NIVtNqIp jSBk70fEqXHLzdpbEyvpn13+C5UmbZfaRj15krlR6fJO6ilopRHQnFsAsItb1kyJSuto1/uSYXx gn0FU7YbMkPzPivhi71M1ROsTz9Xdw+4Ekw2Ij2tm+s2z3KJioGyThewca9Ak957mk25rIiRHD+ OTFc8IEvKEjYZ9sbcxPXbJU6m5pV8UWaNOdeQ4BOEwnxoRonKVHpeakuOb0mXGH/Ufs1xbkvV6S RCT02JRqks9s4aRnMtSYpRQl X-Received: by 2002:a17:907:d64a:b0:c1f:1520:4de5 with SMTP id a640c23a62f3a-c29e51dc0ebmr435703266b.1.1789645872990; Thu, 17 Sep 2026 04:51:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ted Hardie Date: Thu, 17 Sep 2026 12:50:46 +0100 X-Gm-Features: AcwNN1Xr4SOPknN-v_me0VxPEnlVb08C0nhXclWRMrfNm8LxX5wTN2SHH9YPuKM Message-ID: To: Q Misell Content-Type: multipart/alternative; boundary="000000000000889035065bac6680" X-Spamd-Bar: -- Message-ID-Hash: BTZHHJQX2V4ZW3DKUEKFCRAQ64SU6JKD X-Message-ID-Hash: BTZHHJQX2V4ZW3DKUEKFCRAQ64SU6JKD X-MailFrom: ted.ietf@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-urn.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Q Misell , urn@ietf.org X-Mailman-Version: 3.3.10 Precedence: list Subject: [urn] Re: URN Namespace Assignment List-Id: "Discussion about Uniform Resource Names (URNs)." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000889035065bac6680 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Q, I would suggest making the registration when the standards work on the syntax is functionally complete. That way the review can validate the syntax and proposed resolution methods prior to any large scale implementation or deployment. Given the request is coming from an SDO, I think it pretty likely that the namespace will eventually be approved, but it is important that the group validate the syntax and the other aspects of the registration. So I recommend registering prior to things being set in stone, but late enough that there is a clear proposal. best regards, Ted Hardie On Thu, Sep 17, 2026 at 9:57=E2=80=AFAM Q Misell w= rote: > Hi, > > We're still in the process of writing the standard; as such, it doesn't > really exist yet. Would it be better to progress on the assumption that > such a URN namespace could be registered when we're done, and resubmit wh= en > we have published the final standard? > > Mit freundlichen Gr=C3=BC=C3=9Fen, > Q Misell (sie/ihr - she/her) > > =F0=9F=8C=B2 Please consider the environment before using AI to process t= his email. > -- > Max-Planck Institut f=C3=BCr Informatik > Fon +49 681 9325 3547 <+49%20681%2093253547> > Forschungsgruppe Internet Architecture (INET) > Campus E1.4 514, 66123 Saarbr=C3=BCcken > > Am 17.09.2026 um 10:04 schrieb Ted Hardie : > > Hi Q, > > Are you requesting registration under the procedures documented in Sectio= n > 6.3 or RFC 8141, given that this is for CEN-CENELEC? If so, please update > this to point to the document where the NID will be defined. > > As it stands, this registration does not define the syntax to be used, an= d > it can't really progress without that. > > regards, > > Ted Hardie > > On Thu, Sep 17, 2026 at 8:11=E2=80=AFAM Q Misell 40mpi-inf.mpg.de@dmarc.ietf.org> wrote: > >> Hello, >> >> I'm involved in the Barcoded Ticketing for Public Transport ( >> https://bt4pt.eu) project at CEN-CENELEC, and would like to request the >> preliminary registration of a URN namespace for our purpose in the >> standard. Please see below the registration template. >> >> Namespace Identifier: bt4pt >> >> Version: 1 >> >> Date: 2026-09-17 >> >> Registrant: CEN-CENELEC info@cencenelec.eu >> >> Purpose: >> URNs under this namespace will be assigned to entities such as transport >> organisations, stops, routes, lines, etc. They will be used for >> interoperability across public transport in Europe, processed by ticket >> issuing machines and ticket validation devices. The Open Sales and >> Distribution Model (https://osdm.io) already makes use of URNs in its >> APIs under the urn:uic: namespace, thus a URN for BT4PT purposes will >> compliment the UIC's namespace and allow interoperability. >> >> Syntax: >> The exact syntax is as yet undefined, and will be written as part of the >> in-progress CEN-CENELEC standard. >> >> Assignment: >> Assignment will be managed by the CEN-CENELEC, in the process of >> publishing standards documents defining sub-ranges of this URN namespace= . A >> sub-range may, in turn, be delegated to some other registration authorit= y, >> or reference a code-list maintained by another authority, such as the >> European Union Agency for Railways. >> >> Security and Privacy: >> All identifiers will be assigned for publicly available information only= , >> there will be no possibility for leakage of private information nor any >> danger for directory harvesting. >> >> Interoperability: >> There are no foreseen interoperability issues. >> >> Resolution: >> A resolution service does not yet exist, but will be defined as part of >> the in-progress CEN-CENELEC standard. >> >> Documentation: >> Use of this namespace will be documented as part of the in-progress >> CEN-CENELEC standard. >> >> Mit freundlichen Gr=C3=BC=C3=9Fen, >> Q Misell (sie/ihr - she/her) >> >> =F0=9F=8C=B2 Please consider the environment before using AI to process = this email. >> -- >> Max-Planck Institut f=C3=BCr Informatik >> Fon +49 681 9325 3547 <+49%20681%2093253547> >> Forschungsgruppe Internet Architecture (INET) >> Campus E1.4 514, 66123 Saarbr=C3=BCcken >> >> _______________________________________________ >> urn mailing list -- urn@ietf.org >> To unsubscribe send an email to urn-leave@ietf.org >> > > --000000000000889035065bac6680 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi = Q,

I would suggest making the registration when the standards work on = the syntax is functionally complete.=C2=A0 That way the review can validate= the syntax and proposed resolution methods prior to any large scale implem= entation or deployment.=C2=A0 Given the request is coming from an SDO, I th= ink it pretty likely that the namespace will eventually be approved, but it= is important that the group validate the syntax and the other aspects of t= he registration.=C2=A0 So I recommend registering prior to things being set= in stone, but late enough=C2=A0 that there is a clear proposal.=C2=A0

best regards,

Ted Hardie


On Thu, Sep 17, 2026 at 9:57=E2=80=AFAM Q Misell <qmisell@mpi-inf.mpg.de> wrote:
=
Hi,

We're still in the process of writing the standard; as such, it does= n't really exist yet. Would it be better to progress on the assumption = that such a URN namespace could be registered when we're done, and resu= bmit when we have published the final standard?

Mit freundlichen Gr=C3=BC=C3=9Fen,
Q Misell (sie/ihr - she/her)

=F0=9F=8C=B2=C2=A0Please consider the environment before using AI to process this email.=
--
Max-Planck Institut f=C3=BCr=C2=A0Informatik
Fon <= a href=3D"tel:+49%20681%2093253547" value=3D"+4968193253547" target=3D"_bla= nk">+49 681 9325 3547
Forschungsgruppe Internet Architecture = (INET)
Campus E1.4 514, 66123 Saarbr=C3=BCcken
<= /div>

Am 17.09.2026 um 10:04 schrieb Ted = Hardie <ted.ietf= @gmail.com>:

Hi Q,

Are you requesting registration under the proc= edures documented in Section 6.3 or RFC 8141, given that this is for CEN-CE= NELEC? If so, please update this to point to the document where the NID wil= l be defined.
<= br>
As it stand= s, this registration does not define the syntax to be used, and it can'= t really progress without that.

regards,

Ted Hardi= e

On Thu, Sep 17, 2026 at 8:11=E2=80=AFAM Q Misell <qmisell=3D40mpi-inf.m= pg.de@dmarc.ietf.org> wrote:
Hello,

I'm involved in the Barcoded Ticketing for Public= Transport (https://bt4pt.e= u) project at CEN-CENELEC, and would like to request the preliminary re= gistration of a URN namespace for our purpose in the standard. Please see b= elow the registration template.

Namespace Identi= fier: =C2=A0bt4pt

Version: =C2=A01

<= /div>
Date: =C2=A02026-09-17

Registrant: =C2= =A0CEN-CENELEC=C2=A0info@cencenelec.eu

Purpose:
URNs un= der this namespace will be assigned to entities such as transport organisat= ions, stops, routes, lines, etc. They will be used for interoperability acr= oss public transport in Europe, processed by ticket issuing machines and ti= cket validation devices. The Open Sales and Distribution Model (https://osdm.io) already makes use = of URNs in its APIs under the urn:uic: namespace, thus a URN for BT4PT purp= oses will compliment the UIC's namespace and allow interoperability.

Syntax:
The exact syntax is as yet undefin= ed, and will be written as part of the in-progress CEN-CENELEC standard.

Assignment:
Assignment will be managed by = the CEN-CENELEC, in the process of publishing standards documents defining = sub-ranges of this URN namespace. A sub-range may, in turn, be delegated to= some other registration authority, or reference a code-list maintained by = another authority, such as the European Union Agency for Railways.

Security and Privacy:
All identifiers will be as= signed for publicly available information only, there will be no possibilit= y for leakage of private information nor any danger for directory harvestin= g.

Interoperability:
There are no forese= en interoperability issues.

Resolution:
= A resolution service does not yet exist, but will be defined as part of the= in-progress CEN-CENELEC standard.

Documentation:= =C2=A0
Use of this name= space will be documented as part of the in-progress CEN-CENELEC standard.

Mit freundlichen Gr=C3=BC=C3=9Fen,
Q Misell (sie/ihr - she/her)=

=F0=9F=8C=B2=C2=A0Please consider the environment before using AI to process this email= .
--
Max-Planck Institut f=C3=BCr=C2=A0Info= rmatik
Forschungsgruppe = Internet Architecture (INET)
Campus E1.4 514, 66123 Saarbr=C3=BCc= ken

_______________________________________________
urn mailing list -- urn@i= etf.org
To unsubscribe send an email to urn-leave@ietf.org

--000000000000889035065bac6680--