Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id SAA19673; Thu, 20 Jul 2000 18:36:51 -0400 (EDT) Received: by cs.utk.edu (bulk_mailer v1.13); Thu, 20 Jul 2000 18:35:21 -0400 Received: by cs.utk.edu (cf v2.9s-UTK) id SAA19517; Thu, 20 Jul 2000 18:35:20 -0400 (EDT) Received: from windlord.stanford.edu (marvin@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id SAA19504; Thu, 20 Jul 2000 18:35:18 -0400 (EDT) Received: from windlord.stanford.edu (171.64.12.23 -> windlord.Stanford.EDU) by cs.utk.edu (smtpshim v1.0); Thu, 20 Jul 2000 18:35:18 -0400 Received: (qmail 14807 invoked by uid 50); 20 Jul 2000 22:35:16 -0000 To: drums@cs.utk.edu Subject: Re: SMTP WG Last-Call References: <4.3.2.20000720225612.00bc15f0@mail.bayarea.net> In-Reply-To: Dave Crocker's message of "Thu, 20 Jul 2000 22:59:16 +0900" From: Russ Allbery Organization: The Eyrie Date: 20 Jul 2000 15:35:16 -0700 Message-ID: Lines: 30 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Biscayne) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Unsubscribe: Dave Crocker writes: > two, yes. and a third has chimed in. Make it four on several of these points. > That is, working group consensus was consistently and massively against > those concerns. That is not in agreement with my reading of this working group for the time that I've been here. The working group consensus was consistently and massively against the way in which the concerns were presented, but I think some of these are good points, and do not have a consensus against them. I personally don't have an interest in belaboring these points further because I think at this stage it's considerably more important to the rest of the Internet to get an RFC *published* than to deal with these issues, which I think are by and large minor and can possibly be dealt with in a later revision. But I do feel like I have to chime in given the assertion that no one agreed with any of Dan's points. If someone wants to try to make minor revisions at this stage, Philip Hazel's summary is one that I also generally agree with. If the choice is to not do that due to how late this is in the process, I also agree with that. I've enough experience with IETF working groups to know that if the goal is to get the RFC perfect, there will never actually be an RFC. -- Russ Allbery (rra@stanford.edu)