Skip to main content

A Uniform Resource Name (URN) Namespace for Eurosystem Messaging

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 7207.
Authors Gunnar Dickfeld , Miriam Ortseifen
Last updated 2015-10-14 (Latest revision 2014-02-18)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Stream WG state (None)
Document shepherd Barry Leiba
Shepherd write-up Show Last changed 2013-11-08
IESG IESG state Became RFC 7207 (Informational)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Barry Leiba
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
IETF                                                        M. Ortseifen
Internet-Draft                                               G. Dickfeld
Intended status: Informational                       Deutsche Bundesbank
Expires: August 21, 2014                               February 17, 2014

    A Uniform Resource Name (URN) Namespace for Eurosystem Messaging


   This document defines and registers with IANA a Uniform Resource Name
   (URN) namespace that is managed by Deutsche Bundesbank (member of
   ESCB) for usage within messages standardized by the Eurosystem.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 21, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 1]
Internet-Draft          Eurosystem URN Namespace           February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Namespace Considerations  . . . . . . . . . . . . . . . . . . . 3
   3.  Community Considerations  . . . . . . . . . . . . . . . . . . . 4
   4.  Registration Template for the Eurosystem URN Namespace  . . . . 4
   5.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
     7.1.  Registration of Formal URN Namespace 'eurosystem' . . . . . 7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     9.2.  Informative References  . . . . . . . . . . . . . . . . . . 8

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 2]
Internet-Draft          Eurosystem URN Namespace           February 2014

1.  Introduction

   The European System of Central Banks (ESCB) is composed of the
   European Central Bank (ECB) [ECB] and the national central banks
   (NCBs) of all 27 EU Member States (Article 107.01 of the Treaty) --
   whether they have adopted the Euro currency or not.  One central bank
   belonging to the ESCB is Deutsche Bundesbank [DBBK], which, for the
   purpose of this document, is acting on behalf of the ESCB.  The term
   Eurosystem is used to refer to the entity composed of the ECB and the
   NCBs of those member states that have adopted the Euro currency.  For
   further information on the tasks of the ESCB and the Eurosystem,
   please refer to the ECB web site ([ECB], [ESCB], [Eurosystem]).

   The ESCB provides the market infrastructures TARGET2 (Trans-European
   Automated Realtime Gross Settlement Express Transfer) system, which
   is an interbank payment system for the real-time processing of cross-
   border transfers throughout the European Union.  In addition, the
   ESCB is currently implementing TARGET2-Securities, a future
   securities settlement platform that offers a new, harmonized and
   centralized method of settling securities in central bank money.  The
   TARGET2-Securities project was initiated by the Eurosystem as
   platform-owner in 2006.  TARGET2-Securities is currently under
   development.  Four central banks of the Eurosystem - Deutsche
   Bundesbank, Banque de France, Banca d'Italia and Banco de Espana
   (4CB) - are entrusted with the development and the operation of the
   platform.  For details, see [T2S_ECB], [T2S_DBBK].

   The future users of TARGET2-Securities will communicate and exchange
   information with the platform via messages (a set of structured
   information) following the ISO 20022 Standard [ISO20022-RA].

   This document specifies and registers with IANA a URN Namespace for
   the Eurosystem, which will be populated initially by names for
   abstract and concrete entities used in TARGET2-Securities messaging,
   but may be used for similar purposes in the future.

2.  Namespace Considerations

   The goal of the requested namespace is to ensure the stability and
   uniqueness of the names of various items that are used within the
   messages exchanged between the Eurosystem and the users of TARGET2-
   Securities (or potentially, other future projects of the Eurosystem).

   It is essential that names of items (such as the XML schema
   describing the message itself) can be used to identify the resource
   even years after the message has been exchanged.  This context
   requires a new namespace owned by, and under the perpetual control
   of, the Eurosystem.

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 3]
Internet-Draft          Eurosystem URN Namespace           February 2014

   The messaging context of the needed identifiers necessitates the
   usage of Uniform Resource Identifiers (URIs) as specified in Internet
   STD 66 [RFC3986].

   The persistent identifiers needed are protocol independent resource
   names -- the same resource may exist in multiple physical locations,
   and thus be accessible via multiple URLs, but there's the need for a
   single abstract identifier as a handle (name) for it.

   Thus, the logical choice for the placement of such namespace is the
   use of Uniform Resource Names (URNs, as defined by [RFC1737] and
   [RFC2141]) (and its work-in-progress successor), by specifying a new
   URN Namespace [RFC3406] for the Eurosystem.

3.  Community Considerations

   The Eurosystem messages carrying the resource names are exchanged in
   IP networks.  Although the mass production use of the assigned URNs
   will be contained in messages carried in cryptographic digital
   envelopes or Virtual Private Networks, the message-related resources
   being persistently named need to be referred to and resolved in the
   public Internet: 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.  URI references to the Eurosystem resources will be used in
   connection with identifiers drawn from previously standardized Formal
   URN Namespaces allocated to other international treaty organizations,
   and it is mandatory that the authority behind the new URNs be easily
   and clearly identified, and be at a perceived "equivalent" standards
   level, parallel to the existing ones.  Therefore, a mnemonic, Formal
   URN Namespace Identifier is needed for the intended purpose.

   Thus, this document specifies a "Formal URN Namespace" using the
   procedures laid down in RFC 3406 [RFC3406] (and incorporates some of
   the additional information under discussion for its work-in-progress
   successor into the registration template below).

   The requested URN Namespace Identifier (NID) is 'eurosystem'.

4.  Registration Template for the Eurosystem URN Namespace

   The registration template below makes references to Internet STD 66,
   RFC 3986 [RFC3986].

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 4]
Internet-Draft          Eurosystem URN Namespace           February 2014

   Namespace ID:   eurosystem

   Scope / kind of named resources:

      Resources related to Eurosystem messaging.

      This namespace is reserved to the Eurosystem and its community.

   Registration Information:

      -  version number:  1
      -  date:  2013-12-19

   Declared registrant of the Namespace:

      -  Registering organization:
         Name: Deutsche Bundesbank (member of ESCB)
            Wilhelm-Epstein-Strasse 14
            D-60431  Frankfurt

      -  Designated contact person:
         Name: Miriam Ortseifen
            Deutsche Bundesbank
            Zentrale, T2- und T2S-Service-Management
            Wilhelm-Epstein-Strasse 14
            D-60431  Frankfurt am Main

   Declaration of syntactic structure of NSS part:

      The structure of the Namespace Specific String is a flat space of
      printable URI characters (<pchar>, see RFC 3986), with a
      preference to short letter-digit-period-hyphen based strings.
      The NSS has no knowable structure outside of the context of the
      Eurosystem community internal resolver.

   Relevant ancillary documentation:


   Conformance with URN Syntax:

      No special consideration.

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 5]
Internet-Draft          Eurosystem URN Namespace           February 2014

   Rules for Lexical Equivalence of NSS part:

      No special consideration.

   Usage of query part:

      There is no support for query instructions or other components of
      the query part to be used in URI references to 'eurosystem' URNs.

   Usage of fragment part:

      The fragment part of URI references to 'eurosystem' URNs has no
      particular specified utility.

   Identifier uniqueness considerations:

      Identifiers are opaquely assigned by Eurosystem URN Registration
      that guarantees uniqueness.  This is simply achieved by reliably
      keeping track of already assigned names and comparing all new
      proposed names to the ones already present in the database.  If
      the name already has been assigned, a new one has to be proposed.

   Identifier persistence considerations:

      Assigned URNs will not be reused and will remain valid beyond the
      lifecycle of the referenced resources.  However, it should be
      noted that although the URNs remain valid, the status of the
      referenced resource may change.

   Process of identifier assignment:

      Names are granted by Eurosystem URN Registration via proprietary
      registration procedures.

      Future changes to the assignment methods may allow others to
      assign sub-spaces of the flat namespace, but again, this knowledge
      is only valid internally and should never be inferred or relied
      upon externally.

   Process of identifier resolution:

      Eurosystem URNs are resolved via URN resolvers run under
      Eurosystem responsibility.

      Initially, resolution service will be provided via a web page
      listing the assigned names and the related metadata of the named

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 6]
Internet-Draft          Eurosystem URN Namespace           February 2014

   Validation mechanism:

      None specified.

5.  Example

   The following example is listed for pedagogical reasons only; it is
   not guaranteed to become actually assigned.


6.  Security Considerations

   Since the URNs in this namespace are opaque, there are no additional
   security considerations other than those normally associated with the
   use and resolution of URIs and URNs in general (see the Security
   Considerations in Internet STD 66 [RFC3986], RFC 2141 [RFC2141], and
   BCP 66 [RFC3406]).

   It is noted however that attempting to resolve a Eurosystem URN
   through a resolver other than the one provided by the Eurosystem is
   error prone.  In any case, it is not considered authoritative.

7.  IANA Considerations

7.1.  Registration of Formal URN Namespace 'eurosystem'

   IANA maintains the registry of URN Namespaces [IANA-URN].  This
   document requests amendment of this registry by the registration of a
   new Formal URN Namespace with the NID 'eurosystem' as per BCP 66
   [RFC3406]), using the registration template given above in Section 4.

8.  Acknowledgements

   The authors would like to acknowledge the advice and constructive
   input received from Subramanian Moonesamy and Alfred Hoenes, as well
   as David Black and the IESG for last call comments that helped to
   improve this document.

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 7]
Internet-Draft          Eurosystem URN Namespace           February 2014

9.  References

9.1.  Normative References

   [RFC2141]  Moats, R., "URN Syntax", RFC 2141, May 1997.

   [RFC3406]  Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
              "Uniform Resource Names (URN) Namespace Definition
              Mechanisms", BCP 66, RFC 3406, October 2002.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, January 2005.

9.2.  Informative References

   [DBBK]     "Deutsche Bundesbank", <>.

   [ECB]      "European Central Bank", <>.

   [ESCB]     The European Central Bank, "ECB, ESCB and the Eurosystem",

              The European Central Bank, "The Eurosystem - The European
              System of Central Banks", ISBN 978-928990267-0,

              IANA, "URN Namespace Registry",

              ISO 20022 Registration Authority, "ISO 20022 - Universal
              financial industry message scheme",

   [RFC1737]  Sollins, K. and L. Masinter, "Functional Requirements for
              Uniform Resource Names", RFC 1737, December 1994.

              Deutsche Bundesbank, "TARGET2 Securities", <http://

   [T2S_ECB]  European Central Bank, "About T2S", <

Ortseifen & Dickfeld     Expires August 21, 2014                [Page 8]
Internet-Draft          Eurosystem URN Namespace           February 2014

Authors' Addresses

   Miriam Ortseifen
   Deutsche Bundesbank
   Wilhelm-Epstein-Strasse 14
   D-60431  Frankfurt


   Gunnar Dickfeld
   Deutsche Bundesbank
   Wilhelm-Epstein-Strasse 14
   D-60431  Frankfurt


Ortseifen & Dickfeld     Expires August 21, 2014                [Page 9]