HTTP/1.1 Draft Standard Issues List (from issues raised in IESG Last Call)

IESG last call of the specifications occurred in September 1998. The issues here all relate to issues raised during and after the IESG last call period.

For HTTP-WG use only

Issue Status

The comments are based on the Revision 4 of the HTTP/1.1 specification, and Auth-02 of HTTP Authentication.

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.

Links to Related Documents

• Old HTTP/1.1 Draft Standard Issues List (Before Last Call)
• Implementation Reports (Completion of an implementation report is required for Draft Standard)
• HTTP Working Group Pag
• W3C HTTP Page
• Related HTTP Specifications
• Minutes of Chicago IETF meeting
• HTTP/1.1 Proposed Standard Issues List (historical)
• HTTP/1.1 Draft Standard Issues List (before IETF last call; historical)
• HTTP/1.1 Proposed Standard Document
• HTTP/1.1 Proposed Standard Document (Postscript), gziped

HTTP/1.1 Internet Draft (rev-06), dated November 18, 1998.

• Rev-06 text format, gziped

• Rev-06 Word 97 format, gziped
• Rev-06 Postscript format, gziped
• Rev-05 to Rev-06 Word 97 format, gziped
  (Most useful to review changes from Rev05 to Rev06)

• Rev-05 to Rev-06 Postscript format, gziped
  (Changebars; useful for review if you don't have Word 97 available)

HTTP Authentication: Basic and Digest Access Authentication draft (Auth-03 issued September 11, 1998)

• Auth-03 text format

The Name field contains the name of the issue; and there are hypertext anchors present in this document of these names for each issue, to aid in cross referencing. We generally don't change the name or delete it once an issue has been opened.

The Short Description field contains a short description of the issue, often hyperlinked to a longer explanation of the issue.

The Status field can have the following values:

1. Open- the issue has been acknowledged to be a problem, but no definate solution proposed
2. Drafting- a solution is being drafted, and discussion is continuing in the mailing list
3. Ready for last call - a proposed resolution has been circulated, but the last call not yet issued
4. Last Call Issued- a last call for comments has been issued by the working group chair (Larry Masinter)
5. Closed - the issue is believed to be closed by the proposed resolution, and will be incorporated into the draft
6. Closed, no action needed -the issue is believed to be closed by the proposed resolution, and no action is needed.
7. In Rev XX - the closed issue has been edited and (will) appear(s) in draft XX of the specification (maybe with caveats).
8. Out of scope - this issue will not be addressed in the HTTP/1.1 specifications
9. Editorial- the issue does not involve technical problems with the specifications (beyond minor clarification)
10. RFC 2XXX -The issue has been dealt with independently of the HTTP/1.1 specification in the named document.
11. Subsumed By - the issue has been subsumed by a different issue (sometimes when disentangling an issue into its component issues, you find other issues that really are a symptom of a problem originally thought to be different)

The Raised By field contains a mailto: link to the name of the person who raised the issue initially.

The Resp. field contains a mailto: link to the name of the person responsible for drafting language to fix the issue, or responsible to see that action on the issue occurs.

Summary Of Issues in HTTP/1.1 and Authentication specifications.

One open Authentication technical issue: DOMAIN

0 open HTTP technical issues:

1 Closed HTTP editorial issue:

PUTREDIR

0 open HTTP editorial issues:

43 Closed HTTP editorial issues:

ROSS01, ROSS02, ROSS03, ROSS04 , ROSS05, ROSS06, ROSS07, ROSS08, ROSS09, ROSS10, ROSS11, ROSS12, ROSS13, ROSS14, ROSS15, ROSS16, ROSS17, ROSS18, ROSS19, ROSS20, ROSS21, ROSS22, ROSS23, ROSS24, LASTM, DMKULTRA, REF2183, FORUSE, TESWITCH, PROXYAUTH, WARNVAL, IMPLIEDLWS, ADAMS1, ADAMS2, ADAMS3, ADAMS28, ADAMS31, ADAMS41, ADAMS60, ADAMS84, ADAMS84b, ADAMS88, MORIGIN

The following issues (all resolved before IESG last call was issued) have been moved to a separate page to keep them clearly separate from items raised during IESG last call.

AUTH-PARAM, CHALLENGE-ORDER, DIGEST-URI, SNOOPED, REQUEST-DIGEST, CNONCE, NONCE-ETAG, DIGEST-MULTIPART, CHALLENGE-ORDER, AUTHVSPROXY, PROTECTION-SPACE, PROXY-AUTH, DMKAUTHNITS, COPYRIGHT, XREFS, CLEAN_INDEXES, PROXY-MAXAGE-TYPO, AUTHORS, REFERENCES, INTERNIC, MMS, EXPECT, TRANSFORMATIONS, CHUNKEDTRAILERS, TE-IDENTITY, PROXY-DNS, ERRORS, WARN-GEN, RANGEDELIM, IEBUG, MISTAKES, VERSION, EXPECT, CREATE, BENNETT, REFERENCES, NOTES, MMSCHECKTENIT, MISTAKES, DEPOSIT, ADVANTAGE, CONT, FLATTINNITS, TOKENS, INTERNIC, DMKNITS, LARRYENG, UNRECOGNISED, TSCHALAER, DATEWRONG, BNFNIT, REDIR, COPYRIGHT, WARN-GEN, TPROXY, PERSIST, 302FOUND, 202CAPS, 409CONFLICT, ARTG, RANGECONTRA, DMKNIT, RULE, POSTNIT, REVALIDATION, PROXY-MAXAGE-TYPO, AUTHORS, CHANGES

If you have comments or suggestions, email me at jg@w3.org