Browse Prior Art Database

The Model Primary Content Type for Multipurpose Internet Mail Extensions (RFC2077)

IP.com Disclosure Number: IPCOM000002629D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 11 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Mitra: AUTHOR [+3]

Abstract

The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". RFC 2045 [1] describes mechanisms for specifying and describing the format of Internet Message Bodies via content-type/subtype pairs. We believe that "model" defines a fundamental type of content with unique presentational, hardware, and processing aspects. Various subtypes of this primary type are immediately anticipated but will be covered under separate documents.

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

Network Working Group S. Nelson

Request for Comments: 2077 LLNL

Category: Standards Track C. Parks

NIST

Mitra

WorldMaker

January 1997

The Model Primary Content Type for

Multipurpose Internet Mail Extensions

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.

Introduction

The purpose of this memo is to propose an update to Internet RFC 2045

to include a new primary content-type to be known as "model". RFC

2045 [1] describes mechanisms for specifying and describing the

format of Internet Message Bodies via content-type/subtype pairs. We

believe that "model" defines a fundamental type of content with

unique presentational, hardware, and processing aspects. Various

subtypes of this primary type are immediately anticipated but will be

covered under separate documents.

Table of Contents

1. Overview............................................. 2

2. Definition........................................... 2

3. Consultation Mechanisms.............................. 4

4. Encoding and Transport............................... 5

5. Security Considerations Section...................... 6

6. Authors' Addresses................................... 7

7. Expected subtypes.................................... 7

8. Appendix............................................. 9

9. Acknowledgements..................................... 13

1. Overview

This document will outline what a model is, show examples of models,

and discuss the benefits of grouping models together. This document

will not directly deal with the intended subtypes since those will be

covered by their separate registrations. Some immediately expected

subtypes are listed in section 7.

This document is a discussion document for an agreed definition,

intended eventually to form a standard accepted extension to RFC

2045. We are also targeting developers of input/output filters,

viewer software and hardwar...