Re: draft-housley-binarytime-00.txt

Russ Housley <housley@vigilsec.com> Fri, 17 September 2004 18:46 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 OAA27021 for <smime-archive@lists.ietf.org>; Fri, 17 Sep 2004 14:46:51 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8HIWIoh092303; Fri, 17 Sep 2004 11:32:18 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8HIWHrE092302; Fri, 17 Sep 2004 11:32:17 -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 [144.202.240.3]) by above.proper.com (8.12.11/8.12.9) with SMTP id i8HIWGGm092295 for <ietf-smime@imc.org>; Fri, 17 Sep 2004 11:32:17 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 7180 invoked by uid 0); 17 Sep 2004 18:32:15 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (141.156.160.173) by woodstock.binhost.com with SMTP; 17 Sep 2004 18:32:15 -0000
Message-Id: <6.1.2.0.2.20040917143105.05d46c50@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Fri, 17 Sep 2004 14:32:14 -0400
To: pgut001@cs.auckland.ac.nz, Peter.Sylvester@EdelWeb.fr
From: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-binarytime-00.txt
Cc: ietf-smime@imc.org
In-Reply-To: <E1C8Lp3-0005jr-00@medusa01>
References: <6.1.2.0.2.20040917114319.05c44008@mail.binhost.com> <E1C8Lp3-0005jr-00@medusa01>
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>

Peter:

That was what draft -00 did.  I changed it based on feed back from Peter^2.

Russ

At 12:42 PM 9/17/2004, Peter Gutmann wrote:

>Russ Housley <housley@vigilsec.com> writes:
>
> >The application itself is not ready for release to the IETF, and it may 
> never
> >be released to the IETF.  However, please take a look at draft-housley-cms-
> >fw-wrap.  This has many properties in common with the application that 
> is not
> >yet ready for release.  Basically, a content type is defined, and the use of
> >CMS to protect that content type is specified.  S/MIME is not used, only 
> CMS.
>
>If it's meant for use in fw-wrap, couldn't it just be specified as an extra
>attribute in there, along with the other attributes that fw-wrap introduces?
>
>Peter.