idnits 2.17.1 draft-bundesbank-eurosystem-namespace-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 17, 2014) is 3719 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF M. Ortseifen 3 Internet-Draft G. Dickfeld 4 Intended status: Informational Deutsche Bundesbank 5 Expires: August 21, 2014 February 17, 2014 7 A Uniform Resource Name (URN) Namespace for Eurosystem Messaging 8 draft-bundesbank-eurosystem-namespace-03 10 Abstract 12 This document defines and registers with IANA a Uniform Resource Name 13 (URN) namespace that is managed by Deutsche Bundesbank (member of 14 ESCB) for usage within messages standardized by the Eurosystem. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on August 21, 2014. 33 Copyright Notice 35 Copyright (c) 2014 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Namespace Considerations . . . . . . . . . . . . . . . . . . . 3 52 3. Community Considerations . . . . . . . . . . . . . . . . . . . 4 53 4. Registration Template for the Eurosystem URN Namespace . . . . 4 54 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 55 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 56 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 57 7.1. Registration of Formal URN Namespace 'eurosystem' . . . . . 7 58 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 59 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 60 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 61 9.2. Informative References . . . . . . . . . . . . . . . . . . 8 63 1. Introduction 65 The European System of Central Banks (ESCB) is composed of the 66 European Central Bank (ECB) [ECB] and the national central banks 67 (NCBs) of all 27 EU Member States (Article 107.01 of the Treaty) -- 68 whether they have adopted the Euro currency or not. One central bank 69 belonging to the ESCB is Deutsche Bundesbank [DBBK], which, for the 70 purpose of this document, is acting on behalf of the ESCB. The term 71 Eurosystem is used to refer to the entity composed of the ECB and the 72 NCBs of those member states that have adopted the Euro currency. For 73 further information on the tasks of the ESCB and the Eurosystem, 74 please refer to the ECB web site ([ECB], [ESCB], [Eurosystem]). 76 The ESCB provides the market infrastructures TARGET2 (Trans-European 77 Automated Realtime Gross Settlement Express Transfer) system, which 78 is an interbank payment system for the real-time processing of cross- 79 border transfers throughout the European Union. In addition, the 80 ESCB is currently implementing TARGET2-Securities, a future 81 securities settlement platform that offers a new, harmonized and 82 centralized method of settling securities in central bank money. The 83 TARGET2-Securities project was initiated by the Eurosystem as 84 platform-owner in 2006. TARGET2-Securities is currently under 85 development. Four central banks of the Eurosystem - Deutsche 86 Bundesbank, Banque de France, Banca d'Italia and Banco de Espana 87 (4CB) - are entrusted with the development and the operation of the 88 platform. For details, see [T2S_ECB], [T2S_DBBK]. 90 The future users of TARGET2-Securities will communicate and exchange 91 information with the platform via messages (a set of structured 92 information) following the ISO 20022 Standard [ISO20022-RA]. 94 This document specifies and registers with IANA a URN Namespace for 95 the Eurosystem, which will be populated initially by names for 96 abstract and concrete entities used in TARGET2-Securities messaging, 97 but may be used for similar purposes in the future. 99 2. Namespace Considerations 101 The goal of the requested namespace is to ensure the stability and 102 uniqueness of the names of various items that are used within the 103 messages exchanged between the Eurosystem and the users of TARGET2- 104 Securities (or potentially, other future projects of the Eurosystem). 106 It is essential that names of items (such as the XML schema 107 describing the message itself) can be used to identify the resource 108 even years after the message has been exchanged. This context 109 requires a new namespace owned by, and under the perpetual control 110 of, the Eurosystem. 112 The messaging context of the needed identifiers necessitates the 113 usage of Uniform Resource Identifiers (URIs) as specified in Internet 114 STD 66 [RFC3986]. 116 The persistent identifiers needed are protocol independent resource 117 names -- the same resource may exist in multiple physical locations, 118 and thus be accessible via multiple URLs, but there's the need for a 119 single abstract identifier as a handle (name) for it. 121 Thus, the logical choice for the placement of such namespace is the 122 use of Uniform Resource Names (URNs, as defined by [RFC1737] and 123 [RFC2141]) (and its work-in-progress successor), by specifying a new 124 URN Namespace [RFC3406] for the Eurosystem. 126 3. Community Considerations 128 The Eurosystem messages carrying the resource names are exchanged in 129 IP networks. Although the mass production use of the assigned URNs 130 will be contained in messages carried in cryptographic digital 131 envelopes or Virtual Private Networks, the message-related resources 132 being persistently named need to be referred to and resolved in the 133 public Internet: The transparency requirements (needed for 134 establishing and maintaining public trust into the subject financial 135 transaction systems), open software development processes, and 136 software deployment require the origin and authority for the URNs to 137 be easily identified, and the URNs to be resolved on the public 138 Internet. URI references to the Eurosystem resources will be used in 139 connection with identifiers drawn from previously standardized Formal 140 URN Namespaces allocated to other international treaty organizations, 141 and it is mandatory that the authority behind the new URNs be easily 142 and clearly identified, and be at a perceived "equivalent" standards 143 level, parallel to the existing ones. Therefore, a mnemonic, Formal 144 URN Namespace Identifier is needed for the intended purpose. 146 Thus, this document specifies a "Formal URN Namespace" using the 147 procedures laid down in RFC 3406 [RFC3406] (and incorporates some of 148 the additional information under discussion for its work-in-progress 149 successor into the registration template below). 151 The requested URN Namespace Identifier (NID) is 'eurosystem'. 153 4. Registration Template for the Eurosystem URN Namespace 155 The registration template below makes references to Internet STD 66, 156 RFC 3986 [RFC3986]. 158 Namespace ID: eurosystem 160 Scope / kind of named resources: 162 Resources related to Eurosystem messaging. 164 This namespace is reserved to the Eurosystem and its community. 166 Registration Information: 168 - version number: 1 169 - date: 2013-12-19 171 Declared registrant of the Namespace: 173 - Registering organization: 174 Name: Deutsche Bundesbank (member of ESCB) 175 Address: 176 Wilhelm-Epstein-Strasse 14 177 D-60431 Frankfurt 178 Germany 179 URI: http://www.bundesbank.de/ 181 - Designated contact person: 182 Name: Miriam Ortseifen 183 Address: 184 Deutsche Bundesbank 185 Zentrale, T2- und T2S-Service-Management 186 Wilhelm-Epstein-Strasse 14 187 D-60431 Frankfurt am Main 188 Germany 189 Email: iso20022@bundesbank.de 191 Declaration of syntactic structure of NSS part: 193 The structure of the Namespace Specific String is a flat space of 194 printable URI characters (, see RFC 3986), with a 195 preference to short letter-digit-period-hyphen based strings. 196 The NSS has no knowable structure outside of the context of the 197 Eurosystem community internal resolver. 199 Relevant ancillary documentation: 201 None 203 Conformance with URN Syntax: 205 No special consideration. 207 Rules for Lexical Equivalence of NSS part: 209 No special consideration. 211 Usage of query part: 213 There is no support for query instructions or other components of 214 the query part to be used in URI references to 'eurosystem' URNs. 216 Usage of fragment part: 218 The fragment part of URI references to 'eurosystem' URNs has no 219 particular specified utility. 221 Identifier uniqueness considerations: 223 Identifiers are opaquely assigned by Eurosystem URN Registration 224 that guarantees uniqueness. This is simply achieved by reliably 225 keeping track of already assigned names and comparing all new 226 proposed names to the ones already present in the database. If 227 the name already has been assigned, a new one has to be proposed. 229 Identifier persistence considerations: 231 Assigned URNs will not be reused and will remain valid beyond the 232 lifecycle of the referenced resources. However, it should be 233 noted that although the URNs remain valid, the status of the 234 referenced resource may change. 236 Process of identifier assignment: 238 Names are granted by Eurosystem URN Registration via proprietary 239 registration procedures. 241 Future changes to the assignment methods may allow others to 242 assign sub-spaces of the flat namespace, but again, this knowledge 243 is only valid internally and should never be inferred or relied 244 upon externally. 246 Process of identifier resolution: 248 Eurosystem URNs are resolved via URN resolvers run under 249 Eurosystem responsibility. 251 Initially, resolution service will be provided via a web page 252 listing the assigned names and the related metadata of the named 253 resources. 255 Validation mechanism: 257 None specified. 259 5. Example 261 The following example is listed for pedagogical reasons only; it is 262 not guaranteed to become actually assigned. 264 urn:eurosystem:xsd:reda.012.001.01 266 6. Security Considerations 268 Since the URNs in this namespace are opaque, there are no additional 269 security considerations other than those normally associated with the 270 use and resolution of URIs and URNs in general (see the Security 271 Considerations in Internet STD 66 [RFC3986], RFC 2141 [RFC2141], and 272 BCP 66 [RFC3406]). 274 It is noted however that attempting to resolve a Eurosystem URN 275 through a resolver other than the one provided by the Eurosystem is 276 error prone. In any case, it is not considered authoritative. 278 7. IANA Considerations 280 7.1. Registration of Formal URN Namespace 'eurosystem' 282 IANA maintains the registry of URN Namespaces [IANA-URN]. This 283 document requests amendment of this registry by the registration of a 284 new Formal URN Namespace with the NID 'eurosystem' as per BCP 66 285 [RFC3406]), using the registration template given above in Section 4. 287 8. Acknowledgements 289 The authors would like to acknowledge the advice and constructive 290 input received from Subramanian Moonesamy and Alfred Hoenes, as well 291 as David Black and the IESG for last call comments that helped to 292 improve this document. 294 9. References 296 9.1. Normative References 298 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 300 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 301 "Uniform Resource Names (URN) Namespace Definition 302 Mechanisms", BCP 66, RFC 3406, October 2002. 304 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 305 Resource Identifier (URI): Generic Syntax", STD 66, 306 RFC 3986, January 2005. 308 9.2. Informative References 310 [DBBK] "Deutsche Bundesbank", . 312 [ECB] "European Central Bank", . 314 [ESCB] The European Central Bank, "ECB, ESCB and the Eurosystem", 315 . 317 [Eurosystem] 318 The European Central Bank, "The Eurosystem - The European 319 System of Central Banks", ISBN 978-928990267-0, 320 . 322 [IANA-URN] 323 IANA, "URN Namespace Registry", 324 . 326 [ISO20022-RA] 327 ISO 20022 Registration Authority, "ISO 20022 - Universal 328 financial industry message scheme", 329 . 331 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 332 Uniform Resource Names", RFC 1737, December 1994. 334 [T2S_DBBK] 335 Deutsche Bundesbank, "TARGET2 Securities", . 340 [T2S_ECB] European Central Bank, "About T2S", . 343 Authors' Addresses 345 Miriam Ortseifen 346 Deutsche Bundesbank 347 Wilhelm-Epstein-Strasse 14 348 D-60431 Frankfurt 349 Germany 351 Email: iso20022@bundesbank.de 353 Gunnar Dickfeld 354 Deutsche Bundesbank 355 Wilhelm-Epstein-Strasse 14 356 D-60431 Frankfurt 357 Germany 359 Email: iso20022@bundesbank.de