At 16:04 6/13/2001 -0700, Roy T. Fielding wrote:
But that doesn't answer my question. Are you planning on submitting
draft-elson-opes-icap-01.txt to the RFC editor as a representation of
the iCAP protocol?
From real world discussions at the workshop last week and elsewhere I'd
say the answer is a (very big) "no".
If you are, then please identify what versions of
what software have been implemented according to that specification, because
the last time I checked it was impossible for that specification to be
implemented as written.
What I am saying is: fix the specification first. I don't want you to
include all the wild ideas, just the fixes that make it possible for
independent interoperable implementations to exist based on the specification
and not based on reverse-engineering the behavior of your software.
This was discussed at the workshop last week. While the minutes haven't
been published yet (oops, probably my fault for not getting mine to Michael
until yesterday) my memory suggests that Alberto agreed to try to get the
new revision out - with the known bug fixes applied - sometime around the
end of this week.
(For what it's worth I think it would be useful to just publish that as a
new revision of the I-D and point folks to it once it's in the repository,
rather than email it to the list.)
After that we get to look at it and scream and shout again before trying to
get the *final* draft submitted prior to the IETF cutoff date. (Though I'd
suggest trying to do it a lot sooner than that if you want to get any IESG
time to review it. In fact, we're probably already too late for that to
happen prior to the next meeting.)