Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo

koen@win.tue.nl (Koen Holtman) wrote:
>Yaron Goland:
>>
>[...]
>>BTW I find it strange that we are pushing a draft to proposed standard
>>when no one has implemented it and, in so far as I am aware, is even
>>planning on implementing it.
>
>A proposed standard does not require existing or planned
>implementations.
>
>I am not aware of anybody planning to implement hit metering either,
>and that is going to be a proposed standard too.
>
>For a proposed standard, the only thing required is that the WG thinks
>it is a good idea.  If you were to argue this WG as a whole has no
>consensus on state-man-mec being a good idea, you would have a very
>valid point.
>
>Though I have no objections to this thing being submitted as a
>proposed standard, I think that submission as `an experimental RFC
>which supersedes 2109' would better reflect the WG status.
>
>Not submitting it at all would mean not fixing the bugs in 2109, which
>is not an acceptable option as far as I am concerned.

	The revision has been implemented in Lynx, and is undergoing
field testing, with no problems so far.  Most of the changes relative
to the current RFC where made to accomodate MSIE, and the draft does
so, fully now, within the context of valid concerns about user privacy
and not just those of market forces.  Just as no one should expect
to be believed simply on the basis of where he is employed, rather
than on the basis of the credibility he establishes over time, no one
should assume to have a crystal ball concerning what will or will not
be implemented.

	I agree that it should be moved on to Experimental RFC which
supersedes RFC 2109 (and that most of the time most of the options
to disable this or that aspect of cookie handling should be used,
just as BLINK should be disabled :).

				Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 MACRIDES@SCI.WFBR.EDU         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================

Received on Thursday, 10 July 1997 16:58:52 UTC