RFC 3151 on A URN Namespace for Public Identifiers

RFC Editor <rfc-ed@ISI.EDU> Fri, 19 October 2001 23:46 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06037; Fri, 19 Oct 2001 19:46:12 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA08359 for ietf-123-outbound.10@ietf.org; Fri, 19 Oct 2001 19:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07186 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:11:20 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02913 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:11:15 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMBIH26003; Fri, 19 Oct 2001 15:11:18 -0700 (PDT)
Message-Id: <200110192211.f9JMBIH26003@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3151 on A URN Namespace for Public Identifiers
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:11:18 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3151

        Title:	    A URN Namespace for Public Identifiers
        Author(s):  N. Walsh, J. Cowan, P. Grosso
        Status:     Informational
	Date:       August 2001
        Mailbox:    Norman.Walsh@East.Sun.COM,
                    jcowan@reutershealth.com, pgrosso@arbortext.com 
        Pages:      9
        Characters: 15595
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-walsh-urn-publicid-01.txt

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


This document describes a URN (Uniform Resource Name) namespace that
is designed to allow Public Identifiers to be expressed in URI
(Uniform Resource Identifiers) syntax.

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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc3151.txt"><ftp://ftp.isi.edu/in-notes/rfc3151.txt>