List Info

Thread: RFC 4387 on Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access




RFC 4387 on Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access
user name
2006-02-08 01:25:38
A new Request for Comments is now available in online RFC
libraries.

        
        RFC 4387

        Title:      Internet X.509 Public Key Infrastructure

                    Operational Protocols: Certificate Store
Access via 
                    HTTP 
        Author:     P. Gutmann,  Ed.
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    pgut001cs.auckland.ac.nz
        Pages:      25
        Characters: 63182
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-certstore-http-09.txt

        URL:        http://www.
rfc-editor.org/rfc/rfc4387.txt

The protocol conventions described in this document satisfy
some of the
operational requirements of the Internet Public Key
Infrastructure (PKI).
This document specifies the conventions for using the
Hypertext Transfer
Protocol (HTTP/HTTPS) as an interface mechanism to obtain
certificates and
certificate revocation lists (CRLs) from PKI repositories. 
Additional
mechanisms addressing PKIX operational requirements are
specified in
separate documents.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure
(X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet
standards track
protocol for the Internet community,and requests discussion
and suggestions for improvements.Please refer to the current
edition of
the Internet Official Protocol Standards (STD 1) for the 
standardization state and status of this protocol. 
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-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained
by sending
an EMAIL message to rfc-infoRFC-EDITOR.ORG with the
message body 

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-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-ManagerRFC-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-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...


--22b50466d5aa20ab9f92be34617c09da


A new Request for Comments is now available in online RFC
libraries.

        
        RFC 4387

        Title:      Internet X.509 Public Key Infrastructure

                    Operational Protocols: Certificate Store
Access via 
                    HTTP 
        Author:     P. Gutmann,  Ed.
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    pgut001cs.auckland.ac.nz
        Pages:      25
        Characters: 63182
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-certstore-http-09.txt

        URL:        http://www.
rfc-editor.org/rfc/rfc4387.txt

The protocol conventions described in this document satisfy
some of the
operational requirements of the Internet Public Key
Infrastructure (PKI).
This document specifies the conventions for using the
Hypertext Transfer
Protocol (HTTP/HTTPS) as an interface mechanism to obtain
certificates and
certificate revocation lists (CRLs) from PKI repositories. 
Additional
mechanisms addressing PKIX operational requirements are
specified in
separate documents.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure
(X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet
standards track
protocol for the Internet community,and requests discussion
and suggestions for improvements.Please refer to the current
edition of
the Internet Official Protocol Standards (STD 1) for the 
standardization state and status of this protocol. 
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-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained
by sending
an EMAIL message to rfc-infoRFC-EDITOR.ORG with the
message body 

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-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-ManagerRFC-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-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-distmailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
[1]

about | contact  Other archives ( Real Estate discussion Medical topics )