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

An HTTP Extension Framework (RFC2774)

IP.com Disclosure Number: IPCOM000003372D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 15 page(s) / 37K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Nielsen: AUTHOR [+3]

Abstract

A wide range of applications have proposed various extensions of the HTTP protocol. Current efforts span an enormous range, including distributed authoring, collaboration, printing, and remote procedure call mechanisms. These HTTP extensions are not coordinated, since there has been no standard framework for defining extensions and thus, separation of concerns. This document describes a generic extension mechanism for HTTP, which is designed to address the tension between private agreement and public specification and to accommodate extension of applications using HTTP clients, servers, and proxies. The proposal associates each extension with a globally unique identifier, and uses HTTP header fields to carry the extension identifier and related information between the parties involved in the extended communication.

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

Network Working Group H. Nielsen

Request for Comments: 2774 P. Leach

Category: Experimental Microsoft

S. Lawrence

Agranat Systems

February 2000

An HTTP Extension Framework

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. It does not specify an Internet standard of any kind.

Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Copyright Notice

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

IESG Note

This document was originally requested for Proposed Standard status.

However, due to mixed reviews during Last Call and within the HTTP

working group, it is being published as an Experimental document.

This is not necessarily an indication of technical flaws in the

document; rather, there is a more general concern about whether this

document actually represents community consensus regarding the

evolution of HTTP. Additional study and discussion are needed before

this can be determined.

Note also that when HTTP is used as a substrate for other protocols,

it may be necessary or appropriate to use other extension mechanisms

in addition to, or instead of, those defined here. This document

should therefore not be taken as a blueprint for adding extensions to

HTTP, but it defines mechanisms that might be useful in such

circumstances.

Abstract

A wide range of applications have proposed various extensions of the

HTTP protocol. Current efforts span an enormous range, including

distributed authoring, collaboration, printing, and remote procedure

call mechanisms. These HTTP extensions are not coordinated, since

there has been no standard framework for defining extensions and

thus, separation of concerns. This document describes a generic

extension mechanism for HTTP, which is designed to address the

tension between private agreement and public specification and to

accommodate extension of applications using HTTP clients, servers,

and proxies. The proposal associates each extension with a globally

unique identifier, and uses HTTP header fields to carry the extension

identifier and related information between the parties involved in

the extended communication.

Table of Contents

1. Introduction ...............................................3

<...