home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
ietf
/
http
/
http-charter.txt
< prev
next >
Wrap
Text File
|
1997-10-29
|
9KB
|
205 lines
HyperText Transfer Protocol (http)
----------------------------------
Charter
Last Modified: 27-Oct-97
Current Status: Active Working Group
Chair(s):
Larry Masinter <masinter@parc.xerox.com>
Dave Raggett <dsr@w3.org>
Applications Area Director(s):
Keith Moore <moore+iesg@cs.utk.edu>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Applications Area Advisor:
Keith Moore <moore+iesg@cs.utk.edu>
Mailing Lists:
General Discussion:http-wg@cuckoo.hpl.hp.com
To Subscribe: http-wg-request@cuckoo.hpl.hp.com
In Body: subscribe http-wg Your Full Name
Archive: http://www.ics.uci.edu/pub/ietf/http/hypermail
Description of Working Group:
Note: This working group is jointly chartered by the Applications Area
and the Transport Services Area.
The HTTP Working Group will work on the specification of the Hypertext
Transfer Protocol (HTTP). HTTP is a data access protocol currently run
over TCP and is the basis of the World-Wide Web. The initial work will
be to document existing practice and short-term extensions. Subsequent
work will be to extend and revise the protocol. Directions which have
already been mentioned include:
o improved efficiency,
o extended operations,
o extended negotiation,
o richer metainformation, and
o ties with security protocols.
Note: the HTTP working group will not address HTTP security extensions
as these are expected to be the topic of another working group.
Background information
The initial specification of the HTTP protocol was kept in hypertext
form and a snapshot circulated as an Internet draft between 11/93 and
5/94. A revision of the specification by Berners-Lee, Fielding and
Frystyk Nielsen has been circulated as an Internet draft between 11/94
and 5/95. An overview of the state of the specifications and a
repository of pointers to HTTP resources may be found at
http://www.w3.org/hypertext/WWW/Protocols/Overview.html
Once established, the working group will expand and complete that
document to reflect HTTP/1.0 as it has been implemented by World-Wide
Web clients and servers prior to November 1994. The resulting
specification of HTTP/1.0 will be published for review as an
Internet-Draft and, if deemed appropriate, will be submitted to the
IESG for consideration as a Proposed Standard or Informational RFC.
In parallel with the above effort, the working group will consider
enhancements/restrictions to the current practice in order to form a
specification of the HTTP protocol suitable for eventual consideration
as a proposed standard.
Also in parallel with the above efforts, the working group will engage
in defining (or selecting from various definitions) a next-generation
protocol for hypertext transfer (HTTPng).
A description of HTTP/1.0 as it is generally practiced currently on the
Internet has been submitted to become an Informational RFC. The working
group is considering enhancements/restrictions to the current practice
in order to form a specification of the HTTP protocol suitable for
eventual consideration as a proposed standard.
Goals and Milestones:
Done Draft working group charter. Establish mailing list and
archive.
Done Review draft charter for discussion at the Chicago WWWF'94
conference. Invest an interim Chair for the working group.
Determine writing assignments for first draft of HTTP/1.0
document.
Done Publish an Internet-Draft on HTTP as reflected by current
practice (HTTP/1.0)
Done Meet at the San Jose IETF as a BOF. Review HTTP/1.0
Internet-Draft and decide whether it should be published as
Informational, should be a candidate for further working group
development, or should be allowed to expire. Determine writing
assignments for first drafts of the HTTP/1.1 or HTTPng
documents. Establish charter and submit to IESG
Done Revise the Internet-Draft on HTTP/1.0 and, if desired, submit
to the IESG for consideration under the category determined at
San Jose IETF.
Done Final review of HTTP/1.1 draft at the Danvers IETF. Revise
HTTP/1.1 draft and submit to IESG for consideration as Proposed
Standard. Review progress on HTTPng.
Done Final review of HTTPng draft at the Dallas IETF. Revise HTTPng
draft and submit to IESG for consideration as Proposed
Standard. Retrospective look at the activities of the HTTP WG.
Done Initial publication of HTTP/1.1 proposal from document editors.
Done Publish Internet-Drafts on HTTP/1.0
Done Complete review of HTTP/1.1 proposal and pending I-Ds by
subgroups: Persistent connections; cache-control and proxy
behavior; content negotiation; authentication;state
management;range retrievals; extension mechanisms; other new
methods and header features.
Apr 96 Submit HTTP/1.1 as Internet-Draft (editing team led by Jim
Gettys).
May 96 Submit HTTP/1.1 to IESG for consideration as a Proposed
Standard.
Jun 96 Review additional features for HTTP/1.2
Oct 96 Submit HTTP/1.2 to IESG for consideration as a Proposed
Standard.
Internet-Drafts:
Posted Revised I-D Title <Filename>
------ ------- ------------------------------------------
Nov 95 Jul 97 <draft-ietf-http-pep-04.txt, .ps>
PEP - an Extension Mechanism for HTTP
Feb 96 Sep 97 <draft-ietf-http-negotiation-04.txt>
Transparent Content Negotiation in HTTP
Oct 96 Jul 97 <draft-ietf-http-feature-reg-02.txt>
Feature Tag Registration Procedures
Feb 97 Jul 97 <draft-ietf-http-rvsa-v10-02.txt>
HTTP Remote Variant Selection Algorithm -- RVSA/1.0
Mar 97 New <draft-ietf-http-warning-00.txt>
Problem with HTTP/1.1 Warning header, and proposed fix
Mar 97 Sep 97 <draft-ietf-http-uahint-01.txt>
The User Agent Hint Response Header
Mar 97 Oct 97 <draft-ietf-http-state-man-mec-04.txt,.ps>
HTTP State Management Mechanism (Rev1)
Mar 97 New <draft-ietf-http-connection-00.txt>
HTTP Connection Management
May 97 Oct 97 <draft-ietf-http-jaye-trust-state-01.txt>
HTTP Trust Mechanism for State Management
Jun 97 Jul 97 <draft-ietf-http-negotiate-scenario-01.txt>
Scenarios for the Delivery of Negotiated Content using HTTP
Jun 97 New <draft-cohen-http-305-306-responses-00.txt>
HTTP/1.1 305 and 306 Response Codes
Jul 97 Jul 97 <draft-ietf-http-feature-scenarios-01.txt>
Feature Tag Scenarios
Jul 97 Aug 97 <draft-ietf-http-options-02.txt>
Specification of HTTP/1.1 OPTIONS messages
Jul 97 New <draft-ietf-http-digest-aa-rev-00.txt>
An Extension to HTTP : Digest Access Authentication
Sep 97 New <draft-ietf-http-req-sum-00.txt>
Format and Example of HTTP/1.1 Requirements Summary
Sep 97 New <draft-ietf-http-alternates-00.txt>
The Alternates Header Field
Oct 97 New <draft-ietf-http-v11-spec-rev-00.txt,.ps>
Hypertext Transfer Protocol -- HTTP/1.1
Request For Comments:
RFC Stat Published Title
------- -- ---------- -----------------------------------------
RFC1945 May 96 Hypertext Transfer Protocol -- HTTP/1.0
RFC2069 PS Jan 97 An Extension to HTTP: Digest Access Authentication
RFC2068 PS Jan 97 Hypertext Transfer Protocol -- HTTP/1.1
RFC2109 PS Feb 97 HTTP State Management Mechanism
RFC2145 May 97 Use and interpretation of HTTP version numbers
RFC2227 PS Oct 97 Simple Hit-Metering and Usage-Limiting for HTTP