Network Working Group J. Gustin Request for Comments: 3615 A. Goyens Category: Informational SWIFT September 2003 A Uniform Resource Name (URN) Namespace for SWIFT Financial Messaging Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved.
AbstractThis document describes a Uniform Resource Name (URN) namespace that is managed by SWIFT for usage within messages standardized by SWIFT.
1] which have no knowable structure outside of the context of the SWIFT community internal resolver. 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. Relevant ancillary Documentation: None Identifier uniqueness considerations: Identifiers are assigned by SWIFT URN Registration that guarantees uniqueness. This is simply achieved by keeping track of already assigned names and comparing all new proposed names to the database ones. If the name already exists a new one has to be proposed. Identifiers persistence considerations: The assignment process guarantees that names are not reassigned. In any case SWIFT URNs are guaranteed to remain valid for 15 years.
Process of identifiers assignment: Names are granted via SWIFT proprietary registration procedures. Process for identifier resolution: SWIFT URNs are resolved via URN resolvers run under SWIFT responsibility. Rules for lexical equivalence: No special consideration. Conformance with URN syntax: No special consideration. Validation mechanism: None specified. Scope: This namespace is reserved to the global financial community.
 Moats, R., "URN Syntax", RFC 2141, May 1997.  Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "Uniform Resource Name (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. http://www.swift.com
Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.