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

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

updated AUTH48 version of RFC7234 (#553)

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