source: draft-ietf-httpbis/latest/auth48/rfc7232.abdiff.txt @ 2705

Last change on this file since 2705 was 2704, checked in by julian.reschke@…, 6 years ago

updated AUTH48 versions of RFC7231 and RFC7232 (#553)

  • Property svn:eol-style set to native
File size: 5.6 KB
Line 
1
2INTRODUCTION, paragraph 1:
3OLD:
4
5 HTTPbis Working Group                                   R. Fielding, Ed.
6 Internet-Draft                                                     Adobe
7 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
8 Intended status: Standards Track                              greenbytes
9 Expires: November 20, 2014                                  May 19, 2014
10
11NEW:
12
13 Internet Engineering Task Force (IETF)                  R. Fielding, Ed.
14 Request for Comments: 7232                                         Adobe
15 Obsoletes: 2616                                          J. Reschke, Ed.
16 Category: Standards Track                                     greenbytes
17 ISSN: 2070-1721                                                 May 2014
18
19
20INTRODUCTION, paragraph 2:
21OLD:
22
23       Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
24                 draft-ietf-httpbis-p4-conditional-latest
25
26NEW:
27
28       Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
29
30
31INTRODUCTION, paragraph 5:
32OLD:
33
34 Editorial Note (To be removed by RFC Editor)
35 
36    Discussion of this draft takes place on the HTTPBIS working group
37    mailing list (ietf-http-wg@w3.org), which is archived at
38    <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
39 
40    The current issues list is at
41    <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
42    documents (including fancy diffs) can be found at
43    <http://tools.ietf.org/wg/httpbis/>.
44 
45    _This is a temporary document for the purpose of tracking the
46    editorial changes made during the AUTH48 (RFC publication) phase._
47 
48 Status of This Memo
49
50NEW:
51
52 Status of This Memo
53
54
55INTRODUCTION, paragraph 6:
56OLD:
57
58    This Internet-Draft is submitted in full conformance with the
59    provisions of BCP 78 and BCP 79.
60
61NEW:
62
63    This is an Internet Standards Track document.
64
65
66INTRODUCTION, paragraph 7:
67OLD:
68
69    Internet-Drafts are working documents of the Internet Engineering
70    Task Force (IETF).  Note that other groups may also distribute
71    working documents as Internet-Drafts.  The list of current Internet-
72    Drafts is at http://datatracker.ietf.org/drafts/current/.
73
74NEW:
75
76    This document is a product of the Internet Engineering Task Force
77    (IETF).  It represents the consensus of the IETF community.  It has
78    received public review and has been approved for publication by the
79    Internet Engineering Steering Group (IESG).  Further information on
80    Internet Standards is available in Section 2 of RFC 5741.
81
82
83INTRODUCTION, paragraph 8:
84OLD:
85
86    Internet-Drafts are draft documents valid for a maximum of six months
87    and may be updated, replaced, or obsoleted by other documents at any
88    time.  It is inappropriate to use Internet-Drafts as reference
89    material or to cite them other than as "work in progress."
90    This Internet-Draft will expire on November 20, 2014.
91
92NEW:
93
94    Information about the current status of this document, any errata,
95    and how to provide feedback on it may be obtained at
96    http://www.rfc-editor.org/info/rfc7232.
97
98
99Section 10.1., paragraph 3:
100OLD:
101
102    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
103               Protocol (HTTP/1.1): Message Syntax and Routing",
104               draft-ietf-httpbis-p1-messaging-latest (work in progress),
105               May 2014.
106
107NEW:
108
109    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
110               Protocol (HTTP/1.1): Message Syntax and Routing",
111               RFC 7230, May 2014.
112
113
114Section 10.1., paragraph 4:
115OLD:
116
117    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
118               Protocol (HTTP/1.1): Semantics and Content",
119               draft-ietf-httpbis-p2-semantics-latest (work in progress),
120               May 2014.
121
122NEW:
123
124    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
125               Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
126               May 2014.
127
128
129Section 10.1., paragraph 5:
130OLD:
131
132    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
133               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
134               draft-ietf-httpbis-p5-range-latest (work in progress),
135               May 2014.
136
137NEW:
138
139    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
140               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
141               RFC 7233, May 2014.
142
143
144Section 10.1., paragraph 6:
145OLD:
146
147    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
148               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
149               draft-ietf-httpbis-p6-cache-latest (work in progress),
150               May 2014.
151
152NEW:
153
154    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
155               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
156               RFC 7234, May 2014.
157
158
159Appendix A., paragraph 2:
160OLD:
161
162    Weak entity-tags are now allowed in all requests except range
163    requests.  (Sections 2.1 and 3.2)
164    The ETag header field ABNF has been changed to not use quoted-string,
165    thus avoiding escaping issues.  (Section 2.3)
166 
167    ETag is defined to provide an entity tag for the selected
168    representation, thereby clarifying what it applies to in various
169    situations (such as a PUT response).  (Section 2.3)
170
171NEW:
172
173    Weak entity-tags are now allowed in all requests except range
174    requests.  (Sections 2.1 and 3.2)
175 
176    The ETag header field ABNF has been changed to not use quoted-string,
177    thus avoiding escaping issues.  (Section 2.3)
178    ETag is defined to provide an entity tag for the selected
179    representation, thereby clarifying what it applies to in various
180    situations (such as a PUT response).  (Section 2.3)
181
Note: See TracBrowser for help on using the repository browser.