Re: [apps-discuss] Comments on Malformed Message BCP draft

Dave CROCKER <dhc@dcrocker.net> Fri, 15 April 2011 16:48 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfc.amsl.com
Delivered-To: apps-discuss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 527A8130044 for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 09:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mM9G5CR081Dy for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 09:48:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id 02996130045 for <apps-discuss@ietf.org>; Fri, 15 Apr 2011 09:48:03 -0700 (PDT)
Received: from [192.168.1.5] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3FGlsZw017230 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2011 09:47:59 -0700
Message-ID: <4DA876B6.9050700@dcrocker.net>
Date: Fri, 15 Apr 2011 09:47:50 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F1343319E22@EXCH-C2.corp.cloudmark.com> <CEDB17EC-80CE-49B5-91C1-FBCB0449BBA5@network-heretics.com> <4DA8542F.9040003@tana.it> <F5833273385BB34F99288B3648C4F06F1343319E51@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F1343319E51@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 15 Apr 2011 09:48:00 -0700 (PDT)
Cc: ietf-822 <ietf-822@imc.org>, apps-discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Comments on Malformed Message BCP draft
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 16:48:08 -0000

On 4/15/2011 9:44 AM, Murray S. Kucherawy wrote:
> The intended status of this document doesn't give any kind of standard status to malformations.  It recommends the safest way of handling them if you're in an environment where you have to do so rather than simply rejecting them.  And the reality is that we (the industry) usually have to do that, so it seems like a good idea to share the collected wisdom about the best/safest way to do so.


Perhaps we need to add a new document classification, given this long-term need 
to acknowledge and deal with real-world operational pragmatics and the benefit 
of regularizing them:  Best Current Bad Practices

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net