BCP 81, RFC 3688 on The IETF XML Registry
rfc-editor@rfc-editor.org Sat, 31 January 2004 01:00 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23179 for <ietf-announce-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:00:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AmjLn-0005DI-0v for ietf-announce-list@asgard.ietf.org; Fri, 30 Jan 2004 19:51:07 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AmjLD-00054m-IR for all-ietf@asgard.ietf.org; Fri, 30 Jan 2004 19:50:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12295 for <all-ietf@ietf.org>; Fri, 30 Jan 2004 19:50:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmjLB-00058E-00 for all-ietf@ietf.org; Fri, 30 Jan 2004 19:50:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmjKC-0004x0-00 for all-ietf@ietf.org; Fri, 30 Jan 2004 19:49:29 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AmjJC-0004gU-00 for all-ietf@ietf.org; Fri, 30 Jan 2004 19:48:27 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0V0mQk01015; Fri, 30 Jan 2004 16:48:26 -0800 (PST)
Message-Id: <200401310048.i0V0mQk01015@gamma.isi.edu>
To: IETF-Announce:;
Subject: BCP 81, RFC 3688 on The IETF XML Registry
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 30 Jan 2004 16:48:26 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.2 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries.
BCP 81
RFC 3688
Title: The IETF XML Registry
Author(s): M. Mealling
Status: Best Current Practice
Date: January 2004
Mailbox: michael@verisignlabs.com
Pages: 8
Characters: 17325
SeeAlso: BCP 81
I-D Tag: draft-mealling-iana-xmlns-registry-05.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3688.txt
This document describes an IANA maintained registry for IETF standards
which use Extensible Markup Language (XML) related items such as
Namespaces, Document Type Declarations (DTDs), Schemas, and Resource
Description Framework (RDF) Schemas.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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.
- BCP 81, RFC 3688 on The IETF XML Registry rfc-editor