- From: Jim Gettys <jg@zorch.w3.org>
- Date: Thu, 22 May 1997 15:35:05 -0400
- To: www-amaya@w3.org
- Cc: jg@pa.dec.com
Here's my notes from a quick attempt to use amaya; amaya doesn't seem
to be up to dealing with the table in this document, so I'll have to
go back to something else.
o Amaya added the following unsolicited to head. If defaults are sensible,
should not add. Bytes in the <head> are the most expensive in the document.
<style>
A:link { color : #0000FF }
A:visited { color : #7F007F }
</style>
o Should remove silly meta tags from braindead editors. Those bytes in
the first packet of a HTML document are precious, and wasted.
o Would be nice if amaya removed stupid 's at end of lines that
various other editors (e.g. netscape) seem to add at the drop of a hat.
o When a menu is pulled down, the menu title becomes black.
o I had a structure view open, and was editing out some breaks and
trying to replace them with paragraphs, and core dumped.
Here's a stack trace.
zorch.w3.org % dbx /usr/local/Thot/osf1/bin/amaya core
dbx version 3.11.10
Type 'help' for help.
Core file created by program "amaya"
signal Segmentation fault at [SplitTextElement:5 +0x328,0x120150e78] Source not available
(dbx) where
> 0 SplitTextElement() ["/tahiti/diffusion/opera/thotlib/content/content.c":5, 0x120150e78]
1 BreakElement() ["/tahiti/diffusion/opera/thotlib/editing/structmodif.c":5, 0x12014fe7c]
2 TtcCreateElement() ["/tahiti/diffusion/opera/thotlib/editing/unstructchange.c":5, 0x1200e0358]
3 ThotInput() ["/tahiti/diffusion/opera/thotlib/dialogue/input.c":5, 0x120178bf0]
4 XCharTranslation() ["/tahiti/diffusion/opera/thotlib/dialogue/input.c":5, 0x1201785cc]
5 FrameCallback() ["/tahiti/diffusion/opera/thotlib/dialogue/appli.c":5, 0x1200fe1a8]
6 TtaHandleOneEvent() ["/tahiti/diffusion/opera/thotlib/dialogue/interface.c":5, 0x1200fc75c]
7 TtaMainLoop() ["/tahiti/diffusion/opera/thotlib/dialogue/interface.c":5, 0x1200fc8cc]
8 main() ["/tahiti/diffusion/opera/osf1/amaya/EDITORAPP.c":5, 0x12003e520]
(dbx)
o I found that Netscape ends up putting lots of multiple <br>'s, where I had
meant for paragraphs.... I cleaned these up using the structure view,
which I find very nice.
o sometimes the menu's go completely invisible (i.e. text foreground
color becomes the same as background color. This makes Amaya unusable.
o highlighted text is almost invisible on my display; I get a blue against
bluegreen background.
o I can't figure out from the UI how to center some text (in this case,
a <h3></h3>
o the table layout is pretty hopeless.... I've looked at the HTML
(not that I'm a table wizard), and don't see anything wrong, but
amaya is squishing a number of columns; I get the same behavior on
my alpha and on a Sun using my Alpha for its display.
The behavior is so wrong I'll have to use some other editor.
But amaya shows some promise....
Appended is the HTML of the file I'm editing.
- Regards,
Jim Gettys
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<style>
A:link { color : #0000FF }
A:visited { color : #7F007F }
</style>
<title>
Overview2</title>
</head>
<body bgcolor="#FFFFFF" link="#0000FF" vlink="#800080">
<p>
<a href="../../../"><img src="w3c_home" alt="W3C" border="0" height="48"
width="72"></a><a href="../../"><img src="HTTP48x" alt="HTTP" border="0"
height="48" width="48"></a><a href="http://www.ietf.org"></a> <a
href="http://www.ietf.org"><img src="ietf-130.gif" alt="IETF HTTP Working
Group" height="82" width="136"></a><br>
</p>
<h1 align=center>HTTP/1.1 Draft Standard Issues List</h1>
<p>
</p>
<hr>
During implementaton of the HTTP/1.1 Proposed Standard, a number of issues
have been raised that need to be addressed before the HTTP/1.1 is moved to
Draft Standard (the next phase of the IETF standardization process). Note that
at this time we are not suggesting how these issues are resolved, and
procedurally, the issues will be resolved in a number of different ways,
depending upon the severity of the problem and how it interacts with <a
href="http://www.ietf.org/structure.html">IETF process</a>.
<p>
The following is a list of these issues, and proposed solutions.</p>
<h2>For HTTP-WG use only</h2>
<p>
Please note: this list is an internal working document of the IETF HTTP-WG.
Please do not distribute, publish, or quote.</p>
<p>
Last update $Id: Overview.html,v 1.8 1997/04/04 20:13:45 frystyk Exp $ Updated
to reorganize list.</p>
<h2>Issue Status</h2>
<p>
This is a list of issues. If you think the summary is wrong in any of these
instances, please send mail to <a href="mailto:jg@w3.org">Jim Gettys</a>, or,
if you really think you have a new issue, please send mail to <a
href="mailto:http-wg@cuckoo.hpl.hp.com">the http working group</a>.</p>
<p>
If there's an open issue or something is wrong, please speak up.</p>
<p>
The comments are based on the HTTP/1.1 Proposed Standard (RFC 2068).</p>
<p>
When referring to issues on the list, it helps the editor if you put the issue
name into the subject line of any mail messages.</p>
<p>
The list below also needs to be organized into some sort of priority list. Due
to the April Fool's blizzard, this won't happen until after the IETFmeeting.
You can presume, though, that if an ID is associated with an issue, it is
relatively important (but the lack of an ID does not mean that the issue is
unimportant).</p>
<hr>
<h3>Links to Related Documents</h3>
<ul>
<li>
<a href="http://www.ics.uci.edu/pub/ietf/http/">HTTP Working Group Page</a>
<li>
<a href="http://www.w3.org/pub/WWW/Protocols/">W3C HTTP Page</a>
<li>
<a href="http://www.w3.org/pub/WWW/Protocols/Specs.html">Related HTTP
Specifications</a>
<li>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0039.html">Minutes
of Memphis IETF meeting (Ted Hardie)</a>
<li>
<a
href="http://www.w3.org/pub/WWW/Protocols/HTTP/Issues/http-wg.html">HTTP/1.1
Proposed Standard Issues List (historical)</a>
<li>
<a
href="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc2068.txt">HTTP/1.1
Proposed Standard Document</a>
<li>
<a
href="http://www.w3.org/pub/WWW/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-07.doc">HTTP/1.1
Proposed Standard Document (Postscript, of final Internet Draft)</a>
<li>
HTTP/1.1 Latest Internet Draft (placeholder, does not yet exist)
</ul>
Note: Some of the technical issues may really just be editorial problems; I
have tried to err on the conservative side until I have other opinions as to
if the issues are really of technical nature. The lists also need to be sorted
in some order of importance, though you can presume that if an issue has an ID
discussing it, the issue has been seen as of significant importance. The
<b>Status </b>field also needs to clarify what state discussions are actually
at. Open and Closed are the current states, but several intermediate states
need to be defined to reflect that consensus has been reached or concrete
wording proposed.
<h3>Technical Issues</h3>
<hr>
<table border="1" width="100%">
<tbody>
<tr>
<td><dl>
<dt><b>Name</b></dt>
</dl>
</td>
<td><dl>
<dt><b><span>Short Description</span></b></dt>
</dl>
</td>
<td><dl>
<dt><b>Resolution</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Status</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Raised By</b></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><b>Resp.</b></dt>
</dl>
</td>
</tr>
<tr>
<td>
COOKIE
</td>
<td>
Compatibility problem of RFC 2109
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:dmk@bell-labs.com">dmk</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td><dl>
<dt>DISPOSITION</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0048.html">Should
content-disposition from RFC 1806 be considered for HTTP? The same goes for
content-description (a.k.a. Title).</a></dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0151.html">Add
to</a></dt>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0151.html">Appendix</a></dt>
</dl>
</td>
<td><dl>
<dt>Drafting</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:masinter@parc.xerox.com">masinter</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:koen@win.tue.nl">koen</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CHUNKED</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0087.html">Chunked
encoding clarification</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Last Call</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:rlgray@raleigh.ibm.com">rlgray</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt>????</dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CACHING</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0004.html">Criticism
of HTTP/1.1 caching</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Last Call</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:dingle@ksvi.mff.cuni.cz">dingle</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>DATE_IF_MODIFIED</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0096.html">Date
string used in the If-modified-since header.</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:luotonen@netscape.com">luotonen</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>WARNINGS</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0113.html">Problems
with caching headers in Warnings</a> <a
href="ftp://ds.internic.net/internet-drafts/draft-ietf-http-warning-00.txt">(Internet
Draft)</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:luotonen@netscape.com">luotonen</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>VERSION</dt>
</dl>
</td>
<td><dl>
<dt>What version number should HTTP/1.1 servers return? <a
href="ftp://ietf.org/internet-drafts/draft-ietf-http-versions-00.txt">(Internet
Draft)</a> <a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0153.html">(Mailing
list discussion)</a> <a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0350.html">(more
discussion)</a></dt>
</dl>
</td>
<td><dl>
<dt>IESG action completed; awaiting RFC issue.</dt>
</dl>
</td>
<td><dl>
<dt>Closed</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:jcma@ai.mit.edu">jcma</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:mogul@pa.dec.com">mogul</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>PROXY-REDIRECT</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0323.html">Proxy
redirect (305) is at least vague, but more likely broken.</a><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0492.html">Working
list discussion.</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:josh@netscape.com">josh</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>PROXY-AUTH</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0387.html">Proposal
of Josh Cohen to modify Proxy authentication.</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Closed</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:josh@netscape.com">josh</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CLOSE</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0186.html">Who
should close the connection?<br>
</a><a
href="ftp://ietf.org/internet-drafts/draft-ietf-http-connection-00.txt">(Internet
Draft) </a>(<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0656.html">Mailing
List discussion</a>)</dt>
</dl>
</td>
<td><dl>
<dt>Draft should <br>
proceed independently.</dt>
</dl>
</td>
<td><dl>
<dt>Drafting</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:rbriscoe@jungle.bt.co.uk">briscoe</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:jg@w3.org">jg</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>PROXY-MAXAGE</dt>
</dl>
</td>
<td><dl>
<dt>Proposal to add a new ``proxy-maxage'' directive to deal with overlooked
cache case. <a
href="ftp://ds.internic.net/internet-drafts/draft-mogul-http-revalidate-00.txt">(Internet
Draft)</a> (<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0453.html">Mailing
List discussion</a>)</dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:mogul@pa.dec.com">mogul</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td>
PROXY-AUTHORIZATION
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0421.html">When
should Proxy-Authorization header be sent?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:dmk@bell-labs.com">dmk</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td><dl>
<dt>CHARSET-WILDCARD</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0049.html">Please
clarify * is legal in HTTP1/1 Accept-Charset Header.</a> <a
href="ftp://ds.internic.net/internet-drafts/draft-holtman-http-wildcards-00.txt">(Internet
Draft)</a></dt>
</dl>
</td>
<td><dl>
<dt>Fold into 1.1 spec.</dt>
</dl>
</td>
<td><dl>
<dt>Last Call</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:ftang@netscape.com">ftang</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>403VS404</dt>
</dl>
</td>
<td><dl>
<dt><a href="404vs403.txt">Current wording says: Description for "404 Not
found" says "403 Forbidden" can be used instead. As Ari Luotonen points out -
this should be the other way round.</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:luotonen@netscape.com">luotonen</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>STATUS100</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0194.html">Message
transmission requirements may need clarification.</a></dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0127.html">Fold
into 1.1 spec.</a></dt>
</dl>
</td>
<td><dl>
<dt>Drafting</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:rlgray@raleigh.ibm.com">rlgray</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:rlgray@raleigh.ibm.com">rlgray</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>AGE</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0285.html">Should
age be touched if a document is never resident in a cache?</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:fielding@liege.ICS.UCI.EDU">fielding</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>COMMENT</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0361.html">Quoting
confusion</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a
href="mailto:ulrich.windl@rrzc1.rz.uni-regensburg.de">ulrich.windl</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CACHING-CGI</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0363.html">Should
we add a note explaining how CGI can be cached?</a></dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0093.html">Fold
into 1.1 spec.</a></dt>
</dl>
</td>
<td><dl>
<dt>Drafting</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:mogul@pa.dec.com">mogul</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:mogul@pa.dec.com">mogul</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>PUT-RANGE</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0630.html">Do
Content-Range and PUT work together?</a></dt>
</dl>
</td>
<td><dl>
<dt>Eliminate PUT with byte ranges.</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:strachan@waterloo.hp.com">strachan</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:paulle@microsoft.com">paulle</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CONTENT-ENCODING</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0151.html">There
are problems in the Content-Encoding specification</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:mogul@pa.dec.com">mogul</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>RANGE-ERROR</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0101.html">What
should be the correct server response for a byte range that is outside the
actual contents of the file?</a></dt>
</dl>
</td>
<td><dl>
<dt>Fold into 1.1 spec.</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:matt@pointcast.com">matt</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt><a href="mailto:hardie@thornhill.arc.nasa.gov">hardie</a></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>WARNING-8859</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0413.html">Warnings,
and the use of 8859.</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:mduerst@ifi.unizh.ch">mduerst</a></dt>
</dl>
</td>
<td></td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td>
HOST
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0142.html">Where/when
should the host part of a URL be interpreted if not fully qualified?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:dahming.chiu@eng.sun.com">dahming.chiu</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
SHOULD-8859
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0197.html">Charset
confusion confusion.</a>
</td>
<td>
Add note to 1.1 spec.
</td>
<td>
Open
</td>
<td>
<a href="mailto:misha.wolf@reuters.com">misha.wolf</a>
</td>
<td></td>
<td>
<a href="mailto:masinter@parc.xerox.com">masinter</a>
</td>
</tr>
<tr>
<td>
CONTENT-LOCATION
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0236.html">Content-Location
needs minor clarification</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="../kweide@tezcat.com">kw</a><a
href="mailto:kweide@tezcat.com">e</a><a href="../kweide@tezcat.com">ide</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
AGE-CALCULATION
</td>
<td>
<a href="../age.txt">Conservative vs. Optimistic Age calculation, and
clarification.</a> <a
href="ftp://ds.internic.net/internet-drafts/draft-holtman-http-wildcards-00.txt">(Internet
Draft)</a><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0662.html">
(Dicussion)</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:fielding@liege.ICS.UCI.EDU">fielding</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
X-BYTERANGES
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0275.html">Need
note about x-byteranges in spec.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:akosut@nueva.pvt.k12.ca.us">akosut</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
FIN-WAIT-2
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0251.html">Is
there any problem in HTTP/1.1 causing fin-wait-2 problems, or is this strictly
a implementation bug (client, server, or TCP stack)?</a>
</td>
<td>
Implementation bug.
</td>
<td>
Closed
</td>
<td>
<a href="mailto:fielding@liege.ICS.UCI.EDU">fielding</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
PROXY-LENGTH
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0406.html">Proxies
should be able to add Content Length.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:dan@spyglass.com">dan</a>
</td>
<td></td>
<td>
<a href="mailto:paulle@microsoft.com">paulle</a>
</td>
</tr>
<tr>
<td>
PADDING
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0294.html">Should
padding rules be loosened in chunked encoding?</a>
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0040.html">Fold
into 1.1 spec</a>
</td>
<td>
Drafting
</td>
<td>
<a href="mailto:john@math.nwu.edu">john</a>
</td>
<td></td>
<td>
<a href="mailto:lawrence@agranat.com">lawrence</a>
</td>
</tr>
<tr>
<td>
CONNECTION
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0333.html">Should
spec be clarified around connection:Cache-Control? </a><a
href="connectionclarification.txt">Jeff Mogul's suggested resolution.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:urbani@ares.mctel.fr">urbani</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
AUTH-CHUNKED
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0347.html">Chunked
vs. Digest problem</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:lawrence@agranat.com">lawrence</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
RANGES
</td>
<td>
<a href="otherrange.txt">Might be nice to allow 206 response to range request
without knowing total content length.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:frystyk@w3.org">frystyk</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
QUOTED-BACK
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0361.html">Backslash
within quotes.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de">Ulrich.Windl</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
CLARIFY-NO-CACHE
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0039.html">Cache-Control:
No-cache needs clarification.</a> (<a href="jeff_nocache.html">Jeff's
mail</a>)
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:abaird@w3.org">abaird</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
QZERO
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0005.html">Quality
= 0.0.</a>
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0149.html">Fold
into 1.1 spec</a>
</td>
<td>
Drafting
</td>
<td>
<a href="mailto:gjw@wnetc.com">gjw</a>
</td>
<td></td>
<td>
<a href="mailto:koen@win.tue.nl">koen</a>
</td>
</tr>
<tr>
<td>
LANGUAGE-TAG
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0005.html">Language
tag matching needs to be added.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:gjw@wnetc.com">gjw</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
CACHE-CONTRA
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0004.html">Apparent
contradiction between 14.8 and 14.9.4.</a> <br>
<a href="maxageres.txt">Proposed resolution.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:koen@win.tue.nl">koen</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
CACHE-DIRECTIVE
</td>
<td>
<a href="cachedirective.txt">Need to either define field-name or change
grammar.</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:abaird@w3.org">abaird</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
REVALIDATE-REQUESTED
</td>
<td>
<a href="revalidaterequested.txt">Should there be a revalidate requested
code?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:kdyer@draper.com">kdyer</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
RETRY-AFTER
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0373.html">Should
Retry-After apply to:</a> <br>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0373.html">-
3xx Redirect class responses</a> <br>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0373.html">- as
well as 503 Service Unavailable</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:rbriscoe@jungle.bt.co.uk">briscoe</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
304-LAST-MODIFIED
</td>
<td>
<a href="lastmodified.txt">Should 304 include Last Modified?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:frystyk@w3.org">frystyk</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
BYTE-RANGE
</td>
<td>
<a href="byterange.txt">Is the right meta-data returned on range requests?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:frystyk@w3.org">frystyk</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
LWS-DELIMITER
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0131.html">Implied
LWS rule does not talk about LWS as delimiter between tokens, but as some 1.1
headers use LWS instead of tspecials as delimiters between tokens.</a>
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0147.html">Fold
into 1.1 spec.</a>
</td>
<td>
Open
</td>
<td>
<a href="koen@win.tue.nl">koen</a>
</td>
<td></td>
<td>
<a href="koen@win.tue.nl">koen</a>
</td>
</tr>
<tr>
<td>
CRLF
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0324.html">Is a
CRLF in a quoted-string legal, and what is the relation to header
continuation?</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="koen@win.tue.nl">koen</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
ACCEPT-ENCODING
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0176.html">Confusion
about accept-encoding language</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="koen@win.tue.nl">koen</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
MAX-AGE
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0650.html">Max-age
in responses not defined</a>
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:fielding@liege.ICS.UCI.EDU">fielding</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
VARY
</td>
<td>
Vary is really cache advice.
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:frystyk@w3.org">frystyk</a>
</td>
<td></td>
<td>
<a href="mailto:frystyk@w3.org">frystyk</a>
</td>
</tr>
<tr>
<td>
HIT-METER
</td>
<td>
Hit metering draft to go to RFC.
</td>
<td></td>
<td>
Last Call?
</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>
OPTIONS
</td>
<td>
Roy's Options neverousness...
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:fielding@liege.ICS.UCI.EDU">fielding</a>
</td>
<td></td>
<td></td>
</tr>
<tr>
<td>
IF-MODIFIED
</td>
<td>
Equality check for Date if Modified.
</td>
<td></td>
<td>
Open
</td>
<td>
<a href="mailto:josh@netscape.com">josh</a>
</td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
<p>
</p>
<table border="1" width="100%">
<caption><h3>Editorial Issues</h3>
</caption>
<tbody>
<tr>
<td><dl>
<dt><b>Name</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Short Description</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Resolution</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Status</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Raised By</b></dt>
</dl>
</td>
<td><dl>
<dt><b>Resp.</b></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>CLEANUP</dt>
</dl>
</td>
<td><dl>
<dt><a href="wordcleanup.txt">Clean up Microsoft Word document to make
generating HTML easier.</a></dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:rbriscoe@jungle.bt.co.uk">rbriscoe</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>ACCEPT-RANGES</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0300.html">Should
Accept-Ranges be listed in section 6.2 as a response
headerhttp://www.ics.uci.edu/pub/ietf/http/hypermail/1997q2/0127.html</a></dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:phethmon@utk.edu">phethmon</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>KEEP-ALIVE</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0182.html">Persist
connection token referred to.</a></dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:tromey@creche.cygnus.com">tromly</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>UTF-8</dt>
</dl>
</td>
<td><dl>
<dt><a href="ftp://ds.internic.net/rfc/rfc2044.txt">RFC for UTF-8 has
issued.</a> HTTP/1.1 should refer to this, and to IETF policy</dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>COOKIE</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0059.html">BNF
name is misleading.</a></dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:dmk@research.bell-labs.com">dmk</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td><dl>
<dt>KEYWORDS</dt>
</dl>
</td>
<td><dl>
<dt><a
href="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc2119.txt">Spec
should use Bradner's terms, and ref. them.</a></dt>
</dl>
</td>
<td><dl>
<dt>Editorial</dt>
</dl>
</td>
<td><dl>
<dt>Open</dt>
</dl>
</td>
<td><dl>
<dt><a href="mailto:jg@w3.org">jg</a></dt>
</dl>
</td>
<td><dl>
<dt></dt>
</dl>
</td>
</tr>
<tr>
<td>
RESPONSE-VERSION
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-versions-00.txt">Jeff
Mogul's I-D on response version should be folded into the spec.</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:masinter@parc.xerox.com">masinter</a>
</td>
<td></td>
</tr>
<tr>
<td>
URL-SYNTAX
</td>
<td>
Use the revised URL syntax draft rather than repeating this in HTTP
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:masinter@parc.xerox.com">masinter</a>
</td>
<td></td>
</tr>
<tr>
<td>
XREF
</td>
<td>
<a href="conings.txt">Nit in cross reference</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:richard.conings@mch.sni.edu">richard.conings</a>
</td>
<td></td>
</tr>
<tr>
<td>
COMMON-HEADERS
</td>
<td>
Spec should probably reference <a
href="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc2076.txt">RFC
2076</a>, "common internet mail headers"
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:jg@w3.org">jg</a>
</td>
<td></td>
</tr>
<tr>
<td>
ENTITY
</td>
<td>
Language around strong and weak validators talks about validators.
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:gjw@wnetc.com">gjw</a>
</td>
<td></td>
</tr>
<tr>
<td>
DOCKDIGEST
</td>
<td>
<a href="dockdigest.txt">Should we dock Digest authentication? Change section
2.1.3 that the AuthenticationInfo Header is allowed in the footer of a chunked
encoded HTTP message.</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:masinter@parc.xerox.com">masinter</a>
</td>
<td></td>
</tr>
<tr>
<td>
NO-CACHE
</td>
<td>
<a href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1996q4/0536.html">We
did not intend the "in that case".</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:abaird@w3.org">abaird</a>
</td>
<td></td>
</tr>
<tr>
<td>
FIX-REF
</td>
<td>
<a href="touch.html">Fix reference to persistent connections work</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:touch@isi.edu">touch</a>
</td>
<td></td>
</tr>
<tr>
<td>
PERSIST-CONFUSED
</td>
<td>
<a
href="http://www.ics.uci.edu/pub/ietf/http/hypermail/1997q1/0437.html">Clarify
distinction between origin and proxy server persistent connection
requirements.</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="bertold@tohotom.vein.hu">bertold</a>
</td>
<td></td>
</tr>
<tr>
<td>
CONNECTION2
</td>
<td>
<a href="connection2.html">Make implied connection requirement explicit.</a>
</td>
<td>
Editorial
</td>
<td>
Open
</td>
<td>
<a href="mailto:mogul@pa.dec.com">mogul</a>
</td>
<td></td>
</tr>
<tr>
<td>
REQUIREMENTS
</td>
<td>
Need table of requirements like RFC 1122 and 1123
</td>
<td>
Editoral
</td>
<td>
Open
</td>
<td>
all
</td>
<td></td>
</tr>
</tbody>
</table>
<p>
If you have comments or suggestions, email me at <i><a
href="mailto:jg@w3.org">jg@w3.org</a></i> <br>
<br>
</p>
<hr>
<address>
<a href="http://www.w3.org/pub/WWW/People/Gettys/">Jim Gettys</a></address>
<p>
<br>
<br>
@(#) $Id: Overview.html,v 1.8 1997/04/04 20:13:45 frystyk Exp $ <br>
</p>
</body>
</html>
Received on Thursday, 22 May 1997 21:34:12 UTC