draft-hakala-nbn

Last Version:	draft-hakala-nbn-01.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	RFC3188 (diff)
Previous Versions:	draft-hakala-nbn-00.txt (diff)    - 06-Dec-2000

A new Request for Comments is now available in online RFC libraries.


        RFC 3188

        Title:      Using National Bibliography Numbers as Uniform
                    Resource Names
        Author(s):  J. Hakala
        Status:     Informational
        Date:       October 2001
        Mailbox:    juha.hakala@helsinki.fi
        Pages:      13
        Characters: 27923
        SeeAlso/Updates/Obsoletes:    None

        I-D Tag:    draft-hakala-nbn-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3188.txt


This document discusses how national bibliography numbers (persistent
and unique identifiers assigned by the national libraries) can be
supported within the URN (Uniform Resource Names) framework and the
syntax for URNs defined in RFC 2141.  Much of the discussion is
based on the ideas expressed in RFC 2288.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.