Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA15507; Mon, 27 May 1996 16:10:35 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.6); Mon, 27 May 1996 16:09:59 -0400 Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.111]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA15402; Mon, 27 May 1996 16:09:57 -0400 Message-Id: <199605272009.QAA15402@CS.UTK.EDU> To: drums@cs.utk.edu From: "Roger Fajman" Date: Mon, 27 May 1996 16:09:25 EDT Subject: Re: 821bis outstanding issues list > > I think it's a good idea to mention this as a possible option in the > > security consideration section, but I don't think it's a good idea to > > define exactly how this feature should work, or to make any statement > > that requires it. > > I concur. While it appears that such a feature will be increasingly > desirable in the future, I don't think we have sufficient experience > to dictate how it should work. In particular, I fear that any strong > requriement to implement such a facility would cause a degradation > of reliability of Internet mail due to mis-configurations. We already > have enough problems due to DNS and mail-routing errors. > > Keith I agree that a mention as a possible option in the security considerations section is the right way to handle this. I do think that an example of how it might be implemented would be a reasonable thing to have. It would be just an example, not a requirement.