Subject: Policy-Discussion
List archive
- From: SK <sk.list AT gmail.com>
- To: Policy-Discussion <cacert-policy AT lists.cacert.org>
- Subject: [CAcert-Policy] Thawte migration process in the policy?
- Date: Fri, 11 Mar 2005 10:13:54 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ak2iY2riiuUtUISK3/e6sPq84Dhrs1QMYiIb1sO4UmGfDSaRORq0oyek9jWnIHGpPnGCgjQ+5Hni2UUqT2jA+2FnwxHkd96geLUG+mwGr8ypVoRdH9zKeV6BAxJQTrKk2477NE0ZYXDms6q54YzZhA7EAkBC9D1bKQumGhhtewY=
- List-archive: <http://lists.cacert.org/cgi-bin/mailman/private/cacert-policy>
- List-id: Policy-Discussion <cacert-policy.lists.cacert.org>
Duane's recent email to the general mailing list reminded me that we
do not seem to have the process that is used to "inherit" Thawte
Notary mentioned anywhere in the polict draft.
Shouldn't this be included around section 5.2 "Precedural Controls"?
SK
- [CAcert-Policy] Thawte migration process in the policy?, SK, 03/11/2005
Archive powered by MHonArc 2.6.16.