[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Content Negotiation
Working Group of the IETF.
Title : Content Feature Tag Registration Procedure
Author(s) : E. Hardie, K. Holtman, A. Mutz
Filename : draft-ietf-conneg-feature-reg-01.txt
Pages : 10
Date : 06-Jul-98
Recent Internet applications, such as the World Wide Web, tie together a great diversity in data formats, client and server platforms, and communities. This has created a need for content feature descriptions and negotiation mechanisms in order to identify and reconcile the form of information to the capabilities and preferences of the parties involved.
Extensible content feature identification and negotiation mechanisms require a common vocabulary in order to positively identify content features. A registration process and authority for content features is defined with the intent of sharing this vocabulary between communicating parties. In addition, a URI tree is defined to enable sharing of content feature definitions without registration.
This document defines a registration procedure which uses the Internet Assigned Numbers Authority (IANA) as a central registry for the content feature vocabulary.
Internet-Drafts are available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A URL for the Internet-Draft is:
Internet-Drafts directories are located at:
Pacific Rim: munnari.oz.au
US East Coast: ftp.ietf.org
US West Coast: ftp.isi.edu
Internet-Drafts are also available by mail.
Send a message to: mailserv@xxxxxxxxx In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the