source: wg_materials/shepherd_writeups/p1-messaging.txt @ 2719

Last change on this file since 2719 was 2423, checked in by mnot@…, 7 years ago

Oops

File size: 2.6 KB
Line 
11. Summary
2
3Document: draft-ietf-httpbis-p1-messaging-24
4Document Shepherd: Mark Nottingham
5Responsible Area Director: Barry Leiba
6Publication Type: Proposed Standard
7
8The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
9distributed, collaborative, hypertext information systems. HTTP has been in use
10by the World Wide Web global information initiative since 1990. This document
11provides an overview of HTTP architecture and its associated terminology,
12defines the "http" and "https" Uniform Resource Identifier (URI) schemes,
13defines the HTTP/1.1 message syntax and parsing requirements, and describes
14general security concerns for implementations.
15
16The Working Group has chosen Proposed Standard because this is a substantial
17revision of the text, compared to RFC2616. We anticipate moving to Internet
18Standard subsequently.
19
20Note that this document is part of a set, which should be reviewed together:
21
22* draft-ietf-httpbis-p1-messaging
23* draft-ietf-httpbis-p2-semantics
24* draft-ietf-httpbis-p4-conditional
25* draft-ietf-httpbis-p5-range
26* draft-ietf-httpbis-p6-cache
27* draft-ietf-httpbis-p7-auth
28* draft-ietf-httpbis-method-registrations
29* draft-ietf-httpbis-authscheme-registrations
30
31
322. Review and Consensus
33
34As chartered, this work was very constrained; the WG sought only to clarify
35RFC2616, making significant technical changes only where there were
36considerably interoperability or security issues.
37
38While the bulk of the work was done by a core team of editors, it has been
39reviewed by a substantial number of implementers, and design issues enjoyed
40input from many of them.
41
42It has been through two Working Group Last Calls, with multiple reviewers each
43time. We have also discussed this work with external groups (e.g., the W3C TAG).
44
45We were not able to get consensus on text to add regarding Security
46Considerations for interception of unencrypted HTTP traffic.
47
483. Intellectual Property
49
50There are no IPR disclosures against this document. The authors have confirmed
51that they have no direct, personal knowledge of IPR related to this document
52that has not been disclosed.
53
544. Other Points
55
56Downward references:
57* RFC1950
58* RFC1951 (already in downref registry)
59* RFC1952
60* "Welch"
61
62New registries created: None.
63
64Updated registries:
65
66* The Transfer Encoding Registry policy is changed from First Come First Served
67  to IETF Review, and registration procedures are now defined by this document.
68  The policy was changed to assure adequate review.
69
70* The Upgrade Token Registry policy remains at First Come First Served, but
71  registration procedures are now defined by this document.
72
Note: See TracBrowser for help on using the repository browser.