[Search] [txt|pdf|bibtex] [Tracker] [WG] [Email] [Nits]

Versions: 00                                                            
Internet-Draft                                                Ryan Moats
draft-ietf-schema-whois-00.txt                                      AT&T
Expires in six months                                         April 1998


                     A MIME Content-Type for WHOIS
                Filename: draft-ietf-schema-whois-00.txt

Status of this Memo

      This document is an Internet-Draft.  Internet-Drafts are working
      documents of the Internet Engineering Task Force (IETF), its
      areas, and its working groups.  Note that other groups may also
      distribute working documents as Internet-Drafts.

      Internet-Drafts are draft documents valid for a maximum of six
      months and may be updated, replaced, or obsoleted by other
      documents at any time.  It is inappropriate to use Internet-
      Drafts as reference material or to cite them other than as ``work
      in progress.''

      To learn the current status of any Internet-Draft, please check
      the ``1id-abstracts.txt'' listing contained in the Internet-
      Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
      (Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East
      Coast), or ftp.isi.edu (US West Coast).


Abstract

   This document defines a MIME directory profile [1] for holding a
   WHOIS [2] schema and is intended for communication with the Internet
   schema listing service.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [3].

1. Overview

   The document defines how a MIME type may be used to transfer a single
   WHOIS schema definition.  Although [2] specifies the result as non-
   machine readable it should be realized that the returned object is
   simply text.  Schemas created from this specify the parsing of the
   text.  Therefore an example of how a to register a WHOIS schema is
   presented.





Expires 10/31/98                                                [Page 1]


INTERNET DRAFT           Mime Content for WHOIS               April 1998


2. Example MIME Directory Type Registrations

   This document defines an example whoisSchema used in the "schema-
   whois-example-0" profile.

2.1 whoisSchema

   To: ietf-mime-direct@imc.org
   Subject: Registration of text/directory MIME type whoisSchema

   Type name: whoisSchema

   Type purpose: To represent an example WHOIS schema

   Type encoding: 8bit

   Type valuetype: text, encoded according to the BNF of section 2.1.1

   Type special notes: Each value of this type specifies the contents of
   a WHOIS schema definition.  A definition of all attributes in the schema
   MUST be present in the content containing this value.

   Intended usage: COMMON

2.1.1 whoisSchema Syntax Definition

   Values of whoisSchema are represented according to the following BNF:

      whoisSchema = "(" whsp attribute-line *[whsp "$" whsp attribute-line] whsp ")"
      attribute-line = *[ "line:" whsp attr *[whsp "$" whsp attr]
      attr = 1*utf8

   All attributes have text values.  It should be noted that this
   definition is not intended to handle all formatting circumstances nor
   is intended for complete machine parsing.

3.0 Example

  From: whomever@wherever.com
  To: Someone@somewhere.com
  Subject: schema information
  MIME-Version: 1.0
  Message-Id: <ids1@wherever.com>
  Content-Type: text/directory; profile="schema-whois-0";charset="utf-8"
  Content-Transfer-Encoding: Quoted-Printable
  whoisSchema: ( line: Lastname $ Firstname  $ Handle $ Email $
    line: Address1 $ line: Address2 $ line: City $ State $ Zip $
    line: Phones $ line: null $ line: Record-Last-Updated $



Expires 10/31/98                                                [Page 2]


INTERNET DRAFT           Mime Content for WHOIS               April 1998


    line: Database-Last-Updated $ line: Announcements )

4. Security Considerations

   A MIME body part containing a text/directory may be incorporated in a
   digitally signed MIME content, which can be used to verify that the
   body part has not been modified in transit.  When the signer has been
   certified by a trusted third party service, it may also be possible
   to verify the origin of the content.

5. Acknowledgments

   Thanks to various members of the SCHEMA Working Group for comments on
   earlier drafts of this document.  The work described in this document
   is partially supported by the National Science Foundation,
   Cooperative Agreement NCR-9218179.

6. Refernces

   Request For Comments (RFC) are available from ftp://venera.isi.edu,
   Internet Draft documents are available from ftp://ftp.ietf.org, and
   both are available from numerous mirror sites.

[1]         M. Wahl, "A MIME Content-Type for Directory Information,"
            Internet Draft (work in progress), March 8, 1998.


[2]         K. Harrenstien, M.K. Stahl, E.J. Feinler, "NICNAME/WHOIS,"
            RFC 954, October 1985.


[3]         S. Bradner, "Key words for use in RFCs to Indicate Require-
            ment Levels," RFC 2119, March 1997.

7. Author's Address

   Ryan Moats
   AT&T
   15621 Drexel Circle
   Omaha, NE 68135-2358
   USA

   Email: jayhawk@att.com








Expires 10/31/98                                                [Page 3]