Re: Informational RFC to be: draft-adams-cmpaltcert-03.txt

The IESG <iesg-secretary@ietf.org> Fri, 09 April 2004 18:53 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12004 for <ietf-announce-archive@odin.ietf.org>; Fri, 9 Apr 2004 14:53:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC17w-0005oC-Ht for ietf-announce-archive@odin.ietf.org; Fri, 09 Apr 2004 14:53:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39IrKjb022292 for ietf-announce-archive@odin.ietf.org; Fri, 9 Apr 2004 14:53:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC13q-0004Yb-0B; Fri, 09 Apr 2004 14:49:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC0dD-0002Gc-Ry for ietf-announce@optimus.ietf.org; Fri, 09 Apr 2004 14:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10815 for <ietf-announce@ietf.org>; Fri, 9 Apr 2004 14:21:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC0dA-0001vE-00 for ietf-announce@ietf.org; Fri, 09 Apr 2004 14:21:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC0c7-0001nW-00 for ietf-announce@ietf.org; Fri, 09 Apr 2004 14:20:27 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BC0aK-0001aR-00; Fri, 09 Apr 2004 14:18:36 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BC0aI-000213-Rr; Fri, 09 Apr 2004 14:18:34 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, iana@iana.org
Subject: Re: Informational RFC to be: draft-adams-cmpaltcert-03.txt
Message-Id: <E1BC0aI-000213-Rr@optimus.ietf.org>
Date: Fri, 09 Apr 2004 14:18:34 -0400
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>

The IESG has no problem with the publication of 'Alternative Certificate 
Formats for the PKIX Certificate Management Protocols' 
<draft-adams-cmpaltcert-03.txt> as an Informational RFC. 

The IESG contact person is Russ Housley.


Thank you,

The IESG Secretary

Technical Summary

  The PKIX (Public Key Infrastructure using X.509) Working Group of the
  has defined a number of certificate management protocols.  These
  protocols are primarily focused on X.509v3 public key certificates.
  However, it is sometimes desirable to manage certificates in
  alternative formats as well.  This document specifies how such
  certificates may be requested using the CRMF (Certificate Request
  Message Format) syntax that is used by several different protocols.
  It also explains how alternative certificate formats may be
  incorporated into such popular protocols as PKIX-CMP (PKIX Certificate
  Management Protocol) and CMC (Certificate Management Messages over
  CMS).

End-run Check

  This document was reviewed by Russ Housley for the IESG.

IESG Note

  This document is not a candidate for any level of Internet
  Standard.  The IETF disclaims any knowledge of the fitness of this
  document for any purpose, and in particular notes that it has not
  had IETF review for such things as security, congestion control or
  inappropriate interaction with deployed protocols.  The RFC Editor
  has chosen to publish this document at its discretion.  Readers of
  this document should exercise caution in evaluating its value for
  implementation and deployment.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce