Re: [apps-discuss] Comments on Malformed Message BCP draft
Larry Masinter <masinter@adobe.com> Sat, 16 April 2011 01:46 UTC
Return-Path: <masinter@adobe.com>
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 8DD27E06A5 for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 18:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 aL9RptatMkCm for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 18:46:18 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfc.amsl.com (Postfix) with ESMTP id 56039E061E for <apps-discuss@ietf.org>; Fri, 15 Apr 2011 18:46:17 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKTaj03MC/vMcOqpTDzscDjweaM1c/8tM6@postini.com; Fri, 15 Apr 2011 18:46:18 PDT
Received: from inner-relay-4.eur.adobe.com (inner-relay-4.adobe.com [193.104.215.14]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id p3G1j9ES008437; Fri, 15 Apr 2011 18:45:10 -0700 (PDT)
Received: from nacas03.corp.adobe.com (nacas03.corp.adobe.com [10.8.189.121]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id p3G1jx1R029517; Fri, 15 Apr 2011 18:46:00 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas03.corp.adobe.com ([10.8.189.121]) with mapi; Fri, 15 Apr 2011 18:45:59 -0700
From: Larry Masinter <masinter@adobe.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri, 15 Apr 2011 18:45:57 -0700
Thread-Topic: [apps-discuss] Comments on Malformed Message BCP draft
Thread-Index: Acv7s7gPWXfDv5H3Sjii4WO/iHLk/wAB4aRwAAcDhhA=
Message-ID: <C68CB012D9182D408CED7B884F441D4D05A07766ED@nambxv01a.corp.adobe.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> <4DA8B7DD.3030909@gulbrandsen.priv.no> <F5833273385BB34F99288B3648C4F06F1343319E8B@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F1343319E8B@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C68CB012D9182D408CED7B884F441D4D05A07766EDnambxv01acorp_"
MIME-Version: 1.0
Cc: "ietf-822@imc.org" <ietf-822@imc.org>, "apps-discuss@ietf.org" <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
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: Sat, 16 Apr 2011 01:46:20 -0000
One might note that the same kind of difficult debate over 'error handling' has been at the root of much controversy in HTML land. Don't many MTAs actually implement the same "sniffing" for content-type and charset as is being proposed in http://tools.ietf.org/html/draft-ietf-websec-mime-sniff-02 It was my impression they did. Is "wrong content-type" a "malformed message"? Larry -- http://larry.masinter.net -----Original Message----- From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Murray S. Kucherawy Sent: Friday, April 15, 2011 3:21 PM To: Arnt Gulbrandsen Cc: ietf-822@imc.org; apps-discuss@ietf.org Subject: Re: [apps-discuss] Comments on Malformed Message BCP draft > -----Original Message----- > From: Arnt Gulbrandsen [mailto:arnt@gulbrandsen.priv.no] > Sent: Friday, April 15, 2011 2:26 PM > To: Murray S. Kucherawy > Cc: ietf-822@imc.org; apps-discuss@ietf.org > Subject: Re: [apps-discuss] Comments on Malformed Message BCP draft > > I found the advice rather naïve. Not bad, but also not very > sophisticated, and I fear that extending it to be comprehensive will not > produce a readable document. It's meant only as a starting point. And I think extending it, if done carefully, will produce something readable and valuable. > Still, I can see value in a document whose abstract says "here are some > of the bad things you must expect to receive, and not just from > spammers". Is that the goal of your draft? "...and what the consensus view is about what to do with them," precisely. _______________________________________________ apps-discuss mailing list apps-discuss@ietf.org<mailto:apps-discuss@ietf.org> https://www.ietf.org/mailman/listinfo/apps-discuss
- [apps-discuss] Comments on Malformed Message BCP … Simon Tyler
- Re: [apps-discuss] Comments on Malformed Message … Nathaniel Borenstein
- Re: [apps-discuss] Comments on Malformed Message … Alessandro Vesely
- Re: [apps-discuss] Comments on Malformed Message … Murray S. Kucherawy
- Re: [apps-discuss] Comments on Malformed Message … Dave CROCKER
- Re: [apps-discuss] Comments on Malformed Message … Dave Cridland
- Re: [apps-discuss] Comments on Malformed Message … Dave Cridland
- Re: [apps-discuss] Comments on Malformed Message … Dave CROCKER
- Re: [apps-discuss] Comments on Malformed Message … Simon Tyler
- Re: [apps-discuss] Comments on Malformed Message … Keith Moore
- Re: [apps-discuss] Comments on Malformed Message … Keith Moore
- Re: [apps-discuss] Comments on Malformed Message … Dave Cridland
- Re: [apps-discuss] Comments on Malformed Message … Murray S. Kucherawy
- Re: [apps-discuss] Comments on Malformed Message … Keith Moore
- Re: [apps-discuss] Comments on Malformed Message … Keith Moore
- Re: [apps-discuss] Comments on Malformed Message … J.D. Falk
- Re: [apps-discuss] Comments on Malformed Message … Arnt Gulbrandsen
- Re: [apps-discuss] Comments on Malformed Message … Murray S. Kucherawy
- Re: [apps-discuss] Comments on Malformed Message … Larry Masinter
- Re: [apps-discuss] Comments on Malformed Message … Nathaniel Borenstein
- Re: [apps-discuss] Comments on Malformed Message … Jaap Akkerhuis
- Re: [apps-discuss] Comments on Malformed Message … Keith Moore
- Re: [apps-discuss] Comments on Malformed Message … Peter Koch
- Re: [apps-discuss] Comments on Malformed Message … Tony Finch
- Re: [apps-discuss] Comments on Malformed Message … Eric Burger
- Re: [apps-discuss] Comments on Malformed Message … Tony Finch
- Re: [apps-discuss] Comments on Malformed Message … Tony Finch
- Re: [apps-discuss] Comments on Malformed Message … John C Klensin
- Re: [apps-discuss] Comments on Malformed Message … Ned Freed
- Re: [apps-discuss] Comments on Malformed Message … Tony Finch
- Re: [apps-discuss] Comments on Malformed Message … Douglas Otis
- Re: [apps-discuss] FW: Comments on Malformed Mess… Barry Leiba
- Re: [apps-discuss] FW: Comments on Malformed Mess… Murray S. Kucherawy