ietf-http-wg@w3.org from October to December 2006 by author

Adam Roach

• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Sunday, 15 October)

Alexey Melnikov

• Re: RFC2616bis question: is the reference to RFC1123 normative? (Tuesday, 5 December)

Anne van Kesteren

• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: security requirements (Tuesday, 17 October)
• Re: RFC2616 erratum "languagetag" (Sunday, 15 October)
• Re: RFC2616 erratum "languagetag" (Saturday, 14 October)

Bjoern Hoehrmann

• Re: References style in draft-lafon-rfc2616bis (Sunday, 12 November)
• Re: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)

David Morris

• Large content size value [was: RE: Use of 1*DIGIT (Friday, 29 December)
• RE: Allow is not in 13.5.2 (Friday, 22 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 23 October)
• Re: security requirements (Sunday, 22 October)
• Re: Enforcement of specifications (Saturday, 21 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)

Etan Wexler

• Re: Enforcement of specifications (Saturday, 21 October)
• Enforcement of specifications (Saturday, 21 October)

Helge Hess

• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Tuesday, 7 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 6 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 6 November)

Henrik Nordstrom

• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Friday, 29 December)
• RE: Allow is not in 13.5.2 (Friday, 22 December)
• Re: Allow is not in 13.5.2 (Thursday, 21 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• Re: Allow is not in 13.5.2 (Thursday, 21 December)
• RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Thursday, 21 December)
• RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• RE: Content-Location in Requests (Tuesday, 19 December)
• Re: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• Re: Content-Location in Requests (Friday, 15 December)
• Re: NEW ISSUE: editorial bug in 13.5.1 (Thursday, 14 December)
• Re: NEW ISSUE: editorial bug in 13.5.1 (Thursday, 14 December)
• [ietf-http-wg] <none> (Monday, 11 December)
• Re: NEW ISSUE: Drop Content-Location (Sunday, 10 December)
• Re: Etag-on-write, draft -04 (Sunday, 10 December)
• RE: ERR header (NEW ISSUE: Drop Content-Location) (Tuesday, 5 December)
• Re: ERR header (NEW ISSUE: Drop Content-Location) (Sunday, 3 December)
• Re: Etag-on-write, draft -04 (Sunday, 3 December)
• Re: ERR header (NEW ISSUE: Drop Content-Location) (Saturday, 2 December)
• Re: Etag-on-write, draft -04 (Saturday, 2 December)
• Re: Weak and strong ETags (Friday, 1 December)
• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)
• Re: Etag-on-write, draft -04 (Thursday, 30 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format (Wednesday, 29 November)
• Re: Etag-on-write, 5th attempt (== IETF draft 04), was: I-D ACTION:draft-reschke-http-etag-on-write-04.txt (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Tuesday, 7 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 6 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 23 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 23 October)
• Re: security requirements (Sunday, 22 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 22 October)
• Re: security requirements (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: security requirements (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)

Henry Story

• Re: ERR header (NEW ISSUE: Drop Content-Location) (Sunday, 3 December)
• Re: ERR header (NEW ISSUE: Drop Content-Location) (Saturday, 2 December)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)

Ian Hickson

• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)

Ingo Struck

• Re: security requirements (Saturday, 21 October)
• Re: security requirements (Friday, 20 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Monday, 16 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Sunday, 15 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Sunday, 15 October)

Jamie Lokier

• Re: Large content size value (Saturday, 30 December)
• Re: Etag-on-write, draft -04 (Sunday, 3 December)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 22 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Thursday, 19 October)

Jan Algermissen

• PATCH method (Tuesday, 5 December)
• Redirection after DELETE? (Tuesday, 14 November)

Jeffrey Mogul

• Re: NEW ISSUE: editorial bug in 13.5.1 (Tuesday, 12 December)

Joris Dobbelsteen

• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Thursday, 28 December)
• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Wednesday, 27 December)
• RE: ERR header (NEW ISSUE: Drop Content-Location) (Sunday, 3 December)
• RE: ERR header (NEW ISSUE: Drop Content-Location) (Wednesday, 29 November)

Julian Reschke

• Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• Re: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• Re: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• Re: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• Re: RFC 2616 Errata: 14.11 Content Encoding (Friday, 15 December)
• Re: NEW ISSUE: editorial bug in 13.5.1 (Friday, 15 December)
• Re: NEW ISSUE: editorial bug in 13.5.1 (Wednesday, 13 December)
• NEW ISSUE: editorial bug in 13.5.1 (Tuesday, 12 December)
• RFC2616bis question: is the reference to RFC1123 normative? (Tuesday, 5 December)
• Re: Etag-on-write, draft -04 (Sunday, 3 December)
• Re: Etag-on-write, draft -04 (Sunday, 3 December)
• Re: ERR header (NEW ISSUE: Drop Content-Location) (Sunday, 3 December)
• Re: Etag-on-write, draft -04 (Saturday, 2 December)
• NEW ISSUE: example for matching functions, was: Weak and strong ETags (Saturday, 2 December)
• Re: Weak and strong ETags (Friday, 1 December)
• Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format (Thursday, 30 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Etag-on-write, 5th attempt (== IETF draft 04), was: I-D ACTION:draft-reschke-http-etag-on-write-04.txt (Tuesday, 28 November)
• Re: I-D ACTION:draft-lafon-rfc2616bis-02.txt (Tuesday, 21 November)
• NEW ISSUE: inconsistency in date format explanation (Monday, 20 November)
• NEW ISSUE: typo (?) in 14.18, rfc1123-format (Monday, 20 November)
• References style in draft-lafon-rfc2616bis (Sunday, 12 November)
• NEW ISSUE: references to RFC1700 (Sunday, 12 November)
• NEW ISSUE: classify RFC977 reference as "informative", and update to RFC3977 (Friday, 10 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Tuesday, 7 November)
• Re: security requirements (Sunday, 5 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Sunday, 5 November)
• DELETE and ETag (Saturday, 4 November)
• NEW ISSUE: unneeded references (Tuesday, 31 October)
• Re: Revising RFC2616 - what's happening (Tuesday, 24 October)
• Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 23 October)
• Re: Reorganising RFC2616 [was: Revising RFC2616 - what's happening] (Saturday, 21 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: security requirements (Friday, 20 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: Revising RFC2616 - what's happening (Thursday, 19 October)
• ETags vs Variants, was: Revising RFC2616 - what's happening (Thursday, 19 October)
• References in RFC2616, was: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)
• Re: I-D ACTION:draft-lafon-rfc2616bis-00.txt (Wednesday, 18 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: Response to appeal by Robert Sayre dated 2006-08-29 (Monday, 16 October)
• Re: Response to appeal by Robert Sayre dated 2006-08-29 (Monday, 16 October)
• Re: RFC2616 erratum "languagetag" (Monday, 16 October)
• Re: RFC2616 erratum "languagetag" (Sunday, 15 October)
• RFC2616 erratum "languagetag" (Saturday, 14 October)
• Etag-on-write, 3rd attempt (== IETF draft 01), was: Etag-on-write, 2nd attempt (== IETF draft 01) (Thursday, 5 October)

Justin Chapweske

• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 6 November)

Justin Erenkrantz

• Re: Use of 1*DIGIT (Friday, 29 December)
• Re: Etag-on-write, draft -04 (Monday, 4 December)
• Re: Etag-on-write, draft -04 (Monday, 4 December)

Larry Masinter

• RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Saturday, 30 December)
• RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Friday, 29 December)
• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Thursday, 28 December)
• RE: Etag-on-write, draft -04 (Sunday, 3 December)
• RE: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)

Lisa Dusseault

• Re: Etag-on-write, draft -04 (Saturday, 9 December)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Saturday, 4 November)
• Re: security requirements (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Monday, 16 October)

lists@ingostruck.de

• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)

Mark Baker

• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)
• Re: DELETE and ETag (Sunday, 5 November)

Mark Nottingham

• Re: NEW ISSUE: Drop Content-Location (Monday, 4 December)
• Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format (Thursday, 30 November)
• Re: NEW ISSUE: inconsistency in date format explanation (Thursday, 30 November)
• Re: NEW ISSUE: references to RFC1700 (Thursday, 30 November)
• Re: NEW ISSUE: classify RFC977 reference as "informative", and update to RFC3977 (Thursday, 30 November)
• Re: unneeded references (Thursday, 2 November)
• An RFC2616bis issues list (Saturday, 28 October)
• Reorganising RFC2616 [was: Revising RFC2616 - what's happening] (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Friday, 20 October)
• Revising RFC2616 - what's happening (Wednesday, 18 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)

Mike Dierken

• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)

Paul Leach

• RE: Use of 1*DIGIT (Thursday, 21 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• RE: security requirements (Friday, 20 October)
• RE: security requirements (Friday, 20 October)
• RE: security requirements (Friday, 20 October)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)

Robert Collins

• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)

Robert Sayre

• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (Friday, 20 October)
• Re: security requirements (Friday, 20 October)
• Re: security requirements (Friday, 20 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)
• Re: security requirements (Wednesday, 18 October)
• security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Monday, 16 October)
• Re: Response to appeal by Robert Sayre dated 2006-08-29 (Monday, 16 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Monday, 16 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Sunday, 15 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Sunday, 15 October)

Roy T. Fielding

• Re: Large content size value (Sunday, 31 December)
• Re: Use of 1*DIGIT (Friday, 22 December)
• Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• Re: Etag-on-write, draft -04 (Saturday, 9 December)
• Re: NEW ISSUE: Drop Content-Location (Monday, 4 December)
• Re: NEW ISSUE: Drop Content-Location (Saturday, 2 December)
• Re: Etag-on-write, draft -04 (Saturday, 2 December)
• Re: Etag-on-write, draft -04 (Thursday, 30 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: Redirection after DELETE? (Tuesday, 14 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 6 November)
• Re: Reorganising RFC2616 [was: Revising RFC2616 - what's happening] (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Friday, 20 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Wednesday, 18 October)

Stefan Eissing

• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 6 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)
• Re: security requirements (Friday, 20 October)
• Re: Revising RFC2616 - what's happening (Wednesday, 18 October)
• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Tuesday, 17 October)

Sylvain Hellegouarch

• Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 (Monday, 16 October)

Travis Snoozy (Volt)

• RE: Large content size value (Saturday, 30 December)
• RE: Large content size value (Friday, 29 December)
• RE: Use of 1*DIGIT (Friday, 29 December)
• RE: Use of 1*DIGIT (Friday, 29 December)
• RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Friday, 29 December)
• RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Thursday, 28 December)
• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Thursday, 28 December)
• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Thursday, 28 December)
• RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Wednesday, 27 December)
• NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes (Friday, 22 December)
• RE: Allow is not in 13.5.2 (Friday, 22 December)
• RE: Use of 1*DIGIT (Friday, 22 December)
• RE: Use of 1*DIGIT (Friday, 22 December)
• NEW ISSUE: Sort 1.3 Terminology (Thursday, 21 December)
• RE: Allow is not in 13.5.2 (Thursday, 21 December)
• Use of 1*DIGIT (Thursday, 21 December)
• RE: Intent of 14.38 Server (Thursday, 21 December)
• Allow is not in 13.5.2 (Thursday, 21 December)
• Intent of 14.38 Server (Thursday, 21 December)
• RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Thursday, 21 December)
• RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos (Wednesday, 20 December)
• RE: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• RE: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• RE: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• RE: RFC 2616 Errata: Misc. Typos (Tuesday, 19 December)
• RE: RFC 2616 Errata: Misc. Typos (Monday, 18 December)
• RFC 2616 Errata: Misc. Typos (Monday, 18 December)
• RE: Content-Location in Requests (Monday, 18 December)
• Content-Location in Requests (Thursday, 14 December)
• RFC 2616 Errata: 14.11 Content Encoding (Thursday, 14 December)

Wilfredo Sánchez Vega

• Re: Etag-on-write, draft -04 (Friday, 1 December)
• Re: Etag-on-write, draft -04 (Friday, 1 December)
• Re: Etag-on-write, draft -04 (Friday, 1 December)
• Re: Etag-on-write, draft -04 (Thursday, 30 November)
• Etag-on-write, draft -04 (Thursday, 30 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Tuesday, 7 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 6 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 6 November)
• Re: DELETE and ETag (Monday, 6 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Monday, 6 November)
• Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt (Saturday, 4 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Thursday, 19 October)

William A. Rowe, Jr.

• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Sunday, 5 November)
• Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) (Saturday, 4 November)

Yngve N. Pettersen (Developer Opera Software ASA)

• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• Re: NEW ISSUE: Drop Content-Location (Wednesday, 29 November)
• (HTTP Cookie) Domain structure/validation drafts released (Friday, 27 October)
• Fwd: I-D ACTION:draft-pettersen-cookie-v2-00.txt (Wednesday, 18 October)

Yves Lafon

• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)
• Re: NEW ISSUE: Drop Content-Location (Thursday, 30 November)
• Re: ETags vs Variants, was: Revising RFC2616 - what's happening (Monday, 23 October)
• Re: RFC2616 erratum "languagetag" (Monday, 16 October)

Last message date: Sunday, 31 December 2006 04:53:10 UTC