Re: Final Last Last Last Last straw poll

New Message Reply About this list Date view Thread view Subject view Author view

From: Bruce Lilly (blilly@erols.com)
Date: Fri Sep 06 2002 - 17:36:34 CDT


> 1. [y/n] We've produced a great draft and have achieved
> "rough consensus" besides, so let's move on!
y, with a reservation re. mail incompatibility (details below)

> 2. [y/n] We've produced a reasonable draft and have
> achieved "rough consensus", so let's move on!
y, same reservation as above

> 3. [y/n] We've produced a lousy draft, but have nonetheless
> achieved "rough consensus" - or at least Mr.
> Lindsey says so, so let's move on!
n

> 4. [y/n] The draft isn't ready yet, and will never be, but
> I'm tired of all this, so let's move on; hopefully
> the IETF will stop it.
n
 
> 5. [y/n] The draft isn't ready yet, and will never be,
> but I'm tired of all this. Let's give up!
n
 
> 6. [y/n] The draft isn't ready yet, and will never be, but
> we might have a chance if we started from scratch.
n

> 7. [y/n] The draft can still be fixed, but needs more work.
> Yes, we're probably all tired of it, but that's
> not a reason to call it "complete".
y, but note that the "more work" can be minimal (change one
word)

> 8. [y/n] _see details below_____________
y

I'd prefer that the "SHOULD NOT" in 4.2.2 be changed to
"MUST NOT". [re. "parameters" for headers standardized
before the draft (I refer specifically to RFC 2822
headers Date, Message-ID, Keywords, Sender, and
References (and also implicitly any MIME headers which
do not permit parameters). Such parameters are illegal
in email, which is a problem under any of three
conditions:
1. post-and-mail
2. incoming gateways (from email), particularly in the
   case of moderated newsgroups
3. outgoing gateways (to email)

If 4.2.2 cannot be so changed, the issue needs to be
addressed in sections 5.1, 5.3, 6.2, 6.4, 6.9, 6.15,
6.21.1, 8.8.1, and 8.8.2. Obviously, a one word change
to 4.2.2 would be much simpler...

Aside from that issue, I have only one minor quibble
re. the use of "Content-Type" to mean "media type" (as
used in the MIME RFCs). I think the use of a header
field name (including capitalization and hyphenation)
to refer to something other than that specific header
may lead to confusion.

Other than that one important issue and one minor
quibble -- excellent.


New Message Reply About this list Date view Thread view Subject view Author view


This archive was generated by hypermail 2b29.