RFC 4151 on The 'tag' URI Scheme

rfc-editor@rfc-editor.org Tue, 25 October 2005 23:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYTC-00051w-GH; Tue, 25 Oct 2005 19:44:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYT9-00050Y-V7 for ietf-announce@megatron.ietf.org; Tue, 25 Oct 2005 19:44:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05939 for <ietf-announce@ietf.org>; Tue, 25 Oct 2005 19:44:25 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYgC-0002eR-4Z for ietf-announce@ietf.org; Tue, 25 Oct 2005 19:58:09 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j9PNi7L28837; Tue, 25 Oct 2005 16:44:07 -0700 (PDT)
Message-Id: <200510252344.j9PNi7L28837@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 25 Oct 2005 16:44:07 -0700
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4151 on The 'tag' URI Scheme
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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


        RFC 4151

        Title:      The 'tag' URI Scheme
        Author(s):  T. Kindberg, S. Hawke
        Status:     Informational
        Date:       October 2005
        Mailbox:    timothy@hpl.hp.com, sandro@w3.org
        Pages:      11
        Characters: 22555
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-kindberg-tag-uri-07.txt

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


This document describes the "tag" Uniform Resource Identifier (URI)
scheme.  Tag URIs (also known as "tags") are designed to be unique
across space and time while being tractable to humans.  They are
distinct from most other URIs in that they have no authoritative
resolution mechanism.  A tag may be used purely as an entity
identifier.  Furthermore, using tags has some advantages over the
common practice of using "http" URIs as identifiers for
non-HTTP-accessible resources.

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.

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/rfc4151.txt"><ftp://ftp.isi.edu/in-notes/rfc4151.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce