[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: I-D defining a MIME directory profile for WHOIS schema...
In Chris Apple's draft-ietf-schema-mime-metadata-00.txt, there is a reference pointer
to [MIMEWHOIS], containing schema information for WHOIS. Since I suggested to Chris
that this would be a good (or a last historical) idea, he suggested that I write the profile
(gak!). I have a draft of the profile that I didn't get a chance to submit to the i-d
editor until after LA. It's posted here so that the reference pointer doesn't go away
in Chris's draft.
This draft proposes to be under the ietf-schema portion of the tree, since the document
pointing to it is also under the ietf-schema portion of the tree. However, since it won't
be going to the i-d editor until after the meeting in LA, I don't have a problem with changing
it (especially since some of the items are still TBD).
As always, comments welcome...
Ryan Moats
jayhawk@xxxxxxx
===================cut here
Internet-Draft Ryan Moats
draft-ietf-schema-whois-00.txt AT&T
Expires in six months March 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.
2. The "schema-whois-0" MIME Directory Profile Registration
This profile is identified by the following registration template
information.
Expires 9/30/98 [Page 1]
INTERNET DRAFT Mime Content for WHOIS March 1998
To: ietf-mime-direct@xxxxxxx
Subject: Registration of text/directory MIME profile "schema-whois-0"
Profile Name: schema-whois-0
Profile purpose: To represent a schema defined for use with
WHOIS servers.
Profile types: whoisSchema, whoisAttribute
Profile special notes:
The charset parameter MUST be present in the MIME content, and its
value MUST be "utf-8". This allows for future expansion of the
WHOIS schema to support schema values encoded in UTF-8.
Neither the "BEGIN" and "END" types nor type grouping are used i
contents of this profile.
The whoisSchema type in this profile MUST be single valued. The
whoisAttribute type MAY be multi-valued, with each value being
present on its own contentline, in any order.
In this version of the profile, exactly one value of the whoisSchema
type MUST be present. Later version of the profile MAY permit
multiple whoisSchema values to be present in a content.
Implementors should note that there will likely be values of the
profile types with contents much longer than 76 bytes. In
addition, there may eventually be non-ASCII characters and embedded
CRLFs inside of values, which could require either quoting of the
value or use of a content transfer encoding.
If a contentline in a particular content contains a "context"
parameter and the value of that parameter is not "whois", then that
contentline SHOULD be ignored.
Intended usage: COMMON
3. MIME Directory Type Registrations
This document defines both the whoisSchema and whoisAttribute types
used in the "schema-whois-0" profile. While these types are primarily
intended for use in the "schema-whois-0" directory profile, they may
be applicable to other profiles defined in the future.
Expires 9/30/98 [Page 2]
INTERNET DRAFT Mime Content for WHOIS March 1998
3.1 whoisSchema
To: ietf-mime-direct@xxxxxxx
Subject: Registration of text/directory MIME type whoisSchema
Type name: whoisSchema
Type purpose: To represent the WHOIS schema
Type encoding: 8bit
Type valuetype: text, encoded according to the BNF of section 3.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
3.1.1 whoisSchema Syntax Definition
Values of whoisSchema are represented according to the following BNF:
whoisSchema = "(" whsp [ "ATTRIBUTES" attr ] [ "SYNTAXES" synt ] whsp ")"
attr = "(" whsp attrname whsp *["$" whsp attrname whsp] ")"
attrname = 1*utf8
synt = "(" whsp syntax whsp *["$" whsp syntax whsp] ")"
syntax = "utf8" / "languageTag" / "authEmail" / "intPhone" / "domain" /
"dateString" / "serverList"
The individual syntax types are in order, UTF-8 octets, a language
tag as specified in [4], an e-mail address and an international phone
number (as specified in [5]), a string of DNS legal characters, a
date string and a list of servers. A date string has the following
BNF:
datestring = year "-" month "-" day
year = 4*number ; the common year (4 digit form)
month = 2*number ; month in numeric form
day = 2*number ; day in numeric form
Lastly, a list of servers has the following BNF:
serverlist = "(" whsp 1*[ "(" whsp fqdn whsp ipaddr whsp ")" whsp ] ")"
where fqdn is a fully qualified domain named and ipaddr is an IPv4
address in dotted decimal notation.
Expires 9/30/98 [Page 3]
INTERNET DRAFT Mime Content for WHOIS March 1998
3.2 whoisAttribute
To: ietf-mime-direct@xxxxxxx
Subject: Registration of text/directory MIME type whoisAttribute
Type name: whoisAttribute
Type purpose: To represent the whoisAttribute specified in the whoisSchema
type contained in the current content.
Type encoding: 8bit
Type valuetype: text, encoded according to the BNF of section 3.2.1
Type special notes: Each value of the type specifies a single
attribute of the WHOIS schema. Both the name and syntax of this
attribute MUST be included in the whoisSchema type contained in the
current content.
3.2.1 whoisAttribute syntax specification
Attributes for the WHOIS schema are specified according to the
following BNF:
whoisAttribute = "(" whsp "NAME" whsp "'" attrname "'" whsp
"SYNTAX" attrSyntax whsp ")"
attrname = 1*utf8
attrSyntax = syntax ["{" number "}"]
The optional bracketed portion of the attrSyntax allows a maximum
length for that field to be specified.
4.0 Example
From: whomever@xxxxxxxxxxxx
To: Someone@xxxxxxxxxxxxx
Subject: schema information
MIME-Version: 1.0
Message-Id: <ids1@xxxxxxxxxxxx>
Content-Type: text/directory; profile="schema-whois-0";charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable
whoisSchema: ( ATTRIBUTES ( domainName $ registeringOrg $
registeringOrgAddress $ adminContactLang $ adminContactName $
adminContactEmail $ adminContactPhone $ adminContactFAX $
techContactLang $ techContactName $ techContactEmail $
techContactPhone $ techContactFAX $ zoneContactLang $
zoneContactName $ zoneContactEmail $ zoneContactPhone $
zoneContactFAX $ billingContactLang $ billingContactName $
billingContactEmail $ billingContactPhone $ billingContactFAX $
Expires 9/30/98 [Page 4]
INTERNET DRAFT Mime Content for WHOIS March 1998
handle $ domainServers $ recordUpdatedDate $ recordCreatedDate )
SYNTAXES ( utf8 $ languageTag $ authEmail $ intPhone $ domain $
serverList $ dateString ) )
whoisAttribute: ( NAME 'domainName' SYNTAX utf8{256} )
whoisAttribute: ( NAME 'registeringOrg' SYNTAX utf8{32768} )
whoisAttribute: ( NAME 'registeringOrgAddress' SYNTAX utf8{32768} )
whoisAttribute: ( NAME 'adminContactLang' SYNTAX languageTag )
whoisAttribute: ( NAME 'adminContactName' SYNTAX utf8{1024} )
whoisAttribute: ( NAME 'adminContactEmail' SYNTAX authEmail )
whoisAttribute: ( NAME 'adminContactPhone' SYNTAX intPhone )
whoisAttribute: ( NAME 'adminContactFAX' SYNTAX intPhone )
whoisAttribute: ( NAME 'techContactLang' SYNTAX languageTag )
whoisAttribute: ( NAME 'techContactName' SYNTAX utf8{1024} )
whoisAttribute: ( NAME 'techContactEmail' SYNTAX authEmail )
whoisAttribute: ( NAME 'techContactPhone' SYNTAX intPhone )
whoisAttribute: ( NAME 'techContactFAX' SYNTAX intPhone )
whoisAttribute: ( NAME 'zoneContactLang' SYNTAX languageTag )
whoisAttribute: ( NAME 'zoneContactName' SYNTAX utf8{1024} )
whoisAttribute: ( NAME 'zoneContactEmail' SYNTAX authEmail )
whoisAttribute: ( NAME 'zoneContactPhone' SYNTAX intPhone )
whoisAttribute: ( NAME 'zoneContactFAX' SYNTAX intPhone )
whoisAttribute: ( NAME 'billingContactLang' SYNTAX languageTag )
whoisAttribute: ( NAME 'billingContactName' SYNTAX utf8{1024} )
whoisAttribute: ( NAME 'billingContactEmail' SYNTAX authEmail )
whoisAttribute: ( NAME 'billingContactPhone' SYNTAX intPhone )
whoisAttribute: ( NAME 'billingContactFAX' SYNTAX intPhone )
whoisAttribute: ( NAME 'handle' SYNTAX domain{32} )
whoisAttribute: ( NAME 'domainServers' SYNTAX serverList )
whoisAttribute: ( NAME 'recordUpdatedDate' SYNTAX dateString )
whoisAttribute: ( NAME 'recordCreatedDate' SYNTAX dateString )
4. Schema Unit Listing
listingName: tbd
listingTitle;language=en: MimeWHOIS
listingUse;language=en: WHOIS Schema V1.0
specFile: base.1.0.whois
contactLanguage: en
contactName: Ryan Moats
contactEmail: jayhawk@xxxxxxx
contactPhone: +1 402 894 9456
contactAddress: 15621 Drexel Circle $ Omaha, NE 68135-2358 $ USA
authLanguage: en
authName: Ryan Moats
authEmail: jayhawk@xxxxxxx
authPhone: +1 402 894 9456
authAddress: 15621 Drexel Circle $ Omaha, NE 68135-2358 $ USA
security;language=en: Most WHOIS information is considered public=0A=
Expires 9/30/98 [Page 5]
INTERNET DRAFT Mime Content for WHOIS March 1998
domain so this schema only inherits the underlying security=0A=
considerations of the WHOIS protocol and architecture.
5. Security Considerations
A MIME body part containing a text/directory of the schema-whois-0
profile 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.
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 Infor-
mation," 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
Requirement Levels," RFC 2119, March 1997.
[4] H. Alvestrand, "Tags for the Identification of
Languages," March 1995.
[5] C. Apple, "Directory Schema Listing Meta Data,"
Internet Draft (work in progress), January 31,
1998.
7. Author's Address
Ryan Moats
AT&T
15621 Drexel Circle
Omaha, NE 68135-2358
USA
Email: jayhawk@xxxxxxx
Expires 9/30/98 [Page 6]
INTERNET DRAFT Mime Content for WHOIS March 1998
Expires 9/30/98 [Page 7]