RE: Update of CMS-X.400 Drafts

Russ Housley <housley@vigilsec.com> Mon, 18 August 2003 14:29 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20845 for <smime-archive@lists.ietf.org>; Mon, 18 Aug 2003 10:29:22 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7IDuNqt011471 for <ietf-smime-bks@above.proper.com>; Mon, 18 Aug 2003 06:56:23 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h7IDuNmh011470 for ietf-smime-bks; Mon, 18 Aug 2003 06:56:23 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [207.228.252.5]) by above.proper.com (8.12.9/8.12.8) with SMTP id h7IDuMqt011465 for <ietf-smime@imc.org>; Mon, 18 Aug 2003 06:56:22 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 7079 invoked by uid 0); 18 Aug 2003 13:56:20 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (141.156.214.239) by woodstock.binhost.com with SMTP; 18 Aug 2003 13:56:20 -0000
Message-Id: <5.2.0.9.2.20030818095449.02d59810@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 18 Aug 2003 09:56:02 -0400
To: "Bonatti, Chris" <BonattiC@ieca.com>, Francois.Rousseau@CSE-CST.GC.CA
From: Russ Housley <housley@vigilsec.com>
Subject: RE: Update of CMS-X.400 Drafts
Cc: ietf-smime@imc.org
In-Reply-To: <000301c36359$26561240$0300a8c0@ieca.com>
References: <7246F1C4915E1E4B874E62AE51E8F4F8902E5C@broadsword.its.cse.dnd.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>

Chris and Francois:

I would like to proceed with the specification "as is."  If we find that 
there is a lot of implementation, and those folks need compression, then we 
can revisit this issue.

Russ

At 02:15 PM 8/15/2003 -0400, Bonatti, Chris wrote:

>Francois,
>
>   This has not been discussed before on this list, but to my
>knowledge has there has not been a strong call for this.  My view
>is that this is feasible, but presently outside the scope of the
>draft.  Since this doesn't constitute a MUST in the 2633bis, I'm
>not sure this is significant.
>
>   I do not favor slowing down the spec for this.
>
>   Do others have opinions on this?
>
>Chris
>
>
>-----Original Message-----
>From: owner-ietf-smime@mail.imc.org
>[mailto:owner-ietf-smime@mail.imc.org] On Behalf Of
>Francois.Rousseau@CSE-CST.GC.CA
>Sent: Monday, August 11, 2003 13:16
>To: BonattiC@ieca.com
>Cc: ietf-smime@imc.org
>Subject: RE: Update of CMS-X.400 Drafts
>
>
>
>Hi Chris,
>
>I am very sorry to not have noticed this before, but I did not
>see any mention of optionally supporting Compression (i.e.
>RFC3274) under WRAP like under MSGbis.  Isn't compression
>something that could also be useful for X.400 content?  Was this
>intentional?
>
>Cheers,
>
>Francois
>
>
>-----Original Message-----
>From: Bonatti, Chris [mailto:BonattiC@ieca.com]
>Sent: Saturday, August 09, 2003 11:32 AM
>To: ietf-smime@imc.org
>Subject: Update of CMS-X.400 Drafts
>
>
>
>With Paul and Anders help, I have addressed some outstanding IESG
>(or
>AD) comments that I did not hear of until after the Vienna
>meeting.  The comments and their resolution are included below.
>I also updated WRAP so that it includes a specification of AES
>key sizes in alignment with the -05 issue of MSGbis.  This latter
>issue was mentioned in my status report in Vienna.
>
>So you should look for an -08 issue of WRAP and an -09 issue of
>TRANSPORT in the Internet-Drafts directory in short order (posted
>Friday AM).
>
>Cheers!
>Chris
>
>
>______WRAP COMMENTS________
>
>3.2----->"whatever gateway system that is bridging" seems
>grammatically wrong.
>
>Replaced with "any gateway system that might bridge the gap".
>
>
>3.2.1---->"since it is out" should be "since it is outside"?
>
>Done.
>
>
>3.3----->"If other binary transport" should "If another binary"?
>
>Replaced with "If other transport (e.g., X.400) that is optimized
>for binary content".  I think that's clearer.
>
>
>3.3.1------> "it is out" again, outside?
>
>Done.
>
>
>3.4.1---> "7-bit transport, is optional" spurious comma.
>
>Done.
>
>
>3.4.1--->"certs-only, which is only for signed)" seems to be
>missing a noun.
>
>Replaced with "certs-only, which applies only to signed-only
>messages)".
>
>
>
>______TRANSPORT COMMENTS________
>
>2.6.1--->"because those type do not" has subject/verb agreeement
>problem.
>
>Changed "type" to "types".
>
>
>2.6.2-----> "A RecipeintInfo" should be "RecipientInfo".
>
>Done.