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


        RFC 1913:

        Title:      Architecture of the Whois++ Index Service
        Author:     C. Weider, J. Fullton & S. Spero
        Date:       February 1996
        Mailbox:    clw@bunyip.com, fullton@cnidr.org, ses@eit.com
        Pages:      16
        Characters: 33,743
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1913.txt


The WHOIS++ directory service is intended to provide a simple,
extensible directory service predicated on a template-based
information model and a flexible query language.  This RFC describes a
general architecture designed for indexing distributed databases, and
then applys that architecture to link together many of these WHOIS++
servers into a distributed, searchable wide area directory service.
This RFC is the product of the Whois and Network Information Lookup
Service Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  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@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute