RFC 4386 on Internet X.509 Public Key Infrastructure Repository Locator Service
rfc-editor@rfc-editor.org Sat, 04 February 2006 00:49 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5Bbr-0006Dq-ER; Fri, 03 Feb 2006 19:49:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5Bbl-0006BD-3r for ietf-announce@megatron.ietf.org; Fri, 03 Feb 2006 19:49:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07286 for <ietf-announce@ietf.org>; Fri, 3 Feb 2006 19:47:01 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5BnB-0008KZ-A2 for ietf-announce@ietf.org; Fri, 03 Feb 2006 20:00:45 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140mc55009835; Fri, 3 Feb 2006 16:48:38 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140mct6009834; Fri, 3 Feb 2006 16:48:38 -0800
Date: Fri, 03 Feb 2006 16:48:38 -0800
Message-Id: <200602040048.k140mct6009834@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1877e5cab490c097ed5f5a8a532c66ad"
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: ietf-pkix@imc.org, rfc-editor@rfc-editor.org
Subject: RFC 4386 on Internet X.509 Public Key Infrastructure Repository Locator Service
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4386
Title: Internet X.509 Public Key Infrastructure
Repository Locator Service
Author: S. Boeyen, P. Hallam-Baker
Status: Experimental
Date: February 2006
Mailbox: sharon.boeyen@entrust.com,
pbaker@VeriSign.com
Pages: 6
Characters: 11330
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pkix-pkixrep-04.txt
URL: http://www.rfc-editor.org/rfc/rfc4386.txt
This document defines a Public Key Infrastructure (PKI) repository
locator service. The service makes use of DNS SRV records defined in
accordance with RFC 2782. The service enables certificate-using
systems to locate PKI repositories.This memo defines an Experimental Protocol for the Internet community.
This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind. Discussion
and suggestions for improvement are requested. Distribution of this memo
is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
A new Request for Comments is now available in online RFC libraries.
RFC 4386
Title: Internet X.509 Public Key Infrastructure
Repository Locator Service
Author: S. Boeyen, P. Hallam-Baker
Status: Experimental
Date: February 2006
Mailbox: sharon.boeyen@entrust.com,
pbaker@VeriSign.com
Pages: 6
Characters: 11330
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pkix-pkixrep-04.txt
URL: http://www.rfc-editor.org/rfc/rfc4386.txt
This document defines a Public Key Infrastructure (PKI) repository
locator service. The service makes use of DNS SRV records defined in
accordance with RFC 2782. The service enables certificate-using
systems to locate PKI repositories.This memo defines an Experimental Protocol for the Internet community.
This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind. Discussion
and suggestions for improvement are requested. Distribution of this memo
is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce