rfc1875.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 564 行 · 第 1/2 页

Network Working Group                                           N. Berge
Request for Comments: 1875                    Norwegian Computing Center
Category: Informational                                    December 1995


                     UNINETT PCA Policy Statements

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Table of Contents

   1.   Introduction.......................................2
   2.   PCA Identity.......................................2
   3.   UNINETT - a brief overview.........................2
   4.   PCA Scope..........................................2
   4.1  The certification tree.............................3
   4.2  Use of Registration Authorities (RAs)..............3
   5.   PCA Security & Privacy.............................3
   5.1  Security requirements imposed on the PCA...........3
   5.2  Security requirements imposed on CAs...............4
   5.3  Security requirements imposed on RAs...............4
   5.4  Measures taken to protect the privacy of any
        information collected in the course of certifying
        CAs and (for CAs) users............................4
   6.   Certification Policy...............................5
   6.1  Policy and procedures when certifying CAs..........5
   6.2  Policy and procedures when certifying RAs..........5
   6.3  Policy and procedures when certifying users........5
   6.4  Validity interval for issued certificates..........6
   6.5  The CAs right to a DN and procedures to resolve DN
        conflicts..........................................6
   6.6  The users right to a DN and procedures to resolve
        DN conflicts.......................................6
   7.   Certificate Management.............................7
   8.   CRL Management.....................................7
   9.   Naming Conventions.................................8
   10.  Business Issues....................................9
   10.1 Legal agreement concerning CAs.....................9
   10.2 Legal agreement concerning RAs.....................9
   10.3 Fees...............................................9
   11.  Other..............................................9
   11.1 Distribution of software needed by CAs, RAs and
        users..............................................9
   12.  Security Considerations............................9



Berge                        Informational                      [Page 1]

RFC 1875             UNINETT PCA Policy Statements         December 1995


   13.  References........................................10
   14.  Author's Address..................................10

1. Introduction

   This document provides information about policy statements submitted
   by the UNINETT Policy Certification Authority (UNINETT PCA).

   It's purpose is to provide information to members of the Internet
   community who wish to evaluate the trust they can place in a
   certification path that includes a certificate issued by the UNINETT
   PCA, or to set up a CA to be certified by the UNINETT PCA.

2. PCA Identity

   Distinguished Name (DN): C=no, O=uninett, OU=pca

   The UNINETT PCA will be run by:
   Norwegian Computing Center
   Gaustadallien 23
   P.O.Box 114 Blindern,
   N-0314 Oslo, Norway

   Contact person:
   Nils Harald Berge
   Email: [e-mail]
   Tel.: [phone]
   Fax : [phone]

   Duration: This policy is valid from Oct 1, 1995 to Jan 1, 1998

   Info about this PCA is available at: http://www.uninett.no/pca/

3. UNINETT - a brief overview

   UNINETT is a Limited Company (AS) operating the Norwegian network for
   academics and research. It is incorporated under Norwegian law, and
   it's company number is 968100211.

   More information is available from the UNINETT web server at:
   http://www.uninett.no/

4. PCA Scope

   The scope of the UNINETT PCA is determined by UNINETT Policy. It will
   chiefly certify CAs to run on behalf of legal entities such as
   schools and companies.




Berge                        Informational                      [Page 2]

RFC 1875             UNINETT PCA Policy Statements         December 1995


4.1 The certification tree

   The certification tree beneath the UNINETT PCA comprise three
   distinct entities: Certification Authorities (CAs), Registration
   Authorities (RAs) and users. CAs are described in the PEM documents
   [1,2,3,4]. An explanation of RAs is given bellow.

   There will be one CA, with possible sublevel CAs, per UNINETT member
   organization. The CA may be run by the organization itself, or by the
   organization running the PCA for organizations who do not want to
   take on the responsibility themselves.

4.2 Use of Registration Authorities (RAs)

   Since the CA may be located far away from the users, local
   authorities are needed for physical identification/authentication of
   users. For security reasons, and to avoid an unnecessary large number
   of CAs, these authorities are not allowed to issue certificates.

   A registration authority (RA) is an ordinary user, appointed by an
   organization or an organizational unit and trusted by a CA, serving
   as a point of contact for persons who want to register as users, i.e.
   to have a certificate issued. In order to avoid faked requests for
   certification, users must send their self-signed certificate to an
   appropriate RA, and then physically visit the RA with proof of
   identity. The RA will forward the self-signed certificate to the CA
   in a message signed by the RA, if the user is properly authenticated.

   For bulk certification (see 5.3) the RA must physically verify the
   identity of the user before giving out the password for access to the
   users private key.

   A CA may appoint as many RAs as it wish. The only difference between
   certifying an RA and an ordinary user is that the RA (a person) must
   sign an agreement with the certifying CA, stating the obligation to
   adhere to the agreed procedures.

5. PCA Security & Privacy

5.1 Security requirements imposed on the PCA

   - The PCA will have its private key stored on a smartcard.

   - The PCA will be run on a dedicated workstation with no network
     connection. The workstation will be physically secured.

   - Exchanging data between the PCA workstation and the rest of the
     world will be done by using tapes or floppy discs.



Berge                        Informational                      [Page 3]

RFC 1875             UNINETT PCA Policy Statements         December 1995


   - The PCA RSA key pair will have a length of 1024 bits.

   - Backups from the PCA workstation must be stored in at least one off
     site location. Backups must be physically secured

5.2 Security requirements imposed on CAs that are to be certified

   - A CA must be run on a dedicated workstation with no network
     connection. The workstation must be physically secured.

   - Exchanging data between the CA workstation and the rest of the world
     must be done by using tapes or floppy discs.

   - The CA RSA key pair must have a minimum length of 1024 bits.

   A security requirements document concerning CAs will be made
   available online, and expected to be obeyed.

5.3 Security requirements imposed on RAs that are to be certified

   - RAs must use a work station, with remote login disabled. Use of
     X-terminal, terminal emulator etc. with processes running on a
     remote machine is strictly prohibited.

   - The RA RSA key pair must have a minimum length of 512 bits.

   A security requirements document concerning RAs will be made
   available online, and expected to be obeyed.

5.4 Measures taken to protect the privacy of any information collected
    in the course of certifying CAs and (for CAs) users.

   CAs will not collect any security relevant information about users.
   In those cases when CAs generate keys (and certificates) on behalf of
   users, all information pertaining the users private key will be
   securely deleted after it has been received by the user.  CAs will
   always generate their own key pairs, thus no security relevant
   information will be collected by the PCA.

   All archived material concerning DNs for users will be stored on the
   CA workstations, which are physically protected and does not have any
   network connections.









Berge                        Informational                      [Page 4]

RFC 1875             UNINETT PCA Policy Statements         December 1995


6. Certification Policy

6.1 Policy and procedures when certifying CAs

   In order to be certified, a CA must sign an agreement with the
   UNINETT PCA stating the obligation to adhere to the agreed
   procedures.

   The persons responsible for running the CA will be evaluated by the
   UNINETT PCA, in order to determine whether they exhibit the necessary
   qualifications and have access to the resources needed in order to
   run the CA securely.

   The CA must submit its self signed certificate to the UNINETT PCA.

6.2 Policy and procedures when certifying RAs

   The organization or organizational unit is responsible for appointing
   RA persons, typically 1-3 persons per organization/unit. The person
   representing the RA must sign an agreement with the certifying CA,
   stating the obligation to adhere to the agreed procedures in order to
   be certified.

   The person representing the RA will be evaluated by the certifying
   CA, in order to determine whether he/she exhibits the necessary
   qualifications and has access to the resources needed to run the RA
   securely.

   The RA must submit its self signed certificate to the certifying CA.
   In the absence of RAs, or equivalent, the validity of the
   certification request (i.e. the identity of the requestor) must be
   verified by "out of band" means. These means will vary from case to
   case, depending on physical distance, prior knowledge etc.

6.3 Policy and procedures when certifying users

   There are two ways in which a user can be certified:

   - individual certification, or
   - bulk certification

   When applying individual certification, a user will generate his own
   key pair, and his own self-signed certificate. The certification
   procedure follows the PEM documents [1,2,3,4], with the exception
   that the certification request will be sent to an RA. The user must
   then visit the RA with proof of identity





Berge                        Informational                      [Page 5]