RFC 2656 on Registration Procedures for SOIF

RFC Editor <rfc-ed@ISI.EDU> Mon, 16 August 1999 17:16 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00126; Mon, 16 Aug 1999 13:16:55 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA19251 for ietf-123-outbound.10@ietf.org; Mon, 16 Aug 1999 13:15: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 MAA18927 for <all-ietf@loki.ietf.org>; Mon, 16 Aug 1999 12:53:14 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28422 for <all-ietf@ietf.org>; Mon, 16 Aug 1999 12:48:06 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA12396; Mon, 16 Aug 1999 09:48:06 -0700 (PDT)
Message-Id: <199908161648.JAA12396@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2656 on Registration Procedures for SOIF
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 16 Aug 1999 09:48:06 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2656:

        Title:	    Registration Procedures for SOIF Template Types
        Author(s):  T. Hardie
        Status:     Experimental
	Date:       August 1999
        Mailbox:    hardie@equinix.com
        Pages:      9
        Characters: 17409 
	Updates:    
        I-D Tag:    draft-ietf-find-soif-registry-00.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2656.txt


The registration procedure described in this document is specific to
SOIF template types.

This document is a product of the Common Indexing Protocol Working
Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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/rfc2656.txt"><ftp://ftp.isi.edu/in-notes/rfc2656.txt>