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

Sunday, 31 December 2006

Re: Large content size value Roy T. Fielding

Saturday, 30 December 2006

RE: Large content size value Travis Snoozy (Volt)
Re: Large content size value Jamie Lokier
RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Larry Masinter

Friday, 29 December 2006

RE: Large content size value Travis Snoozy (Volt)
Large content size value [was: RE: Use of 1*DIGIT David Morris
RE: Use of 1*DIGIT Travis Snoozy (Volt)
RE: Use of 1*DIGIT Travis Snoozy (Volt)
Re: Use of 1*DIGIT Justin Erenkrantz
RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Larry Masinter
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Henrik Nordstrom

Thursday, 28 December 2006

RE: RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Larry Masinter
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Joris Dobbelsteen

Wednesday, 27 December 2006

RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Joris Dobbelsteen

Friday, 22 December 2006

NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Travis Snoozy (Volt)
RE: Allow is not in 13.5.2 Travis Snoozy (Volt)
RE: Allow is not in 13.5.2 David Morris
RE: Allow is not in 13.5.2 Henrik Nordstrom
RE: Use of 1*DIGIT Travis Snoozy (Volt)
RE: Use of 1*DIGIT Travis Snoozy (Volt)
Re: Use of 1*DIGIT Roy T. Fielding

Thursday, 21 December 2006

RE: Use of 1*DIGIT Paul Leach
NEW ISSUE: Sort 1.3 Terminology Travis Snoozy (Volt)
RE: Allow is not in 13.5.2 Travis Snoozy (Volt)
Use of 1*DIGIT Travis Snoozy (Volt)
RE: Intent of 14.38 Server Paul Leach
RE: Intent of 14.38 Server Paul Leach
RE: Intent of 14.38 Server David Morris
RE: Intent of 14.38 Server Travis Snoozy (Volt)
Re: Allow is not in 13.5.2 Henrik Nordstrom
RE: Intent of 14.38 Server Henrik Nordstrom
Re: Allow is not in 13.5.2 Henrik Nordstrom
RE: Intent of 14.38 Server Paul Leach
RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Henrik Nordstrom
Allow is not in 13.5.2 Travis Snoozy (Volt)
Intent of 14.38 Server Travis Snoozy (Volt)
RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)

Wednesday, 20 December 2006

Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Roy T. Fielding
RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Henrik Nordstrom
RE: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Julian Reschke
Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Henrik Nordstrom
Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Julian Reschke
Re: NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Henrik Nordstrom

Tuesday, 19 December 2006

RE: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
Re: RFC 2616 Errata: Misc. Typos Julian Reschke
RE: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
RE: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
NEW ISSUE: date formats in BNF and spec text, was: RFC 2616 Errata: Misc. Typos Julian Reschke
Re: RFC 2616 Errata: Misc. Typos Julian Reschke
Re: RFC 2616 Errata: Misc. Typos Julian Reschke
RE: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
RE: Content-Location in Requests Henrik Nordstrom
Re: RFC 2616 Errata: Misc. Typos Henrik Nordstrom

Monday, 18 December 2006

RE: RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
RFC 2616 Errata: Misc. Typos Travis Snoozy (Volt)
RE: Content-Location in Requests Travis Snoozy (Volt)

Friday, 15 December 2006

Re: RFC 2616 Errata: 14.11 Content Encoding Julian Reschke
Re: NEW ISSUE: editorial bug in 13.5.1 Julian Reschke
Re: Content-Location in Requests Henrik Nordstrom

Thursday, 14 December 2006

Content-Location in Requests Travis Snoozy (Volt)
RFC 2616 Errata: 14.11 Content Encoding Travis Snoozy (Volt)
Re: NEW ISSUE: editorial bug in 13.5.1 Henrik Nordstrom
Re: NEW ISSUE: editorial bug in 13.5.1 Henrik Nordstrom

Wednesday, 13 December 2006

Re: NEW ISSUE: editorial bug in 13.5.1 Julian Reschke

Tuesday, 12 December 2006

Re: NEW ISSUE: editorial bug in 13.5.1 Jeffrey Mogul
NEW ISSUE: editorial bug in 13.5.1 Julian Reschke

Monday, 11 December 2006

[ietf-http-wg] <none> Henrik Nordstrom

Sunday, 10 December 2006

Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: Etag-on-write, draft -04 Henrik Nordstrom

Saturday, 9 December 2006

Re: Etag-on-write, draft -04 Roy T. Fielding
Re: Etag-on-write, draft -04 Lisa Dusseault

Tuesday, 5 December 2006

Re: RFC2616bis question: is the reference to RFC1123 normative? Alexey Melnikov
PATCH method Jan Algermissen
RFC2616bis question: is the reference to RFC1123 normative? Julian Reschke
RE: ERR header (NEW ISSUE: Drop Content-Location) Henrik Nordstrom

Monday, 4 December 2006

Re: NEW ISSUE: Drop Content-Location Roy T. Fielding
Re: NEW ISSUE: Drop Content-Location Mark Nottingham
Re: Etag-on-write, draft -04 Justin Erenkrantz
Re: Etag-on-write, draft -04 Justin Erenkrantz

Sunday, 3 December 2006

RE: ERR header (NEW ISSUE: Drop Content-Location) Joris Dobbelsteen
RE: Etag-on-write, draft -04 Larry Masinter
Re: ERR header (NEW ISSUE: Drop Content-Location) Henrik Nordstrom
Re: Etag-on-write, draft -04 Henrik Nordstrom
Re: Etag-on-write, draft -04 Julian Reschke
Re: Etag-on-write, draft -04 Julian Reschke
Re: ERR header (NEW ISSUE: Drop Content-Location) Julian Reschke
Re: ERR header (NEW ISSUE: Drop Content-Location) Henry Story
Re: Etag-on-write, draft -04 Jamie Lokier

Saturday, 2 December 2006

Re: ERR header (NEW ISSUE: Drop Content-Location) Henrik Nordstrom
Re: Etag-on-write, draft -04 Henrik Nordstrom
Re: Etag-on-write, draft -04 Julian Reschke
Re: ERR header (NEW ISSUE: Drop Content-Location) Henry Story
NEW ISSUE: example for matching functions, was: Weak and strong ETags Julian Reschke
Re: NEW ISSUE: Drop Content-Location Roy T. Fielding
Re: Etag-on-write, draft -04 Roy T. Fielding

Friday, 1 December 2006

Re: Weak and strong ETags Julian Reschke
Re: Weak and strong ETags Henrik Nordstrom
Re: Etag-on-write, draft -04 Wilfredo Sánchez Vega
Re: Etag-on-write, draft -04 Wilfredo Sánchez Vega
Re: Etag-on-write, draft -04 Wilfredo Sánchez Vega

Thursday, 30 November 2006

Re: NEW ISSUE: Drop Content-Location Mike Dierken
Re: Etag-on-write, draft -04 Roy T. Fielding
Re: NEW ISSUE: Drop Content-Location Yves Lafon
Re: NEW ISSUE: Drop Content-Location Yves Lafon
Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Julian Reschke
Re: NEW ISSUE: Drop Content-Location Anne van Kesteren
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: Etag-on-write, draft -04 Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Mark Baker
Re: Etag-on-write, draft -04 Wilfredo Sánchez Vega
Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Mark Nottingham
Re: NEW ISSUE: inconsistency in date format explanation Mark Nottingham
Re: NEW ISSUE: references to RFC1700 Mark Nottingham
Re: NEW ISSUE: classify RFC977 reference as "informative", and update to RFC3977 Mark Nottingham
Etag-on-write, draft -04 Wilfredo Sánchez Vega

Wednesday, 29 November 2006

Re: NEW ISSUE: Drop Content-Location Yngve N. Pettersen (Developer Opera Software ASA)
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
RE: ERR header (NEW ISSUE: Drop Content-Location) Joris Dobbelsteen
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Julian Reschke
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Yngve N. Pettersen (Developer Opera Software ASA)
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Julian Reschke
Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Ian Hickson
Re: NEW ISSUE: Drop Content-Location Julian Reschke
Re: Etag-on-write, 5th attempt (== IETF draft 04), was: I-D ACTION:draft-reschke-http-etag-on-write-04.txt Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Stefan Eissing
Re: NEW ISSUE: Drop Content-Location Henry Story
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Anne van Kesteren
Re: NEW ISSUE: Drop Content-Location Anne van Kesteren
Re: NEW ISSUE: Drop Content-Location Henrik Nordstrom
Re: NEW ISSUE: Drop Content-Location Anne van Kesteren
Re: NEW ISSUE: Drop Content-Location Roy T. Fielding
Re: NEW ISSUE: Drop Content-Location Julian Reschke
NEW ISSUE: Drop Content-Location Anne van Kesteren

Tuesday, 28 November 2006

Etag-on-write, 5th attempt (== IETF draft 04), was: I-D ACTION:draft-reschke-http-etag-on-write-04.txt Julian Reschke

Tuesday, 21 November 2006

Re: I-D ACTION:draft-lafon-rfc2616bis-02.txt Julian Reschke

Monday, 20 November 2006

NEW ISSUE: inconsistency in date format explanation Julian Reschke
NEW ISSUE: typo (?) in 14.18, rfc1123-format Julian Reschke

Tuesday, 14 November 2006

Re: Redirection after DELETE? Roy T. Fielding
Redirection after DELETE? Jan Algermissen

Sunday, 12 November 2006

Re: References style in draft-lafon-rfc2616bis Bjoern Hoehrmann
References style in draft-lafon-rfc2616bis Julian Reschke
NEW ISSUE: references to RFC1700 Julian Reschke

Friday, 10 November 2006

NEW ISSUE: classify RFC977 reference as "informative", and update to RFC3977 Julian Reschke

Tuesday, 7 November 2006

Monday, 6 November 2006

Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Helge Hess
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Justin Chapweske
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Wilfredo Sánchez Vega
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Helge Hess
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Wilfredo Sánchez Vega
Re: DELETE and ETag Wilfredo Sánchez Vega
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Stefan Eissing
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Wilfredo Sánchez Vega
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Roy T. Fielding

Sunday, 5 November 2006

Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Lisa Dusseault
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Robert Sayre
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Lisa Dusseault
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Lisa Dusseault
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Lisa Dusseault
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Lisa Dusseault
Re: security requirements Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Julian Reschke
Re: DELETE and ETag Mark Baker
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) William A. Rowe, Jr.
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach

Saturday, 4 November 2006

Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Wilfredo Sánchez Vega
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) David Morris
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) lists@ingostruck.de
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) David Morris
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) William A. Rowe, Jr.
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Stefan Eissing
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Lisa Dusseault
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements Lisa Dusseault
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Lisa Dusseault
DELETE and ETag Julian Reschke

Thursday, 2 November 2006

Re: unneeded references Mark Nottingham

Tuesday, 31 October 2006

NEW ISSUE: unneeded references Julian Reschke

Saturday, 28 October 2006

An RFC2616bis issues list Mark Nottingham

Friday, 27 October 2006

(HTTP Cookie) Domain structure/validation drafts released Yngve N. Pettersen (Developer Opera Software ASA)

Tuesday, 24 October 2006

Re: Revising RFC2616 - what's happening Julian Reschke

Monday, 23 October 2006

Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening David Morris
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Yves Lafon
Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt Julian Reschke

Sunday, 22 October 2006

Re: security requirements Henrik Nordstrom
Re: security requirements David Morris
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom

Friday, 20 October 2006

Re: security requirements Henrik Nordstrom

Sunday, 22 October 2006

Re: ETags vs Variants, was: Revising RFC2616 - what's happening Jamie Lokier

Saturday, 21 October 2006

Re: security requirements Ingo Struck
Re: Enforcement of specifications Etan Wexler
Re: Enforcement of specifications David Morris
Re: Reorganising RFC2616 [was: Revising RFC2616 - what's happening] Julian Reschke
Enforcement of specifications Etan Wexler

Friday, 20 October 2006

Re: Reorganising RFC2616 [was: Revising RFC2616 - what's happening] Roy T. Fielding
Re: security requirements Robert Sayre
Reorganising RFC2616 [was: Revising RFC2616 - what's happening] Mark Nottingham
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: security requirements Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Roy T. Fielding
Re: Revising RFC2616 - what's happening Roy T. Fielding
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: security requirements Ingo Struck
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Roy T. Fielding
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Roy T. Fielding
Re: security requirements Robert Sayre
RE: security requirements Paul Leach
RE: security requirements Paul Leach
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: security requirements Robert Sayre
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
RE: ETags vs Variants, was: Revising RFC2616 - what's happening Larry Masinter
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: security requirements Julian Reschke
Re: security requirements Stefan Eissing
RE: security requirements Paul Leach
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Henrik Nordstrom
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Julian Reschke
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre

Thursday, 19 October 2006

RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Larry Masinter

Friday, 20 October 2006

Re: Revising RFC2616 - what's happening Mark Nottingham
Re: Revising RFC2616 - what's happening Mark Nottingham

Thursday, 19 October 2006

Re: ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Wilfredo Sánchez Vega
Re: ETags vs Variants, was: Revising RFC2616 - what's happening Jamie Lokier
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Ingo Struck
Re: Revising RFC2616 - what's happening Bjoern Hoehrmann
Re: Revising RFC2616 - what's happening Julian Reschke
Re: Revising RFC2616 - what's happening Bjoern Hoehrmann
ETags vs Variants, was: Revising RFC2616 - what's happening Julian Reschke
Re: Revising RFC2616 - what's happening Henrik Nordstrom
References in RFC2616, was: Revising RFC2616 - what's happening Julian Reschke
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Julian Reschke
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: Revising RFC2616 - what's happening Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Wilfredo Sánchez Vega

Wednesday, 18 October 2006

Fwd: I-D ACTION:draft-pettersen-cookie-v2-00.txt Yngve N. Pettersen (Developer Opera Software ASA)
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: Revising RFC2616 - what's happening Stefan Eissing
Revising RFC2616 - what's happening Mark Nottingham
Re: I-D ACTION:draft-lafon-rfc2616bis-00.txt Julian Reschke
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Henrik Nordstrom
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Ingo Struck
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Julian Reschke
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Collins
RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Paul Leach
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Roy T. Fielding
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) David Morris
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Bjoern Hoehrmann
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Bjoern Hoehrmann
Re: security requirements Robert Sayre

Tuesday, 17 October 2006

Re: security requirements Anne van Kesteren
security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8) Robert Sayre
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Lisa Dusseault
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Stefan Eissing
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Julian Reschke
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Julian Reschke
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Lisa Dusseault
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Mark Nottingham
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Julian Reschke
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Mark Nottingham
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Bjoern Hoehrmann
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Robert Sayre
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Mark Nottingham

Monday, 16 October 2006

Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Robert Sayre
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Lisa Dusseault
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Ingo Struck
Re: Response to appeal by Robert Sayre dated 2006-08-29 Robert Sayre
Re: Response to appeal by Robert Sayre dated 2006-08-29 Julian Reschke
Re: Response to appeal by Robert Sayre dated 2006-08-29 Julian Reschke
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Sylvain Hellegouarch
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Robert Sayre
Re: RFC2616 erratum "languagetag" Julian Reschke
Re: RFC2616 erratum "languagetag" Yves Lafon

Sunday, 15 October 2006

Re: RFC2616 erratum "languagetag" Anne van Kesteren
Re: RFC2616 erratum "languagetag" Julian Reschke
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Ingo Struck
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Adam Roach
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Robert Sayre
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Ingo Struck
Re: [Ietf-http-auth] Updating RFC 2617 (HTTP Digest) to use UTF-8 Robert Sayre

Saturday, 14 October 2006

Re: RFC2616 erratum "languagetag" Anne van Kesteren
RFC2616 erratum "languagetag" Julian Reschke

Thursday, 5 October 2006

Etag-on-write, 3rd attempt (== IETF draft 01), was: Etag-on-write, 2nd attempt (== IETF draft 01) Julian Reschke

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