RFC 1123bis?

Hector Santos <hsantos@santronics.com> Sun, 01 February 2009 20:28 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n11KSXdH004492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Feb 2009 13:28:33 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n11KSXJr004491; Sun, 1 Feb 2009 13:28:33 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from winserver.com (news.winserver.com [208.247.131.9]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n11KSWKU004485 for <ietf-smtp@imc.org>; Sun, 1 Feb 2009 13:28:32 -0700 (MST) (envelope-from hsantos@santronics.com)
Received: by winserver.com (Wildcat! SMTP Router v6.3.452.5) for ietf-smtp@imc.org; Sun, 01 Feb 2009 15:29:11 -0500
Received: from hdev1 ([65.10.45.22]) by winserver.com (Wildcat! SMTP v6.3.452.5) with ESMTP id 3005973375; Sun, 01 Feb 2009 15:29:10 -0500
Message-ID: <498605E0.6080004@santronics.com>
Date: Sun, 01 Feb 2009 15:28:16 -0500
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: ietf-smtp@imc.org
Subject: RFC 1123bis?
References: <497DE492.4080506@pscs.co.uk> <497DED29.70402@att.com> <497ED420.30708@pscs.co.uk> <alpine.LSU.2.00.0901271403220.4546@hermes-2.csi.cam.ac.uk> <497F86CB.60904@att.com> <alpine.LSU.2.00.0901281434440.4546@hermes-2.csi.cam.ac.uk> <498088B8.9040404@pscs.co.uk> <alpine.LSU.2.00.0901291310080.4546@hermes-2.csi.cam.ac.uk> <4981C0D5.1010401@pscs.co.uk> <4981C6BD.2040900@att.com> <37F39FF37390694B69567838@PST.JCK.COM> <4981E1AB.9000002@att.com> <alpine.LSU.2.00.0901301832470.4795@hermes-2.csi.cam.ac.uk> <49835DE2.3030403@santronics.com> <alpine.LSU.2.00.0901312021190.14750@hermes-2.csi.cam.ac.uk> <4984C49C.5030401@santronics.com> <alpine.LSU.2.00.0902011706190.10756@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.0902011706190.10756@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

Tony Finch wrote:

>> If so, should this be stated in the revised text?
> 
> Not in 3207 - this requirement is inherited from 5321.

On a related, we desperately need another RFC 1123, the "holy bible" 
for Internet hosting as I called it. :-)

Something that puts it all together again.   I just find it funny how 
we can be at times so anal about the whys things are done, with 
partial references and presumptions of inherit understanding, yet, we 
end up revisiting, rewriting things when something occurs people 
worked hard to prevent.  I carry a favorite motto from my old High 
School English teacher, "Being specific is Terrific."   It has helped 
in all my writings, technical or otherwise.

Today, with SMTP and all the augmented extensions, etc, a consolidated 
technical summary guide is necessary.  Not everyone is as keen as 
others where they know every RFC nook and cranny, every twist and turn 
issues related to the email system.

Of course, the question can be asked, should a SMTP implementor, new 
or otherwise, but especially new, be aware of all encompassing 
details, every RFC, etc, related to SMTP before he even attempts to 
write a server or client?  Can 5321 alone do the job for a minimum 
design of standard server or client?

-- 
Sincerely

Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com