Re: Gen-ART review of draft-bundesbank-eurosystem-namespace-02 Tue, 17 December 2013 14:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 53CC11AE182; Tue, 17 Dec 2013 06:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nmnrVnhZ5NxL; Tue, 17 Dec 2013 06:38:37 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 0C4BF1AE17A; Tue, 17 Dec 2013 06:38:36 -0800 (PST)
Received: from [] by id 96/28-02132-BE160B25; Tue, 17 Dec 2013 14:38:35 +0000
X-Originating-IP: []
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10180 invoked from network); 17 Dec 2013 14:38:34 -0000
Received: from unknown (HELO ( by with DHE-RSA-AES256-SHA encrypted SMTP; 17 Dec 2013 14:38:34 -0000
Received: from (lb-extranet-inc2 []) by (Merkur) with ESMTP id 8902EA4C1; Tue, 17 Dec 2013 15:38:34 +0100 (MET)
Subject: Re: Gen-ART review of draft-bundesbank-eurosystem-namespace-02
X-Priority: 3 (Normal)
Importance: Normal
X-KeepSent: 96C0304D:84369D1C-C1257C44:0048EA75; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3FP4 SHF39 May 13, 2013
Message-ID: <>
Date: Tue, 17 Dec 2013 15:38:33 +0100
X-MIMETrack: Serialize by Router on NT999SP23/SRV/BBK/DE(Release 8.5.2FP3|July 10, 2011) at 17.12.2013 15:38:34
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Dec 2013 14:38:40 -0000


thanks for the Gen-ART review [1] you have performed on our draft, and our
apologies for the delay in responding to it.

We have been surprised by your concerns regarding the application for a
Formal URN Namespace, which we'd have expected being raised by someone
during the two stages of URN-NID Expert Review the draft has undergone
since August 2013.  Apparently, the URN experts
active on the urn-nid list did not share your concerns.

The (prospective) 'eurosystem' URN Namespace is modeled after the very
similar 'swift' Formal URN namespace registered per RFC 3615, and there
have been allocated quite a couple of other Formal URN Namespaces to
national institutions and international treaty organizations, which seem to
have similar usage profiles; we are not aware of similar arguments having
been raised against the allocation of these Formal URN Namespaces.

'eurosystem' URNs will be used together with already standardized URNs, in
particular ISO Std 20022 URNs; it is important for their use that the role
of these URNs and the authority behind these URNs be easily and clearly
identified, and be at a perceived "equivalent" standards level -- parallel
to the 'swift' URNs that are managed by an older international treaty
organization with similar purpose but smaller scope and less consumer
friendly targets (regarding timeliness of transaction execution and cost
effectiveness). Therefore, an Informal URN Namespace would not meet the
target objectives of the supporting countries and financial institutions.

Admittedly, it is true that, at the first stage of usage of the
'eurosystem' namespace, the mass production use of the assigned URNs will
be contained in messages carried in cryptographic digital envelopes or
Vitual Private Networks.  However, the transparency requirements (needed
for establishing and maintaining public trust into the subject financial
transaction systems), open software development processes, and software
deployment require the origin and authority for the URNs to be easily
identified, and the URNs to be resolved on the public Internet.
Therefore we claim that a Formal URN Namespace is warranted for the
intended purpose.

We will confer with the sponsoring AD on possible amendments to the
Community Considerations in our draft. (Based on previous feedback, this
section has been kept relatively short and concise.)

Kind regards,


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.