RE: Charter Revision
Carlisle Adams <carlisle.adams@entrust.com> Tue, 22 June 1999 18:26 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 OAA12121 for <smime-archive@odin.ietf.org>; Tue, 22 Jun 1999 14:26:49 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id KAA08593 for ietf-smime-bks; Tue, 22 Jun 1999 10:24:34 -0700 (PDT)
Received: from gatekeeper.entrust.com (gatekeeper.entrust.com [204.101.128.170]) by mail.proper.com (8.8.8/8.8.5) with SMTP id KAA08589 for <ietf-smime@imc.org>; Tue, 22 Jun 1999 10:24:33 -0700 (PDT)
Received: id NAA06782; Tue, 22 Jun 1999 13:23:18 -0400
Received: by gateway id <NL0CA6TP>; Tue, 22 Jun 1999 13:25:46 -0400
Message-ID: <01E1D01C12D7D211AFC70090273D20B104F147@sothmxs06.entrust.com>
From: Carlisle Adams <carlisle.adams@entrust.com>
To: "Pawling, John" <jsp@jgvandyke.com>, 'Phillip M Hallam-Baker' <pbaker@verisign.com>
Cc: ietf-smime@imc.org
Subject: RE: Charter Revision
Date: Tue, 22 Jun 1999 13:25:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
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>
Hi Phill, > ---------- > From: Phillip M Hallam-Baker[SMTP:pbaker@verisign.com] > Sent: Tuesday, June 22, 1999 10:57 AM > To: Pawling, John; ietf-smime@imc.org > Subject: RE: Charter Revision > > > 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. Fair enough. Note, however, that John did not suggest importing semantics from X.509; he suggested importing syntax from X.509, which is the correct thing to do. This should lead to no conflict with what PKIX is doing (recall what the "X" in PKIX stands for...). > 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. As John has pointed out, it has been envisioned from the start of the S/MIME Working Group that Attribute Certificates might be the technology that makes labeling of e-mail messages useful. So what you're asking for above may be precisely the reason that it is valuable to include the text that John suggested... Carlisle.
- Charter Revision Russ Housley
- RE: Charter Revision William Ottaway
- RE: Charter Revision Russ Housley
- Charter Revision Russ Housley
- RE: Charter Revision Pawling, John
- RE: Charter Revision Pawling, John
- RE: Charter Revision Phillip M Hallam-Baker
- RE: Charter Revision Carlisle Adams
- Re: Charter Revision Antonio MaƱa
- RE: Charter Revision Flanigan, Bill