Re: RE: Security AD Review of draft-ietf-pkix-ipki3cmp-05.txt
Mike Smith <mfsmith@zionsbank.com> Tue, 11 November 1997 01:58 UTC
Return-Path: <mfsmith@zionsbank.com>
Received: from consensus.com (mail.consensus.com [157.22.240.7]) by sparky.wovenword.com (8.8.5/8.8.5) with ESMTP id RAA00678 for <tim-mail-work-lists@wovenword.com>; Mon, 10 Nov 1997 17:58:31 -0800
Received: from Tandem.com (192.216.221.8) by consensus.com with ESMTP (Eudora Internet Mail Server 1.2); Mon, 10 Nov 1997 17:54:45 -0700
Received: from ns1.austx.tandem.com (ns1.austx.tandem.com [131.124.253.5]) by Tandem.com (8.8.8/2.0.1) with ESMTP id PAA08149 for <ietf-pkix@tandem.com>; Mon, 10 Nov 1997 15:32:41 -0800 (PST)
Received: from zionsbank.com (mail.zionsbank.com [207.14.144.36]) by ns1.austx.tandem.com (8.8.6/8.8.0) with SMTP id RAA23796 for <ietf-pkix@tandem.com>; Mon, 10 Nov 1997 17:25:23 -0600 (CST)
Received: from ZionsData-Message_Server by zionsbank.com with Novell_GroupWise; Mon, 10 Nov 1997 16:30:07 -0700
Message-Id: <s467368f.092@zionsbank.com>
X-Mailer: Novell GroupWise 4.1
Date: Mon, 10 Nov 1997 16:29:47 -0700
From: Mike Smith <mfsmith@zionsbank.com>
To: kent@bbn.com, carlisle.adams@entrust.com, jis@mit.edu, stephen.farrell@sse.ie, wford@verisign.com
Cc: ietf-pkix@tandem.com
Subject: Re: RE: Security AD Review of draft-ietf-pkix-ipki3cmp-05.txt
Mime-Version: 1.0
Content-Type: text/plain
Content-Disposition: inline
Status:
A seaparate, standardized PKIX glossary would be wonderfully helpful - it gets my vote. michael >>> Carlisle Adams <carlisle.adams@entrust.com> 11/10/97 01:17PM >>> Hi Jeff, Thanks for the comments. I will issue a revised Internet Draft within the next couple of days. I have one slight counter-proposal, though. I wonder if you can give us your feedback on this: >---------- >From: Jeffrey I. Schiller[SMTP:jis@mit.edu] >Sent: Sunday, November 09, 1997 3:37 PM >To: Carlisle Adams; kent@bbn.com; wford@verisign.com; stephen.farrell@sse.ie >Cc: ietf-pkix@tandem.com >Subject: Security AD Review of draft-ietf-pkix-ipki3cmp-05.txt > >Part III Comments <draft-ietf-pkix-ipki3cmp-05.txt>: > >General: A Glossary would be a good idea, or a reference early in the >document to an introductory document that contains a glossary. I think that a glossary could usefully be included in this document. However, there is much overlap in terminology over the full set of PKIX documents, so that I'm not sure that including it in this particular document is the best course of action. My preference would be for the WG to produce a separate document (targeted as an Informational RFC) which serves as the "official" glossary for all other documents produced by the WG. This glossary can be updated as time goes on (if necessary), and all other PKIX RFCs and IDs can point to this as the agreed definition-of-terms for the Internet X.509 PKI. One negative consequence of the above suggestion is that the current Certificate Management Protocol spec. would have no glossary to point to (since it doesn't exist yet). On the positive side, there is no danger that PKIX-CMP would be held up for an indefinite amount of time if (for whatever reason) "discussion" develops over the precise definitions of some terms. Thoughts? -------------------------------------------- Carlisle Adams Entrust Technologies cadams@entrust.com -------------------------------------------- ! ! ! ! ! !
- FW: Security AD Review of draft-ietf-pkix-ipki3cm… Carlisle Adams
- Re: Security AD Review of draft-ietf-pkix-ipki3cm… Bob Jueneman
- RE: Security AD Review of draft-ietf-pkix-ipki3cm… Jeffrey I. Schiller
- Re: RE: Security AD Review of draft-ietf-pkix-ipk… Mike Smith
- RE: Security AD Review of draft-ietf-pkix-ipki3cm… Jeffrey I. Schiller
- RE: Security AD Review of draft-ietf-pkix-ipki3cm… Jeffrey I. Schiller
- RE: Security AD Review of draft-ietf-pkix-ipki3cm… Carlisle Adams
- Security AD Review of draft-ietf-pkix-ipki3cmp-05… Jeffrey I. Schiller