Re: [yam] [secdir] secdir review of draft-ietf-yam-rfc1652bis-03

S Moonesamy <> Fri, 05 March 2010 14:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D19D528C1BE for <>; Fri, 5 Mar 2010 06:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=0.619, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0GhopmCWXCl7 for <>; Fri, 5 Mar 2010 06:41:53 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1A2D428C146 for <>; Fri, 5 Mar 2010 06:41:53 -0800 (PST)
Received: from ([]) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id o25Efl9V028482; Fri, 5 Mar 2010 06:41:52 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple;; s=mail; t=1267800114; x=1267886514; bh=2k/mpKjfFirFKBscfRmIMxWjz5w=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Rxa+9kZq3lQnBMY9c00J97tNof1EVf32a2eB0ccws5GQ9/uSzeL6VUowUZ3UbSo2a hQvpZXOBvJyLQ70RrBkfFa+hcsIw7L5Dfqr5LQ6owOqJEJ9Yxy+13yCuplUDK+b/rp A5fjzCM0w1qGKqcX1I5hzetbNZrrLzcijmjbq5ZI=
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version
Date: Fri, 05 Mar 2010 06:41:32 -0800
To: Alessandro Vesely <>
From: S Moonesamy <>
In-Reply-To: <>
References: <> <> <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [yam] [secdir] secdir review of draft-ietf-yam-rfc1652bis-03
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Mar 2010 14:41:54 -0000

Hi Alessandro,
At 03:38 05-03-10, Alessandro Vesely wrote:
>RFC 4871 is of 2007 and reports an issue with it. Section 5.3 
>practically says that 8bit SHOULD NOT be used. I'm not sure whether 
>this is a security consideration that would incarnate Stephen's 
>concern (also because, since the "relaxed" Header Canonicalization 
>Algorithm does not take into account quotes, /any/ rfc2045 extension 
>token breaks those signatures, not just 8BITMIME.)

Section 5.3 of RFC 4871 sounds more like a deployment consideration 
instead of a security consideration.

The question from Stephen Kent [1] in response to my comment mentions 
that "binary attachments that are ideal for delivering malware are 
supported irrespective of the use of" the 8BITMIME extension.  Dave 
Crocker requested input from the WG on the secdir review [2].  His 
message gives a broader view of the matter (i.e. whether the change 
is within scope for the YAM WG).  If you have any comments, I would 
like to hear them.  I am not saying this because it is required by 
the IETF Standards process; I mean it.  It is less work for me if 
such discussions do not diverge from the issue at hand.  My position 
is that an issue was brought up during the Secdir review and I need 
an answer for the Responsible Area Director and YAM WG Chairs.

I wrote some notes about hostile content ( temporary link 
).  It is not meant to be used as input for YAM WG work.

S. Moonesamy