idnits 2.17.1 draft-rozenfeld-urn-issn-00.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3044 5 Title: Using The ISSN (International Serial Standard 6 Number) as URN (Uniform Resource Names) within an 7 ISSN-URN Namespace 8 Author(s): S. Rozenfeld 9 Status: Informational 10 Date: January 2001 11 Mailbox: rozenfeld@issn.org, issnic@issn.org 12 Pages: 15 13 Characters: 28094 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-rozenfeld-urn-issn-00.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3044.txt 20 This document presents how the ISSN - International Standard Serial 21 Number - which is a persistent number for unique identification of 22 serials widely recognised and used in the bibliographic world, can be 23 supported within the Uniform Resource Name (URN) framework as a 24 specific URN namespace identifier. 26 An ISSN URN resolution system using the ISSN identifier as Uniform 27 resource Name within an ISN URN Namespace has been developed by the 28 ISSN International Centre (ISSN-IC) and is operating as a demonstrator 29 to evaluate all requirements to deploy it in an operational 30 environment. 32 This proceeds from concepts and proposals developed in several IETF 33 RFCs emphasising the way to implement and to use "recognised" existing 34 numbering system within the URN framework (RFC 2248, RFC 2141, RFC 35 2611). 37 This memo provides information for the Internet community. It does 38 not specify an Internet standard of any kind. Distribution of this 39 memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.