RE: Charter Revision

"Phillip M Hallam-Baker" <pbaker@verisign.com> Tue, 22 June 1999 16:19 UTC

Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07626 for <smime-archive@odin.ietf.org>; Tue, 22 Jun 1999 12:19:11 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id HAA04835 for ietf-smime-bks; Tue, 22 Jun 1999 07:53:26 -0700 (PDT)
Received: from caladan.verisign.com (caladan.verisign.com [205.180.232.21]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA04831 for <ietf-smime@imc.org>; Tue, 22 Jun 1999 07:53:25 -0700 (PDT)
Received: from mentat.verisign.com by caladan.verisign.com (8.8.5/BCH1.5) id HAA02469; Tue, 22 Jun 1999 07:54:50 -0700 (PDT)
Received: from pbaker-pc.verisign.com by mentat.verisign.com (8.8.5/BCH1.0) id HAA20425; Tue, 22 Jun 1999 07:55:50 -0700 (PDT)
From: Phillip M Hallam-Baker <pbaker@verisign.com>
To: "Pawling, John" <jsp@jgvandyke.com>, ietf-smime@imc.org
Subject: RE: Charter Revision
Date: Tue, 22 Jun 1999 10:57:21 -0400
Message-ID: <004f01bebcbf$8791b040$6e07a8c0@pbaker-pc.verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal
In-Reply-To: <33BD629222C0D211B6DB0060085ACF311DB448@WFHQEX03>
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

> 1) There is significant work being done in the ISO committees (i.e. FPDAM)
> that will impact the X.509 Attribute Certificate syntax.  
> Recommend that we
> add the following text to the charter: "CMS imports the Attribute
> Certificate syntax from X.509.  If the AC syntax is changed (as is
> expected), then CMS will be enhanced to import the revised syntax."

This is definitely NOT a topic for S/MIME.

In the first place CMS should be importing semantics from PKIX, not
X.509. S/MIME has not addressed PKI infrastructure issues up to this
point and I don't think it is a good time to start.

In the second place simply adding attribute certificates because they
have appeared in an ISO proposal seems a very bad plan. Lots of
ideas make it into ISO specifications that never make it into the
real world. 


The approach S/MIME should take is to look to see what _functionality_
it wants to add to S/MIME to solve _problems_. Simply adding technology
for the sake of it is a very bad move.

The proper place to address attribute certificates would be either
PKIX or more likely a new group focussed on some _use_ of attribute
certificates. I suspect however that a such a group would want to
consider other technologies as well (attributes stored in a
trusted directory, attributes embedded in an OCSP call, etc.).

		Phill