Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A MIME Content-Type for Directory Information (RFC2425)

IP.com Disclosure Number: IPCOM000003002D
Original Publication Date: 1998-Sep-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 27 page(s) / 59K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Howes: AUTHOR [+3]

Abstract

This document defines a MIME Content-Type for holding directory information. The definition is independent of any particular directory service or protocol. The text/directory Content-Type is defined for holding a variety of directory information, for example, name, or email address, or logo. The text/directory Content-Type can also be used as the root body part in a multipart/related Content- Type for handling more complicated situations, especially those in which non-textual information that already has a natural MIME representation, for example, a photograph or sound, is to be represented.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group T. Howes

Request for Comments: 2425 M. Smith

Category: Standards Track Netscape Communications Corp.

F. Dawson

Lotus Development Corporation

September 1998

A MIME Content-Type for Directory Information

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

1. Abstract

This document defines a MIME Content-Type for holding directory

information. The definition is independent of any particular

directory service or protocol. The text/directory Content-Type is

defined for holding a variety of directory information, for example,

name, or email address, or logo. The text/directory Content-Type can

also be used as the root body part in a multipart/related Content-

Type for handling more complicated situations, especially those in

which non-textual information that already has a natural MIME

representation, for example, a photograph or sound, is to be

represented.

The text/directory Content-Type defines a general framework and

format for holding directory information in a simple "type:value"

form. We refer to "type" in this context meaning a property or

attribute with which the value is associated. Mechanisms are defined

to specify alternate languages, encodings and other meta-information.

This document also defines the procedure by which particular formats,

called profiles, for carrying application-specific information within

a text/directory Content-Type can be defined and registered, and the

conventions such formats must follow. It is expected that other

documents will be produced that define such formats for various

applications (e.g., white pages).

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].

2. Table of Contents

Status of the Memo................................................ 1

Copyright Notice.................................................. 1

1. Ab...