RFC 3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8254.
Current document in this lineage: RFC 8254 — Uniform Resource Name (URN) Namespace Registration Transition
In plain English — editorial summary, not part of the RFC
This document presents how the ISSN - International Standard Serial Number - which is a persistent number for unique identification of serials widely recognised and used in the bibliographic world, can be supported within the Uniform Resource Name (URN) framework as a specific URN namespace identifier. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3044
- Published
- January 2001
- Authors
- S. Rozenfeld
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 15
- Also known as
- —
- Obsoleted by:
- RFC 8254
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3044 (2001)
- RFC 3187 (2001)
- RFC 8254 (2017) ✓
Read the full history of Uniform Resource Name (URN) Namespace Registration Transition →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3087Control of Service Context using SIP Request-URICurrent
April 2001
- RFC 2384POP URL SchemeCurrent
August 1998
- RFC 2187Application of Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 1980A Proposed Extension to HTML : Client-Side Image MapsObsoleted
August 1996
- RFC 3041Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
January 2001
- RFC 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 2607Proxy Chaining and Policy Implementation in RoamingCurrent
June 1999
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?