draft-ietf-sidr-cps-irs-02.txt   draft-ietf-sidr-cps-irs-03.txt 
Secure Inter-Domain Routing (sidr) Kong, D. Secure Inter-Domain Routing (sidr) Kong, D.
Internet Draft Seo, K. Internet Draft Seo, K.
Expires: January 2008 Kent, S. Expires: August 2008 Kent, S.
Intended Status: Informational BBN Technologies Intended Status: Informational BBN Technologies
February 2008
Template for an Template for an
Internet Registry's Certification Practice Statement (CPS) Internet Registry's Certification Practice Statement (CPS)
for the Internet IP Address and AS Number (PKI) for the Resource PKI (RPKI)
draft-ietf-sidr-cps-irs-02.txt draft-ietf-sidr-cps-irs-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 35 skipping to change at page 1, line 37
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 8, 2008. This Internet-Draft will expire on August 31, 2008.
Abstract Abstract
This document contains a template to be used for creating a This document contains a template to be used for creating a
Certification Practice Statement (CPS) for an Internet Registry Certification Practice Statement (CPS) for an Internet Registry
(e.g., NIR or RIR) that is part of the Internet IP Address and (e.g., NIR or RIR) that is part of the Resource Public Key
Autonomous System (AS) Number Public Key Infrastructure (PKI). Infrastructure (RPKI).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
Preface...........................................................8 Preface...........................................................8
1. Introduction...................................................9 1. Introduction...................................................9
1.1. Overview.................................................10 1.1. Overview.................................................10
1.2. Document name and identification.........................11 1.2. Document name and identification.........................11
1.3. PKI participants.........................................11 1.3. PKI participants.........................................11
1.3.1. Certification authorities...........................11 1.3.1. Certification authorities...........................11
1.3.2. Registration authorities............................11 1.3.2. Registration authorities............................11
1.3.3. Subscribers.........................................11 1.3.3. Subscribers.........................................12
1.3.4. Relying parties.....................................12 1.3.4. Relying parties.....................................12
1.3.5. Other participants..................................12 1.3.5. Other participants..................................12
1.4. Certificate usage........................................12 1.4. Certificate usage........................................12
1.4.1. Appropriate certificate uses........................12 1.4.1. Appropriate certificate uses........................12
1.4.2. Prohibited certificate uses.........................13 1.4.2. Prohibited certificate uses.........................13
1.5. Policy administration....................................13 1.5. Policy administration....................................13
1.5.1. Organization administering the document.............13 1.5.1. Organization administering the document.............13
1.5.2. Contact person......................................13 1.5.2. Contact person......................................13
1.5.3. Person determining CPS suitability for the policy...13 1.5.3. Person determining CPS suitability for the policy...13
1.5.4. CPS approval procedures.............................13 1.5.4. CPS approval procedures.............................13
skipping to change at page 2, line 49 skipping to change at page 2, line 49
3.1.1. Types of names......................................16 3.1.1. Types of names......................................16
3.1.2. Need for names to be meaningful.....................16 3.1.2. Need for names to be meaningful.....................16
3.1.3. Anonymity or pseudonymity of subscribers............16 3.1.3. Anonymity or pseudonymity of subscribers............16
3.1.4. Rules for interpreting various name forms...........16 3.1.4. Rules for interpreting various name forms...........16
3.1.5. Uniqueness of names.................................16 3.1.5. Uniqueness of names.................................16
3.1.6. Recognition, authentication, and role of trademarks.17 3.1.6. Recognition, authentication, and role of trademarks.17
3.2. Initial identity validation..............................17 3.2. Initial identity validation..............................17
3.2.1. Method to prove possession of private key...........17 3.2.1. Method to prove possession of private key...........17
3.2.2. Authentication of organization identity.............17 3.2.2. Authentication of organization identity.............17
3.2.3. Authentication of individual identity...............17 3.2.3. Authentication of individual identity...............17
3.2.4. Non-verified subscriber information.................18 3.2.4. Non-verified subscriber information.................17
3.2.5. Validation of authority.............................18 3.2.5. Validation of authority.............................18
3.2.6. Criteria for interoperation.........................18 3.2.6. Criteria for interoperation.........................18
3.3. Identification and authentication for re-key requests....18 3.3. Identification and authentication for re-key requests....18
3.3.1. Identification and authentication for routine re-key18 3.3.1. Identification and authentication for routine re-key18
3.3.2. Identification and authentication for re-key after 3.3.2. Identification and authentication for re-key after
revocation.................................................18 revocation.................................................18
3.4. Identification and authentication for revocation request.19 3.4. Identification and authentication for revocation request.18
4. Certificate Life-Cycle Operational Requirements...............20 4. Certificate Life-Cycle Operational Requirements...............19
4.1. Certificate Application..................................20 4.1. Certificate Application..................................19
4.1.1. Who can submit a certificate application............20 4.1.1. Who can submit a certificate application............19
4.1.2. Enrollment process and responsibilities.............20 4.1.2. Enrollment process and responsibilities.............19
4.2. Certificate application processing.......................20 4.2. Certificate application processing.......................19
4.2.1. Performing identification and authentication functions 4.2.1. Performing identification and authentication functions
...........................................................20 ...........................................................19
4.2.2. Approval or rejection of certificate applications...20 4.2.2. Approval or rejection of certificate applications...19
4.2.3. Time to process certificate applications............21 4.2.3. Time to process certificate applications............20
4.3. Certificate issuance.....................................21 4.3. Certificate issuance.....................................20
4.3.1. CA actions during certificate issuance..............21 4.3.1. CA actions during certificate issuance..............20
4.3.2. Notification to subscriber by the CA of issuance of 4.3.2. Notification to subscriber by the CA of issuance of
certificate................................................21 certificate................................................20
4.4. Certificate acceptance...................................21 4.4. Certificate acceptance...................................20
4.4.1. Conduct constituting certificate acceptance.........21 4.4.1. Conduct constituting certificate acceptance.........20
4.4.2. Publication of the certificate by the CA............21 4.4.2. Publication of the certificate by the CA............20
4.5. Key pair and certificate usage...........................21 4.5. Key pair and certificate usage...........................21
4.5.1. Subscriber private key and certificate usage........22 4.5.1. Subscriber private key and certificate usage........21
4.5.2. Relying party public key and certificate usage......22 4.5.2. Relying party public key and certificate usage......21
4.6. Certificate renewal......................................22 4.6. Certificate renewal......................................21
4.6.1. Circumstance for certificate renewal................22 4.6.1. Circumstance for certificate renewal................21
4.6.2. Who may request renewal.............................23 4.6.2. Who may request renewal.............................22
4.6.3. Processing certificate renewal requests.............23 4.6.3. Processing certificate renewal requests.............22
4.6.4. Notification of new certificate issuance to subscriber 4.6.4. Notification of new certificate issuance to subscriber
...........................................................23 ...........................................................22
4.6.5. Conduct constituting acceptance of a renewal 4.6.5. Conduct constituting acceptance of a renewal
certificate................................................23 certificate................................................22
4.6.6. Publication of the renewal certificate by the CA....23 4.6.6. Publication of the renewal certificate by the CA....22
4.6.7. Notification of certificate issuance by the CA to other 4.6.7. Notification of certificate issuance by the CA to other
entities [OMITTED].........................................23 entities [OMITTED].........................................22
4.7. Certificate re-key.......................................23 4.7. Certificate re-key.......................................22
4.7.1. Circumstance for certificate re-key.................23 4.7.1. Circumstance for certificate re-key.................22
4.7.2. Who may request certification of a new public key...24 4.7.2. Who may request certification of a new public key...23
4.7.3. Processing certificate re-keying requests...........24 4.7.3. Processing certificate re-keying requests...........23
4.7.4. Notification of new certificate issuance to subscriber 4.7.4. Notification of new certificate issuance to subscriber
...........................................................24 ...........................................................23
4.7.5. Conduct constituting acceptance of a re-keyed 4.7.5. Conduct constituting acceptance of a re-keyed
certificate................................................24 certificate................................................23
4.7.6. Publication of the re-keyed certificate by the CA...24 4.7.6. Publication of the re-keyed certificate by the CA...24
4.7.7. Notification of certificate issuance by the CA to other 4.7.7. Notification of certificate issuance by the CA to other
entities [OMITTED].........................................25 entities [OMITTED].........................................24
4.8. Certificate modification.................................25 4.8. Certificate modification.................................24
4.8.1. Circumstance for certificate modification...........25 4.8.1. Circumstance for certificate modification...........24
4.8.2. Who may request certificate modification............25 4.8.2. Who may request certificate modification............24
4.8.3. Processing certificate modification requests........25 4.8.3. Processing certificate modification requests........25
4.8.4. Notification of modified certificate issuance to 4.8.4. Notification of modified certificate issuance to
subscriber.................................................26 subscriber.................................................25
4.8.5. Conduct constituting acceptance of modified certificate 4.8.5. Conduct constituting acceptance of modified certificate
...........................................................26 ...........................................................25
4.8.6. Publication of the modified certificate by the CA...26 4.8.6. Publication of the modified certificate by the CA...25
4.8.7. Notification of certificate issuance by the CA to other 4.8.7. Notification of certificate issuance by the CA to other
entities [OMITTED].........................................26 entities [OMITTED].........................................25
4.9. Certificate revocation and suspension....................26 4.9. Certificate revocation and suspension....................25
4.9.1. Circumstances for revocation........................26 4.9.1. Circumstances for revocation........................25
4.9.2. Who can request revocation..........................26 4.9.2. Who can request revocation..........................26
4.9.3. Procedure for revocation request....................26 4.9.3. Procedure for revocation request....................26
4.9.4. Revocation request grace period.....................27 4.9.4. Revocation request grace period.....................26
4.9.5. Time within which CA must process the revocation 4.9.5. Time within which CA must process the revocation
request....................................................27 request....................................................26
4.9.6. Revocation checking requirement for relying parties.27 4.9.6. Revocation checking requirement for relying parties.26
4.9.7. CRL issuance frequency..............................27 4.9.7. CRL issuance frequency..............................26
4.9.8. Maximum latency for CRLs............................27 4.9.8. Maximum latency for CRLs............................26
4.9.9. On-line revocation/status checking availability 4.9.9. On-line revocation/status checking availability
[OMITTED]..................................................28 [OMITTED]..................................................27
4.9.10. On-line revocation checking requirements [OMITTED].28 4.9.10. On-line revocation checking requirements [OMITTED].27
4.9.11. Other forms of revocation advertisements available 4.9.11. Other forms of revocation advertisements available
[OMITTED]..................................................28 [OMITTED]..................................................27
4.9.12. Special requirements re key compromise [OMITTED]...28 4.9.12. Special requirements re key compromise [OMITTED]...27
4.9.13. Circumstances for suspension [OMITTED].............28 4.9.13. Circumstances for suspension [OMITTED].............27
4.9.14. Who can request suspension [OMITTED]...............28 4.9.14. Who can request suspension [OMITTED]...............27
4.9.15. Procedure for suspension request [OMITTED].........28 4.9.15. Procedure for suspension request [OMITTED].........27
4.9.16. Limits on suspension period [OMITTED]..............28 4.9.16. Limits on suspension period [OMITTED]..............27
4.10. Certificate status services.............................28 4.10. Certificate status services.............................27
4.10.1. Operational characteristics [OMITTED]..............28 4.10.1. Operational characteristics [OMITTED]..............27
4.10.2. Service availability [OMITTED].....................28 4.10.2. Service availability [OMITTED].....................27
4.10.3. Optional features [OMITTED]........................28 4.10.3. Optional features [OMITTED]........................27
4.11. End of subscription [OMITTED]...........................28 4.11. End of subscription [OMITTED]...........................27
4.12. Key escrow and recovery [OMITTED].......................28 4.12. Key escrow and recovery [OMITTED].......................27
4.12.1. Key escrow and recovery policy and practices [OMITTED] 4.12.1. Key escrow and recovery policy and practices [OMITTED]
...........................................................28 ...........................................................27
4.12.2. Session key encapsulation and recovery policy and 4.12.2. Session key encapsulation and recovery policy and
practices [OMITTED]........................................28 practices [OMITTED]........................................27
5. Facility, Management, And Operational Controls................29 5. Facility, Management, And Operational Controls................28
5.1. Physical controls........................................29 5.1. Physical controls........................................28
5.1.1. Site location and construction......................29 5.1.1. Site location and construction......................28
5.1.2. Physical access.....................................29 5.1.2. Physical access.....................................28
5.1.3. Power and air conditioning..........................29 5.1.3. Power and air conditioning..........................28
5.1.4. Water exposures.....................................29 5.1.4. Water exposures.....................................28
5.1.5. Fire prevention and protection......................29 5.1.5. Fire prevention and protection......................28
5.1.6. Media storage.......................................29 5.1.6. Media storage.......................................28
5.1.7. Waste disposal......................................29 5.1.7. Waste disposal......................................28
5.1.8. Off-site backup.....................................29 5.1.8. Off-site backup.....................................28
5.2. Procedural controls......................................29 5.2. Procedural controls......................................28
5.2.1. Trusted roles.......................................29 5.2.1. Trusted roles.......................................28
5.2.2. Number of persons required per task.................29 5.2.2. Number of persons required per task.................28
5.2.3. Identification and authentication for each role.....29 5.2.3. Identification and authentication for each role.....28
5.2.4. Roles requiring separation of duties................29 5.2.4. Roles requiring separation of duties................28
5.3. Personnel controls.......................................29 5.3. Personnel controls.......................................28
5.3.1. Qualifications, experience, and clearance requirements 5.3.1. Qualifications, experience, and clearance requirements
...........................................................30 ...........................................................29
5.3.2. Background check procedures.........................30 5.3.2. Background check procedures.........................29
5.3.3. Training requirements...............................30 5.3.3. Training requirements...............................29
5.3.4. Retraining frequency and requirements...............30 5.3.4. Retraining frequency and requirements...............29
5.3.5. Job rotation frequency and sequence.................30 5.3.5. Job rotation frequency and sequence.................29
5.3.6. Sanctions for unauthorized actions..................30 5.3.6. Sanctions for unauthorized actions..................29
5.3.7. Independent contractor requirements.................30 5.3.7. Independent contractor requirements.................29
5.3.8. Documentation supplied to personnel.................30 5.3.8. Documentation supplied to personnel.................29
5.4. Audit logging procedures.................................30 5.4. Audit logging procedures.................................29
5.4.1. Types of events recorded............................30 5.4.1. Types of events recorded............................29
5.4.2. Frequency of processing log.........................30 5.4.2. Frequency of processing log.........................29
5.4.3. Retention period for audit log......................30 5.4.3. Retention period for audit log......................29
5.4.4. Protection of audit log.............................31 5.4.4. Protection of audit log.............................30
5.4.5. Audit log backup procedures.........................31 5.4.5. Audit log backup procedures.........................30
5.4.6. Audit collection system (internal vs. external) 5.4.6. Audit collection system (internal vs. external)
[OMITTED]..................................................31 [OMITTED]..................................................30
5.4.7. Notification to event-causing subject [OMITTED].....31 5.4.7. Notification to event-causing subject [OMITTED].....30
5.4.8. Vulnerability assessments...........................31 5.4.8. Vulnerability assessments...........................30
5.5. Records archival [OMITTED]...............................31 5.5. Records archival [OMITTED]...............................30
5.5.1. Types of records archived [OMITTED].................31 5.5.1. Types of records archived [OMITTED].................30
5.5.2. Retention period for archive [OMITTED]..............31 5.5.2. Retention period for archive [OMITTED]..............30
5.5.3. Protection of archive [OMITTED].....................31 5.5.3. Protection of archive [OMITTED].....................30
5.5.4. Archive backup procedures [OMITTED].................31 5.5.4. Archive backup procedures [OMITTED].................30
5.5.5. Requirements for time-stamping of records [OMITTED].31 5.5.5. Requirements for time-stamping of records [OMITTED].30
5.5.6. Archive collection system (internal or external) 5.5.6. Archive collection system (internal or external)
[OMITTED]..................................................31 [OMITTED]..................................................30
5.5.7. Procedures to obtain and verify archive information 5.5.7. Procedures to obtain and verify archive information
[OMITTED]..................................................31 [OMITTED]..................................................30
5.6. Key changeover...........................................31 5.6. Key changeover...........................................30
5.7. Compromise and disaster recovery [OMITTED]...............32 5.7. Compromise and disaster recovery [OMITTED]...............31
5.7.1. Incident and compromise handling procedures [OMITTED]32 5.7.1. Incident and compromise handling procedures [OMITTED]31
5.7.2. Computing resources, software, and/or data are 5.7.2. Computing resources, software, and/or data are
corrupted [OMITTED]........................................32 corrupted [OMITTED]........................................31
5.7.3. Entity private key compromise procedures [OMITTED]..32 5.7.3. Entity private key compromise procedures [OMITTED]..31
5.7.4. Business continuity capabilities after a disaster 5.7.4. Business continuity capabilities after a disaster
[OMITTED]..................................................32 [OMITTED]..................................................31
5.8. CA or RA termination.....................................32 5.8. CA or RA termination.....................................31
6. Technical Security Controls...................................33 6. Technical Security Controls...................................32
6.1. Key pair generation and installation.....................33 6.1. Key pair generation and installation.....................32
6.1.1. Key pair generation.................................33 6.1.1. Key pair generation.................................32
6.1.2. Private key delivery to subscriber..................33 6.1.2. Private key delivery to subscriber..................32
6.1.3. Public key delivery to certificate issuer...........33 6.1.3. Public key delivery to certificate issuer...........32
6.1.4. CA public key delivery to relying parties...........33 6.1.4. CA public key delivery to relying parties...........32
6.1.5. Key sizes...........................................34 6.1.5. Key sizes...........................................33
6.1.6. Public key parameters generation and quality checking34 6.1.6. Public key parameters generation and quality checking33
6.1.7. Key usage purposes (as per X.509 v3 key usage field)34 6.1.7. Key usage purposes (as per X.509 v3 key usage field)33
6.2. Private Key Protection and Cryptographic Module Engineering 6.2. Private Key Protection and Cryptographic Module Engineering
Controls......................................................34 Controls......................................................33
6.2.1. Cryptographic module standards and controls.........34 6.2.1. Cryptographic module standards and controls.........33
6.2.2. Private key (n out of m) multi-person control.......34 6.2.2. Private key (n out of m) multi-person control.......33
6.2.3. Private key escrow..................................34 6.2.3. Private key escrow..................................33
6.2.4. Private key backup..................................35 6.2.4. Private key backup..................................34
6.2.5. Private key archival................................35 6.2.5. Private key archival................................34
6.2.6. Private key transfer into or from a cryptographic 6.2.6. Private key transfer into or from a cryptographic
module.....................................................35 module.....................................................34
6.2.7. Private key storage on cryptographic module.........35 6.2.7. Private key storage on cryptographic module.........34
6.2.8. Method of activating private key....................35 6.2.8. Method of activating private key....................34
6.2.9. Method of deactivating private key..................35 6.2.9. Method of deactivating private key..................34
6.2.10. Method of destroying private key...................35 6.2.10. Method of destroying private key...................34
6.2.11. Cryptographic Module Rating........................35 6.2.11. Cryptographic Module Rating........................34
6.3. Other aspects of key pair management.....................36 6.3. Other aspects of key pair management.....................35
6.3.1. Public key archival.................................36 6.3.1. Public key archival.................................35
6.3.2. Certificate operational periods and key pair usage 6.3.2. Certificate operational periods and key pair usage
periods....................................................36 periods....................................................35
6.4. Activation data..........................................36 6.4. Activation data..........................................35
6.4.1. Activation data generation and installation.........36 6.4.1. Activation data generation and installation.........35
6.4.2. Activation data protection..........................36 6.4.2. Activation data protection..........................35
6.4.3. Other aspects of activation data....................36 6.4.3. Other aspects of activation data....................35
6.5. Computer security controls...............................36 6.5. Computer security controls...............................35
6.5.1. Specific computer security technical requirement....36 6.5.1. Specific computer security technical requirement....35
6.5.2. Computer security rating [OMITTED]..................37 6.5.2. Computer security rating [OMITTED]..................36
6.6. Life cycle technical controls............................37 6.6. Life cycle technical controls............................36
6.6.1. System development controls.........................37 6.6.1. System development controls.........................36
6.6.2. Security management controls........................37 6.6.2. Security management controls........................36
6.6.3. Life cycle security controls........................37 6.6.3. Life cycle security controls........................36
6.7. Network security controls................................37 6.7. Network security controls................................36
6.8. Time-stamping............................................37 6.8. Time-stamping............................................36
7. Certificate and CRL Profiles..................................38 7. Certificate and CRL Profiles..................................37
Please refer to the Certificate and CRL Profile [draft-ietf-sidr- Please refer to the Certificate and CRL Profile [draft-ietf-sidr-
res-certs-01].................................................38 res-certs-01].................................................37
7.1. Certificate profile [OMITTED]............................38 7.1. Certificate profile [OMITTED]............................37
7.1.1. Version number(s) [OMITTED].........................38 7.1.1. Version number(s) [OMITTED].........................37
7.1.2. Certificate extensions [OMITTED]....................38 7.1.2. Certificate extensions [OMITTED]....................37
7.1.3. Algorithm object identifiers [OMITTED]..............38 7.1.3. Algorithm object identifiers [OMITTED]..............37
7.1.4. Name forms [OMITTED]................................38 7.1.4. Name forms [OMITTED]................................37
7.1.5. Name constraints [OMITTED]..........................38 7.1.5. Name constraints [OMITTED]..........................37
7.1.6. Certificate policy object identifier [OMITTED]......38 7.1.6. Certificate policy object identifier [OMITTED]......37
7.1.7. Usage of Policy Constraints extension [OMITTED].....38 7.1.7. Usage of Policy Constraints extension [OMITTED].....37
7.1.8. Policy qualifiers syntax and semantics [OMITTED]....38 7.1.8. Policy qualifiers syntax and semantics [OMITTED]....37
7.1.9. Processing semantics for the critical Certificate 7.1.9. Processing semantics for the critical Certificate
Policies extension [OMITTED]...............................38 Policies extension [OMITTED]...............................37
7.2. CRL profile [OMITTED]....................................38 7.2. CRL profile [OMITTED]....................................37
7.2.1. Version number(s) [OMITTED].........................38 7.2.1. Version number(s) [OMITTED].........................37
7.2.2. CRL and CRL entry extensions [OMITTED]..............38 7.2.2. CRL and CRL entry extensions [OMITTED]..............37
7.3. OCSP profile [OMITTED]...................................38 7.3. OCSP profile [OMITTED]...................................37
7.3.1. Version number(s) [OMITTED].........................38 7.3.1. Version number(s) [OMITTED].........................37
7.3.2. OCSP extensions [OMITTED]...........................38 7.3.2. OCSP extensions [OMITTED]...........................37
8. Compliance Audit and Other Assessments........................39 8. Compliance Audit and Other Assessments........................38
8.1. Frequency or circumstances of assessment.................39 8.1. Frequency or circumstances of assessment.................38
8.2. Identity/qualifications of assessor......................39 8.2. Identity/qualifications of assessor......................38
8.3. Assessor's relationship to assessed entity...............39 8.3. Assessor's relationship to assessed entity...............38
8.4. Topics covered by assessment.............................39 8.4. Topics covered by assessment.............................38
8.5. Actions taken as a result of deficiency..................39 8.5. Actions taken as a result of deficiency..................38
8.6. Communication of results.................................39 8.6. Communication of results.................................38
9. Other Business And Legal Matters..............................40 9. Other Business And Legal Matters..............................39
9.1. Fees.....................................................40 9.1. Fees.....................................................39
9.1.1. Certificate issuance or renewal fees................40 9.1.1. Certificate issuance or renewal fees................39
9.1.2. Fees for other services (if applicable).............40 9.1.2. Fees for other services (if applicable).............39
9.1.3. Refund policy.......................................40 9.1.3. Refund policy.......................................39
9.2. Financial responsibility.................................40 9.2. Financial responsibility.................................39
9.2.1. Insurance coverage..................................40 9.2.1. Insurance coverage..................................39
9.2.2. Other assets........................................40 9.2.2. Other assets........................................39
9.2.3. Insurance or warranty coverage for end-entities.....40 9.2.3. Insurance or warranty coverage for end-entities.....39
9.3. Confidentiality of business information..................40 9.3. Confidentiality of business information..................39
9.3.1. Scope of confidential information...................40 9.3.1. Scope of confidential information...................39
9.3.2. Information not within the scope of confidential 9.3.2. Information not within the scope of confidential
information................................................40 information................................................39
9.3.3. Responsibility to protect confidential information..40 9.3.3. Responsibility to protect confidential information..39
9.4. Privacy of personal information..........................40 9.4. Privacy of personal information..........................39
9.4.1. Privacy plan........................................40 9.4.1. Privacy plan........................................39
9.4.2. Information treated as private......................40 9.4.2. Information treated as private......................39
9.4.3. Information not deemed private......................40 9.4.3. Information not deemed private......................39
9.4.4. Responsibility to protect private information.......40 9.4.4. Responsibility to protect private information.......39
9.4.5. Notice and consent to use private information.......40 9.4.5. Notice and consent to use private information.......39
9.4.6. Disclosure pursuant to judicial or administrative 9.4.6. Disclosure pursuant to judicial or administrative
process....................................................41 process....................................................40
9.4.7. Other information disclosure circumstances..........41 9.4.7. Other information disclosure circumstances..........40
9.5. Intellectual property rights (if applicable).............41 9.5. Intellectual property rights (if applicable).............40
9.6. Representations and warranties...........................41 9.6. Representations and warranties...........................40
9.6.1. CA representations and warranties...................41 9.6.1. CA representations and warranties...................40
9.6.2. Subscriber representations and warranties...........41 9.6.2. Subscriber representations and warranties...........40
9.6.3. Relying party representations and warranties........41 9.6.3. Relying party representations and warranties........40
9.6.4. Representations and warranties of other participants 9.6.4. Representations and warranties of other participants
[OMITTED]..................................................41 [OMITTED]..................................................40
9.7. Disclaimers of warranties................................41 9.7. Disclaimers of warranties................................40
9.8. Limitations of liability.................................41 9.8. Limitations of liability.................................40
9.9. Indemnities..............................................41 9.9. Indemnities..............................................40
9.10. Term and termination....................................41 9.10. Term and termination....................................40
9.10.1. Term...............................................41 9.10.1. Term...............................................40
9.10.2. Termination........................................41 9.10.2. Termination........................................40
9.10.3. Effect of termination and survival.................41 9.10.3. Effect of termination and survival.................40
9.11. Individual notices and communications with participants.41 9.11. Individual notices and communications with participants.40
9.12. Amendments..............................................41 9.12. Amendments..............................................40
9.12.1. Procedure for amendment............................41 9.12.1. Procedure for amendment............................40
9.12.2. Notification mechanism and period..................41 9.12.2. Notification mechanism and period..................40
9.12.3. Circumstances under which OID must be changed 9.12.3. Circumstances under which OID must be changed
[OMITTED]..................................................41 [OMITTED]..................................................40
9.13. Dispute resolution provisions...........................41 9.13. Dispute resolution provisions...........................40
9.14. Governing law...........................................41 9.14. Governing law...........................................40
9.15. Compliance with applicable law..........................41 9.15. Compliance with applicable law..........................40
9.16. Miscellaneous provisions................................41 9.16. Miscellaneous provisions................................40
9.16.1. Entire agreement...................................42 9.16.1. Entire agreement...................................41
9.16.2. Assignment.........................................42 9.16.2. Assignment.........................................41
9.16.3. Severability.......................................42 9.16.3. Severability.......................................41
9.16.4. Enforcement (attorneys' fees and waiver of rights).42 9.16.4. Enforcement (attorneys' fees and waiver of rights).41
9.16.5. Force Majeure......................................42 9.16.5. Force Majeure......................................41
9.17. Other provisions [OMITTED]..............................42 9.17. Other provisions [OMITTED]..............................41
10. Security Considerations......................................43 10. Security Considerations......................................42
11. IANA Considerations..........................................43 11. IANA Considerations..........................................42
12. Acknowledgments..............................................43 12. Acknowledgments..............................................42
13. References...................................................43 13. References...................................................42
13.1. Normative References....................................43 13.1. Normative References....................................42
13.2. Informative References..................................44 13.2. Informative References..................................43
Author's Addresses...............................................44 Author's Addresses...............................................43
Intellectual Property Statement..................................45 Intellectual Property Statement..................................44
Disclaimer of Validity...........................................45 Disclaimer of Validity...........................................45
Copyright Statement..............................................45 Copyright Statement..............................................45
Preface Preface
This document contains a template to be used for creating a This document contains a template to be used for creating a
Certification Practice Statement (CPS) for an Internet Registry Certification Practice Statement (CPS) for an Internet Registry
(e.g., an NIR or RIR) that is part of the Internet IP Address and (e.g., an NIR or RIR) that is part of the Resource Public Key
Autonomous System (AS) Number Public Key Infrastructure (PKI). The Infrastructure (RPKI). The user of this document should
user of this document should
1. substitute a title page for page 1 saying, e.g., "<Name of 1. substitute a title page for page 1 saying, e.g., "<Name of
Registry> Certification Practice Statement for the Internet IP Registry> Certification Practice Statement for the Resource
Address and AS Number Public Key Infrastructure (PKI)" with Public Key Infrastructure (RPKI)" with date, author, etc.
date, author, etc.
2. delete this Preface 2. delete this Preface
3. fill in the information indicated below by <text in angle 3. fill in the information indicated below by <text in angle
brackets> brackets>
4. delete sections 10, 11, 12, 13.1, Acknowledgments, Author's 4. delete sections 10, 11, 12, 13.1, Acknowledgments, Author's
Addresses, Intellectual Property Statement, Disclaimer of Addresses, Intellectual Property Statement, Disclaimer of
Validity, Copyright Statement, Acknowledgments; leaving a Validity, Copyright Statement, Acknowledgments; leaving a
reference section with just the references in 13.2 reference section with just the references in 13.2
skipping to change at page 9, line 33 skipping to change at page 9, line 33
in the Introduction below. This information should be left in the in the Introduction below. This information should be left in the
CPS as an explanation to the user. CPS as an explanation to the user.
1. Introduction 1. Introduction
This document is the Certification Practice Statement (CPS) of <Name This document is the Certification Practice Statement (CPS) of <Name
of Registry>. It describes the practices employed by the <Name of of Registry>. It describes the practices employed by the <Name of
Registry> Certification Authority (CA) in the Internet IP Address Registry> Certification Authority (CA) in the Internet IP Address
and Autonomous System (AS) Number PKI. These practices are defined and Autonomous System (AS) Number PKI. These practices are defined
in accordance with the requirements of the Certificate Policy (CP, in accordance with the requirements of the Certificate Policy (CP,
[CP]) of this PKI. [RFCxxxx]) of this PKI.
The Internet IP Address and AS Number PKI is aimed at supporting The Resource PKI is aimed at supporting verifiable attestations
verifiable attestations about resource controls, e.g., for improved about resource controls, e.g., for improved routing security. The
routing security. The goal is that each entity that allocates IP goal is that each entity that allocates IP addresses or AS numbers
addresses or AS numbers to an entity will, in parallel, issue a to an entity will, in parallel, issue a certificate reflecting this
certificate reflecting this allocation. These certificates will allocation. These certificates will enable verification that the
enable verification that the holder of the associated private key holder of the associated private key has been allocated the
has been allocated the resources indicated in the certificate, and resources indicated in the certificate, and is the current, unique
is the current, unique holder of these resources. The certificates holder of these resources. The certificates and CRLs, in conjunction
and CRLs, in conjunction with ancillary digitally signed data with ancillary digitally signed data structures, will provide
structures, will provide critical inputs for routing security critical inputs for routing security mechanisms, e.g., generation of
mechanisms, e.g., generation of route filters by ISPs. route filters by ISPs.
The most important and distinguishing aspect of the PKI for which The most important and distinguishing aspect of the PKI for which
this CPS was created is that it does not purport to identify an this CPS was created is that it does not purport to identify an
address space holder or AS number holder via the subject name address space holder or AS number holder via the subject name
contained in the certificate issued to that entity. Rather, each contained in the certificate issued to that entity. Rather, each
certificate issued under this policy is intended to enable an entity certificate issued under this policy is intended to enable an entity
to assert in a verifiable fashion, that it is the current holder of to assert in a verifiable fashion, that it is the current holder of
an address block or an AS number, based on the current records of an address block or an AS number, based on the current records of
the entity responsible for the resources in question. Verification the entity responsible for the resources in question. Verification
of the assertion is based on two criteria: the ability of the entity of the assertion is based on two criteria: the ability of the entity
skipping to change at page 10, line 49 skipping to change at page 10, line 49
. Audit procedures . Audit procedures
. Business and legal issues . Business and legal issues
The PKI encompasses several types of certificates: The PKI encompasses several types of certificates:
. CA certificates for each organization allocating address blocks . CA certificates for each organization allocating address blocks
and/or AS numbers, and for each address space (AS number) holder and/or AS numbers, and for each address space (AS number) holder
. End entity ("shadow") certificates for organizations to use in . End entity (EE) certificates for organizations to use in verifying
verifying signatures of Route Origination Authorizations (ROAs) signatures of Route Origination Authorizations (ROAs) and other
and other (non-certificate/CRL) signed objects (non-certificate/CRL) signed objects
. In the future, the PKI also may include end entity certificates in . In the future, the PKI also may include end entity certificates in
support of access control for the repository system support of access control for the repository system
1.2. Document name and identification 1.2. Document name and identification
The name of this document is "<Name of Registry>'s Certification The name of this document is "<Name of Registry>'s Certification
Practice Statement for the Internet IP Address and AS Number PKI". Practice Statement for the Resource Public Key Infrastructure
(RPKI)".
1.3. PKI participants 1.3. PKI participants
Note: In a PKI, the term "subscriber" refers to an individual or Note: In a PKI, the term "subscriber" refers to an individual or
organization that is a Subject of a certificate issued by a CA. The organization that is a Subject of a certificate issued by a CA. The
term is used in this fashion throughout this document, without term is used in this fashion throughout this document, without
qualification, and should not be confused with the networking use of qualification, and should not be confused with the networking use of
the term to refer to an individual or organization that receives the term to refer to an individual or organization that receives
service from an LIR/ISP. Thus, in this PKI, the term "subscriber" service from an LIR/ISP. Thus, in this PKI, the term "subscriber"
can refer both to LIRs/ISPs, which can be subscribers of RIRs, NIRs, can refer both to LIRs/ISPs, which can be subscribers of RIRs, NIRs,
and other LIRs, and also to organizations that are not ISPs, but and other LIRs, and also to organizations that are not ISPs, but
which are subscribers of ISPs in the networking sense of the term. which are subscribers of ISPs in the networking sense of the term.
Also note that, for brevity, this document always refers to Also note that, for brevity, this document always refers to
subscribers as organizations, even though some subscribers are subscribers as organizations, even though some subscribers are
individuals. When necessary, the phrase "network subscriber" is used individuals. When necessary, the phrase "network subscriber" is used
to refer to an organization that receives network services from an to refer to an organization that receives network services from an
LIR/ISP. LIR/ISP.
1.3.1. Certification authorities 1.3.1. Certification authorities
<Name of Registry> will operate a CA, the primary function of which <Name of Registry> will operate two CAs for the RPKI: one is
is the issuance of certificates to organizations to which address designated "offline" and the other is designated "production." The
space or AS numbers are allocated by the registry. In the future, offline CA is the top level CA for the <Name of Registry> portion of
this CA may also issue other types of end entity (EE) certificates, the RPKI. It provides a secure revocation and recovery capability in
e.g., EE certificates to operations personnel in support of case the production CA is compromised or becomes unavailable. Thus
repository maintenance. this CA issues certificates only to instances of the production CA
and the CRLs it issues are used to revoke only a certificate issued
to that CA. The production CA is used to issue RPKI certificates to
<Name of Registry> members, to which address space or AS numbers
have been allocated.
1.3.2. Registration authorities 1.3.2. Registration authorities
For the certificates issued by this registry under this PKI, this There is no registration authority (RA) for either the offline or
function is provided by the registry per se. The registry already the production CA operating under this CPS. The former needs no RA
performs this function -- establishing a formal relationship with capability because it issues certificates only to the production CA.
each subscriber and assuming responsibility for allocating and The production CA relies upon certificates issued by the <Name of
tracking the current allocation of address space and AS numbers. Registry> Business PKI (BPKI) (see Section 3.2.6) to identify
Since the registry operates the CA, there is no distinct RA. individuals authorized to requests certificates under the RPKI.
<Name of Registry> already establishes a business relationship with
each subscriber (<Name of Registry> member) and assumes
responsibility for allocating and tracking the current allocation of
address space and AS numbers. Since <Name of Registry> operates the
BPKI CA, there is no distinct RA for the RPKI.
1.3.3. Subscribers 1.3.3. Subscribers
Two types of organizations receive allocations of IP addresses and Two types of organizations receive allocations of IP addresses and
AS numbers from this CA and thus are subscribers in the PKI sense: AS numbers from this CA and thus are subscribers in the PKI sense:
network subscribers and Internet Service Providers (ISPs). network subscribers and Internet Service Providers (ISPs).
<Additionally, this CA issues certificates to <Local/National> <Additionally, this CA issues certificates to <Local/National>
Registries (choose the right term for this RIR, if either applies) Registries (choose the right term for this RIR, if either applies)
who, in turn, issue certificates to network subscribers or who, in turn, issue certificates to network subscribers or
LIRs/ISPs.> LIRs/ISPs.>
1.3.4. Relying parties 1.3.4. Relying parties
Entities that need to validate claims of address space and/or AS Entities that need to validate claims of address space and/or AS
number current holdings are relying parties. Thus, for example, number current holdings are relying parties. Thus, for example,
entities that make use of address and AS number allocation entities that make use of address and AS number allocation
skipping to change at page 12, line 32 skipping to change at page 12, line 41
want to authorize an (or another) LIR/ISP to originate routes to want to authorize an (or another) LIR/ISP to originate routes to
this space. this space.
To the extent that repositories make use of certificates for access To the extent that repositories make use of certificates for access
control - checking for authorization to upload certificate, CRL, and control - checking for authorization to upload certificate, CRL, and
ROA update packages -- they too act as relying parties. ROA update packages -- they too act as relying parties.
1.3.5. Other participants 1.3.5. Other participants
<Name of Registry> will operate a repository that holds <Name of Registry> will operate a repository that holds
certificates, CRLs, and other signed objects, e.g., ROAs. certificates, CRLs, and other RPKI signed objects, e.g., ROAs.
1.4. Certificate usage 1.4. Certificate usage
1.4.1. Appropriate certificate uses 1.4.1. Appropriate certificate uses
The certificates issued under this hierarchy are for authorization The certificates issued under this hierarchy are for authorization
in support of validation of claims of current holdings of address in support of validation of claims of current holdings of address
space and/or AS numbers, e.g., for routing security. With regard to space and/or AS numbers, e.g., for routing security. With regard to
routing security, an initial goal of this PKI is to allow the holder routing security, an initial goal of this PKI is to allow the holder
of a set of address blocks to be able to declare, in a secure of a set of address blocks to be able to declare, in a secure
skipping to change at page 13, line 39 skipping to change at page 13, line 48
Not applicable. Each organization issuing a certificate in this PKI Not applicable. Each organization issuing a certificate in this PKI
is attesting to the allocation of resources (IP addresses, AS is attesting to the allocation of resources (IP addresses, AS
numbers) to the holder of the private key corresponding to the numbers) to the holder of the private key corresponding to the
public key in the certificate. The issuing organizations are the public key in the certificate. The issuing organizations are the
same organizations as the ones that perform the allocation hence same organizations as the ones that perform the allocation hence
they are authoritative with respect to the accuracy of this binding. they are authoritative with respect to the accuracy of this binding.
1.6. Definitions and acronyms 1.6. Definitions and acronyms
BPKI - Business PKI: A BPKI is used by an RIR to identify members to
whom RPKI certificates can be issued.
CP - Certificate Policy. A CP is a named set of rules that CP - Certificate Policy. A CP is a named set of rules that
indicates the applicability of a certificate to a particular indicates the applicability of a certificate to a particular
community and/or class of applications with common security community and/or class of applications with common security
requirements. requirements.
CPS - Certification Practice Statement. A CPS is a document that CPS - Certification Practice Statement. A CPS is a document that
specifies the practices that a Certification Authority employs specifies the practices that a Certification Authority employs
in issuing certificates. in issuing certificates.
ISP - Internet Service Provider. An ISP is an organization managing ISP - Internet Service Provider. An ISP is an organization managing
skipping to change at page 14, line 17 skipping to change at page 14, line 32
NIR - National Internet Registry. An NIR is an organization that NIR - National Internet Registry. An NIR is an organization that
manages the assignment of IP address and AS numbers for a manages the assignment of IP address and AS numbers for a
portion of the geopolitical area covered by a Regional portion of the geopolitical area covered by a Regional
Registry. These form an optional second tier in the tree Registry. These form an optional second tier in the tree
scheme used to manage IP address and AS number allocation. scheme used to manage IP address and AS number allocation.
RIR - Regional Internet Registry. An RIR is an organization that RIR - Regional Internet Registry. An RIR is an organization that
manages the assignment of IP address and AS numbers for a manages the assignment of IP address and AS numbers for a
specified geopolitical area. At present, there are five RIRs: specified geopolitical area. At present, there are five RIRs:
ARIN (North America), RIPE NCC (Europe), APNIC (Asia - ARIN (North America), RIPE NCC (Europe), APNIC (Asia -
Pacific), LACNIC (Latin America and Caribbean), and AFRINIC Pacific), LACNIC (Latin America and Caribbean), and AfriNIC
(Africa). (Africa).
ROA - Route Origination Authorization. This is a digitally signed ROA - Route Origination Authorization. This is a digitally signed
object that identifies a network operator, identified by an object that identifies a network operator, identified by an
AS, that is authorized to originate routes to a specified set AS, that is authorized to originate routes to a specified set
of address blocks. of address blocks.
2. Publication And Repository Responsibilities 2. Publication And Repository Responsibilities
2.1. Repositories 2.1. Repositories
As per the CP, certificates and CRLs, will be made available for As per the CP, certificates and CRLs, will be made available for
downloading by all network operators, to enable them to validate downloading by all network operators, to enable them to validate
this data for use in support of routing security. this data for use in support of routing security.
<Describe here the basic set up of your local repository system.> The <Name of Registry> RPKI CA will publish certificates, CRLs, and
other signed objects accessible via RSYNC at rpki.<Name of
Registry>.net.
2.2. Publication of certification information 2.2. Publication of certification information
<Name of Registry> will upload certificates and CRLs issued by it to <Name of Registry> will upload certificates and CRLs issued by it to
a local repository system that operates as part of a world-wide a local repository system that operates as part of a world-wide
distributed system of repositories. distributed system of repositories.
2.3. Time or Frequency of Publication 2.3. Time or Frequency of Publication
<Describe here your procedures for publication (via the repository) <Describe here your procedures for publication (via the repository)
of the certificates and CRLs that you issue. If you choose to of the certificates and CRLs that you issue. If you choose to
outsource publication of PKI data, you still need to provide this outsource publication of PKI data, you still need to provide this
information for relying parties.> information for relying parties.>
As per the CP, the following standards exist for publication times As per the CP, the following standards exist for publication times
and frequency: and frequency:
A certificate will be published within 24 hours after issuance. A certificate will be published within 24 hours after issuance.
The <Name of Registry> CA will publish its CRL prior to the The <Name of Registry> RPKI CA will publish its CRL prior to the
nextScheduledUpdate value in the scheduled CRL previously issued by nextScheduledUpdate value in the scheduled CRL previously issued by
the CA. Within 24 hours of effecting revocation, the CA will publish the CA. Within 24 hours of effecting revocation, the CA will publish
a CRL with an entry for the revoked certificate. a CRL with an entry for the revoked certificate.
2.4. Access controls on repositories 2.4. Access controls on repositories
Access to the repository system, for modification of entries, must Access to the repository system, for modification of entries, must
be controlled to prevent denial of service attacks. All data be controlled to prevent denial of service attacks. All data
(certificates, CRLs and ROAs) uploaded to a repository are digitally (certificates, CRLs and ROAs) uploaded to a repository are digitally
signed. Updates to the repository system must be validated to ensure signed. Updates to the repository system must be validated to ensure
skipping to change at page 16, line 12 skipping to change at page 16, line 12
does not define the means by which updates are verified, but use of does not define the means by which updates are verified, but use of
the PKI itself to validate updates is anticipated. the PKI itself to validate updates is anticipated.
3. Identification And Authentication 3. Identification And Authentication
3.1. Naming 3.1. Naming
3.1.1. Types of names 3.1.1. Types of names
The Subject of each certificate issued by this Registry is The Subject of each certificate issued by this Registry is
identified by an X.500 Disinguished Name (DN). For certificates identified by an X.500 Distinguished Name (DN). For certificates
issued to LIRs/ISPs and subscribers, the Subject will consist of a issued to LIRs/ISPs and subscribers, the Subject will consist of a
single CN attribute with a value generated by the issuer. For single CN attribute with a value generated by the issuer. For
certificates issued to an NIR, the Subject will be the name of the certificates issued to an NIR, the Subject will be the name of the
NIR. NIR.
3.1.2. Need for names to be meaningful 3.1.2. Need for names to be meaningful
The Subject name in each subscriber certificate will be unique The Subject name in each subscriber certificate will be unique
relative to all certificates issued by <Name of LIR/ISP>. However, relative to all certificates issued by <Name of LIR/ISP> RPKI CA.
there is no guarantee that the subject name will be globally unique However, there is no guarantee that the subject name will be
in this PKI. globally unique in this PKI.
Note: The name of the holder of an address block or AS number need Note: The name of the holder of an address block or AS number need
not to be "meaningful" in the conventional, human-readable sense, not to be "meaningful" in the conventional, human-readable sense,
since certificates issued under this PKI are used for authorization since certificates issued under this PKI are used for authorization
in support of routing security, not for identification in support of routing security, not for identification
3.1.3. Anonymity or pseudonymity of subscribers 3.1.3. Anonymity or pseudonymity of subscribers
Although Subject names in certificates issued by this registry need Although Subject names in certificates issued by this registry need
not be meaningful, and may appear "random," anonymity is not a not be meaningful, and may appear "random," anonymity is not a
skipping to change at page 17, line 15 skipping to change at page 17, line 15
3.1.6. Recognition, authentication, and role of trademarks 3.1.6. Recognition, authentication, and role of trademarks
Because the Subject names are not intended to be meaningful, there Because the Subject names are not intended to be meaningful, there
is no provision to recognize nor authenticate trademarks, service is no provision to recognize nor authenticate trademarks, service
marks, etc. marks, etc.
3.2. Initial identity validation 3.2. Initial identity validation
3.2.1. Method to prove possession of private key 3.2.1. Method to prove possession of private key
<Describe the method whereby each subscriber will be required to <Name of Registry> accepts certificate requests via the protocol
demonstrate proof-of-possession (PoP) of the private key described in [up/down]. This protocol makes use of the PKCS #10
corresponding to the public key in the certificate, prior to issuing format, as profiled in [RFCyyyy]. This request format requires that
the certificate. Standard methods are described in the Certificate the PKCS #10 request be signed using the (RSA) private key
Management Protocol (CMP) (RFC 2510) and the Certificate Management corresponding to the public key in the certificate request. This
Messages over CMS protocol (CMC), RFC 2797.> mechanism provides proof of possession by the requester.
3.2.2. Authentication of organization identity 3.2.2. Authentication of organization identity
Certificates issued under this PKI do not attest to the Certificates issued under this PKI do not attest to the
organizational identity of resource holders, with the exception of organizational identity of resource holders, with the exception of
registries. However, certificates are issued to resource holders in registries. However, certificates are issued to resource holders in
a fashion that preserves the accuracy of bindings in this registry's a fashion that preserves the accuracy of allocations as represented
records. in <Name of Registry> records. Specifically, a BPKI certificate used
to authenticate a certificate request serves as a link to the <Name
<Describe the procedures that will be used to ensure that each of Registry> member database that maintains the resource allocation
certificate that is issued accurately reflects your records with records. The certificate request is matched against the database
regard to the organization to which you have allocated (or sub- record for the member in question, and an RPKI certificate is issued
allocated) the address space (or AS numbers) identified in the only if the resources requested are a subset of those held by the
certificate. The specific procedures employed for this purpose member.
should be commensurate with those you already employ as a registry
in the maintenance of address (and AS number) allocation.>
3.2.3. Authentication of individual identity 3.2.3. Authentication of individual identity
Certificates issued under this PKI do not attest to the individual Certificates issued under this PKI do not attest to the individual
identity of a resource holder. However, this registry maintains identity of a resource holder. However, <Name of Registry> maintains
contact information for each resource holder in support of contact information for each resource holder in support of
certificate renewal, re-key, or revocation. certificate renewal, re-key, or revocation, via the BPKI.
<Describe the procedures that will be used to identify at least one The <Name of Registry> BPKI (see Section 3.2.6) issues certificates
individual as a representative of each organization that is an that are used to identify individuals who represent <Name of
address space (or AS number) holder. This is done in support of Registry> members that are address space (or AS number) holders.
issuance, renewal, and revocation of the certificate issued to the
organization. The procedures should be commensurate with those you
already employ in authenticating individuals as representatives for
address space (or AS number) holders. Note that this authentication
is solely for use by you in dealing with the organizations to which
you allocate (or sub-allocate) address space (or AS numbers), and
thus must not be relied upon outside of this CA-subscriber
relationship.>
3.2.4. Non-verified subscriber information 3.2.4. Non-verified subscriber information
No non-verified subscriber data is included in certificates issued No non-verified subscriber data is included in certificates issued
under this certificate policy. under this certificate policy.
3.2.5. Validation of authority 3.2.5. Validation of authority
<Describe the procedures that will be used to verify that an Only an individual to whom a BPKI certificate (see Section 3.2.6)
individual claiming to represent a resource holder to which a has been issued may request issuance of an RPKI certificate. Each
certificate is issued, is authorized to represent that resource certificate issuance request is verified using the BPKI.
holder in this context. The procedures should be commensurate with
those you already employ as a registry in authenticating individuals
as representatives of resource holders.>
3.2.6. Criteria for interoperation 3.2.6. Criteria for interoperation
This PKI is neither intended nor designed to interoperate with any The RPKI is neither intended nor designed to interoperate with any
other PKI. other PKI. However, <Name of Registry> operates a BPKI [cps-
business-pki] that is used to authenticate members and to enable
them to manage their resource allocations. The Resource PKI relies
on this BPKI to authenticate Subscribers who make certificate
requests, revocation requests, etc.
3.3. Identification and authentication for re-key requests 3.3. Identification and authentication for re-key requests
3.3.1. Identification and authentication for routine re-key 3.3.1. Identification and authentication for routine re-key
<Describe the procedures that will be used to ensure that an Routine re-key is effected via a Certificate Issuance Request
organization requesting a re-key is the legitimate holder of the message as described in [up/down]. This digitally signed CMS message
certificate (and associated address space and AS numbers) to be re- is authenticated using a BPKI certificate associated with the
keyed. This should also include the method employed for verifying requester.
PoP of the private key corresponding to the new public key. With
respect to authentication of the holder of the address space and AS
numbers, the procedures should be commensurate with those you
already employ in the maintenance of address (and AS number)
allocation. Note that your organization can choose to require
periodic re-keying consistent with contractual agreements with the
recipient.>
3.3.2. Identification and authentication for re-key after revocation 3.3.2. Identification and authentication for re-key after revocation
<Describe the procedures that will be used to ensure that an Re-key after revocation is effected via a Certificate Issuance
organization requesting a re-key after revocation is the legitimate Request message as described in [up/down]. This digitally signed CMS
holder of the address space and AS numbers in the certificate being message is authenticated using a BPKI certificate associated with
re-keyed. This should also include the method employed for verifying the requester.
PoP of the private key corresponding to the new public key. Note
that there may be different procedures for the case where the
legitimate subject still possesses the original private key as
opposed to the case when it no longer has access to that key. With
respect to authentication of the resource holder, the procedures
should be commensurate with those you already employ in the
maintenance of resource allocation records.>
3.4. Identification and authentication for revocation request 3.4. Identification and authentication for revocation request
<Describe the procedures that will be used to ensure that the An RPKI Subscriber makes an explicit revocation request using the
resource holder requesting revocation is the subject of the protocol defined in [up/down]. Revocation requests in this protocol
certificate (or an authorized representative thereof) to be revoked. are digitally signed CMS messages, and are verified using a public
Note that there may be different procedures for the case where the key bound to an authorized representative via the <Name of Registry>
legitimate subject still possesses the original private key as BPKI.
opposed to the case when the subject no longer has access to that
key. These procedures should be commensurate with those you already
employ in the maintenance of resource holder records.>
Note: If additional IP addresses or AS numbers are being added to When a Subscriber requests an new resource allocation, an existing
an organization's existing allocation, the old certificate need not resource certificate issued to the subscriber is NOT revoked, so
be revoked. Instead, a new certificate may be issued with both the long as the set of resources allocated to the Subscriber did not
old and the new resources and the old key. If IP addresses or AS "shrink," i.e., the new resources are a superset of the old resource
numbers are being removed or if there has been a key compromise, set. However, if a new resource allocation results in "shrinkage" of
then the old certificate will be a revoked (and a re-key will be the set of resources allocated to a Subscriber, this triggers an
performed in the event of a key compromise). A subscriber may implicit revocation of the old resource certificate(s) associated
request that its resource holdings be spread over a set of with that Subscriber.
certificates, rather than consolidating all resources in one
certificate. This may be appropriate if the subscriber wants to
manage his resource allocations as distinct allocations within his
organization.
4. Certificate Life-Cycle Operational Requirements 4. Certificate Life-Cycle Operational Requirements
4.1. Certificate Application 4.1. Certificate Application
4.1.1. Who can submit a certificate application 4.1.1. Who can submit a certificate application
The following entities may submit a certificate application to this The following entities may submit a certificate application to this
CA: CA:
o <Insert if appropriate: "Any NIR or LIR/ISP operating in the o <Insert if appropriate: "Any NIR or LIR/ISP operating in the
geopolitical region served by this registry"> geopolitical region served by this registry">
o Any entity that holds AS numbers or address space assigned by o Any entity that holds AS numbers or address space assigned by
this registry this registry
4.1.2. Enrollment process and responsibilities 4.1.2. Enrollment process and responsibilities
<Describe your enrollment process for issuing certificates both for <Name of Registry> members who are resource holders are enrolled in
initial deployment of the PKI and as an ongoing process. Note that the <Name of Registry> BPKI via the process described in
most of the certificates in this PKI are issued as part of registry [operations-business-pki]. Only a member who holds a certificate
and ISP normal business practices, as an adjunct to address space issued under the BPKI is eligible to make an RPKI certificate
and AS number allocation, and thus a separate application to request request.
a certificate may not be necessary. If so, reference should be made
to where these practices are documented.>
4.2. Certificate application processing 4.2. Certificate application processing
<Describe the certificate request/response standards that you will <A/An Name of Registry> resource holder requests a certificate via a
employ. You should make use of existing standards for certificate Certificate Issuance Request message [up/down], which is
application processing. Relevant standards include RFC 4210, authenticated via the digital signature on the CMS envelope. The
Internet X.509 Public Key Infrastructure Certificate Management certificate used to authenticate the message is issued under the
Protocol (CMP), RFC 2797, Certificate Management Messages over CMS, <Name of Registry> BPKI. <Name of Registry> processes the resource
and RSA Labs standards PKCS #7 and PKCS #10. > request as described in [up/down]. The Certificate Issuance Response
message [up/down] either provides the certificate to the Subscriber,
or provides a response indicating why the request was not fulfilled.
4.2.1. Performing identification and authentication functions 4.2.1. Performing identification and authentication functions
<Describe your practices for identification and authentication of The <Name of Registry> BPKI is used to identify <A/An Name of
certificate applicants. Often, existing practices employed by you Registry> member representative applying for a certificate via a
to identify and authenticate organizations form the basis for certificate issuance request in the up/down protocol. See the <Name
issuance of certificates to these subscribers. Reference can be of Registry> BPKI CPS for additional details [cp-business-pki].
made to documentation of such existing practices.>
4.2.2. Approval or rejection of certificate applications 4.2.2. Approval or rejection of certificate applications
<Describe your practices for approval or rejection of applications The Certificate Issuance Response message [up/down] either provides
and refer to documentation of existing business practices relevant the certificate to the Subscriber, or provides a response indicating
to this process. Note that according to the CP, certificate why the request was not fulfilled. <Describe your practices for
applications will be approved based on the normal business practices approval or rejection of applications and refer to documentation of
of the entity operating the CA, based on the CA's records of address existing business practices relevant to this process. Note that
space and AS number holders. Also, each CA will verify that the according to the CP, certificate applications will be approved based
requester holds the corresponding private key for the public key on the normal business practices of the entity operating the CA,
that will be bound to the certificate the CA issues to the based on the CA's records of address space and AS number holders.
requester.> Also, each CA will verify that the requester holds the corresponding
private key for the public key that will be bound to the certificate
the CA issues to the requester.>
4.2.3. Time to process certificate applications 4.2.3. Time to process certificate applications
<You may declare here your expected time frame for processing <You may declare here your expected time frame for processing
certificate applications.> certificate applications.>
4.3. Certificate issuance 4.3. Certificate issuance
4.3.1. CA actions during certificate issuance 4.3.1. CA actions during certificate issuance
<Describe in this section your procedures for issuance of a A Subscriber generates a draft certificate using the PKCS #10
certificate.> format, as profiled in [RFCyyyy]. This draft certificate is
encapsulated in a CMS message, signed by the requester, and
submitted as a Certificate Issuance Request as described in
[up/down]. The CA verifies the request message as described in
[up/down] and generates a Certificate Issuance Response message.
That message either contains the requested certificate, or provides
a response indicating why the request was not fulfilled.
4.3.2. Notification to subscriber by the CA of issuance of certificate 4.3.2. Notification to subscriber by the CA of issuance of certificate
<Describe your procedure for notification of a subscriber when a a A Subscriber is notified of the issuance of a new certificate by the
certificate has been issued.> Certificate Issuance Response message.
4.3.3. Notification of certificate issuance by the CA to other entities 4.3.3. Notification of certificate issuance by the CA to other entities
[OMITTED] [OMITTED]
4.4. Certificate acceptance 4.4. Certificate acceptance
4.4.1. Conduct constituting certificate acceptance 4.4.1. Conduct constituting certificate acceptance
When a certificate is issued, the CA will place it in the repository When a certificate is issued, the RPKI CA will place it in the
and notify the subscriber. This will be done without subscriber repository. A subject is deemed to have accepted a certificate
review and acceptance. issued by this CA unless the subject explicitly requests revocation
of the certificate after publication in the <Name of Registry> RPKI
repository system, as described in Section 4.9.3
4.4.2. Publication of the certificate by the CA 4.4.2. Publication of the certificate by the CA
Certificates will be published in the Repository system once issued Certificates will be published in the Repository system within 1
following the conduct described in 4.4.1. <Describe your procedures business day of being issued by this CA.
for publication of the approved certificate.>
4.5. Key pair and certificate usage 4.5. Key pair and certificate usage
A summary of the use model for the IP Address and AS Number PKI is A summary of the use model for the RPKI is provided below.
provided below.
4.5.1. Subscriber private key and certificate usage 4.5.1. Subscriber private key and certificate usage
The certificates issued by this registry to resource holders are CA The certificates issued by this registry to resource holders are CA
certificates. The private key associated with each of these certificates. The private key associated with each of these
certificates is used to sign subordinate (CA or EE) certificates and certificates is used to sign subordinate (CA or EE) certificates and
CRLs. A subscriber will issue certificates to any organizations to CRLs. A subscriber will issue certificates to any organizations to
which it allocates IP address space and one or more "shadow" which it allocates resources and one or more EE certificates for use
certificates for use in verifying signatures on ROAs signed by the in verifying signatures on ROAs signed by the subscriber. <If
subscriber. <If appropriate, add "Subscribers that are NIRs issue appropriate, add "Subscribers that are NIRs issue certificates to
certificates to organizations to which they have allocated address organizations to which they have allocated address space or AS
space or AS numbers. Subscribers that are LIRs issue certificates numbers. Subscribers that are LIRs issue certificates to
to organizations to which they have allocated address space."> organizations to which they have allocated address space.">
Subscribers also will issue certificates to operators in support of Subscribers also will issue certificates to operators in support of
repository access control. repository access control.
4.5.2. Relying party public key and certificate usage 4.5.2. Relying party public key and certificate usage
The primary relying parties in this PKI are LIRs/ISPs, who will use The primary relying parties in this PKI are LIRs/ISPs, who will use
shadow certificates to verify ROAs, e.g., in support of generating RPKI EE certificates to verify ROAs and other signed objects, e.g.,
route filters. Repositories will use operator certificates to in support of generating route filters.
verify the authorization of entities to engage in repository
maintenance activities, and thus repositories represent a secondary
type of relying party.
4.6. Certificate renewal 4.6. Certificate renewal
4.6.1. Circumstance for certificate renewal 4.6.1. Circumstance for certificate renewal
As per the CP, a certificate will be processed for renewal based on As per the CP, a certificate will be processed for renewal based on
its expiration date or a renewal request from the certificate its expiration date or a renewal request from the certificate
Subject. The request may be implicit, a side effect of renewing its Subject. The request may be implicit, a side effect of renewing its
resource holding agreement, or may be explicit. If <Name of resource holding agreement, or may be explicit. If <Name of
Registry> initiates the renewal process based on the certificate Registry> initiates the renewal process based on the certificate
skipping to change at page 23, line 8 skipping to change at page 22, line 8
week>, to ensure uninterrupted coverage. week>, to ensure uninterrupted coverage.
Certificate renewal will incorporate the same public key as the Certificate renewal will incorporate the same public key as the
previous certificate, unless the private key has been reported as previous certificate, unless the private key has been reported as
compromised. If a new key pair is being used, the stipulations of compromised. If a new key pair is being used, the stipulations of
Section 4.7 will apply. Section 4.7 will apply.
4.6.2. Who may request renewal 4.6.2. Who may request renewal
The certificate holder or <Name of Registry> may initiate the The certificate holder or <Name of Registry> may initiate the
renewal process. <For the case of the certificate holder, describe renewal process. For the case of the certificate holder, only an
what steps will be taken to verify the identity and authorization of individual to whom a BPKI certificate (see Section 3.2.6) has been
the entity requesting the renewal.> issued may request renewal of an RPKI certificate. Each certificate
issuance request is verified using the BPKI.
4.6.3. Processing certificate renewal requests 4.6.3. Processing certificate renewal requests
<Describe your procedures for handling certificate renewal requests. A Subscriber requests certificate renewal by sending a Certificate
This must include verification that the certificate in question has Issuance Request message [up/down].
not been revoked.>
4.6.4. Notification of new certificate issuance to subscriber 4.6.4. Notification of new certificate issuance to subscriber
<Describe your procedure for notification of new certificate A Subscriber is notified of the issuance of a new certificate via
issuance to the subscriber. This should be consistent with 4.3.2.> the Certificate Issuance Response message, if the Subscriber
initiated the renewal. If <Name of Registry> initiated the renewal
process, the Subscriber is notified by the posting of the renewed
certificate in the <Name of Registry> repository. A Subscriber can
discover a certificate renewed by <Name of Registry> through use of
the List message [up/down].
4.6.5. Conduct constituting acceptance of a renewal certificate 4.6.5. Conduct constituting acceptance of a renewal certificate
When a renewal certificate is issued, the CA will place it in the When a renewal certificate is issued, the CA will place it in the
repository and notify the subscriber. This will be done without repository. A Subscriber is deemed to have accepted a certificate
subscriber review and acceptance. unless the subscriber explicitly requests revocation of the
certificate after publication in the <Name of Registry> RPKI
repository system, as described in Section 4.9.3.
4.6.6. Publication of the renewal certificate by the CA 4.6.6. Publication of the renewal certificate by the CA
<Describe your policy and procedures for publication of a renewed <Name of Registry> will publish a renewal certificate in the <Name
certificate. This should be consistent with 4.4.2.> of Registry> RPKI repository within 1 business day after issuance of
the renewed certificate.
4.6.7. Notification of certificate issuance by the CA to other entities 4.6.7. Notification of certificate issuance by the CA to other entities
[OMITTED] [OMITTED]
4.7. Certificate re-key 4.7. Certificate re-key
4.7.1. Circumstance for certificate re-key 4.7.1. Circumstance for certificate re-key
As per the CP, re-key of a certificate will be performed only when As per the CP, re-key of a certificate will be performed only when
requested, based on: requested, based on:
skipping to change at page 24, line 20 skipping to change at page 23, line 27
Section 5.6 of the Certificate Policy notes that when a CA signs a Section 5.6 of the Certificate Policy notes that when a CA signs a
certificate, the signing key should have a validity period that certificate, the signing key should have a validity period that
exceeds the validity period of the certificate. This places exceeds the validity period of the certificate. This places
additional constraints on when a CA should request a re-key. additional constraints on when a CA should request a re-key.
4.7.2. Who may request certification of a new public key 4.7.2. Who may request certification of a new public key
The holder of the certificate may request a re-key. In addition, The holder of the certificate may request a re-key. In addition,
<Name of Registry> may initiate a re-key based on a verified <Name of Registry> may initiate a re-key based on a verified
compromise report. <Describe what steps will be taken to verify the compromise report. If the Subscriber (certificate Subject) requests
identity and authorization of a subscriber to request a re-key when the rekey, authentication is effected using the <Name of Registry>
the private key has been reported as compromised. Also describe how BPKI. <Describe how a compromise report received from other than a
a compromise report received from other than a subscriber is subscriber is verified.>
verified.>
4.7.3. Processing certificate re-keying requests 4.7.3. Processing certificate re-keying requests
<Describe your process for handling re-keying requests. As per the A Subscriber requests a re-key of a certificate by issuing a
CP, this should be consistent with the process described in Section Certificate Issuance Request message in which the resources are ones
4.3. So reference can be made to that section.> that the Subscriber already holds, but a new public key is provided
in the PKCS #10 portion of the request.
4.7.4. Notification of new certificate issuance to subscriber 4.7.4. Notification of new certificate issuance to subscriber
<Describe your policy regarding notifying the subscriber re: A Subscriber is notified of the issuance of a re-keyed certificate
availability of the new certificate. This should be consistent with via the Certificate Issuance Response message.
the notification process for any new certificate issuance (see
section 4.3.2).>
4.7.5. Conduct constituting acceptance of a re-keyed certificate 4.7.5. Conduct constituting acceptance of a re-keyed certificate
When a re-keyed certificate is issued, the CA will place it in the When a re-keyed certificate is issued, the CA will place it in the
repository and notify the subscriber. This will be done without repository. A subject is deemed to have accepted a certificate
subscriber review and acceptance. issued by this CA unless the subject explicitly requests revocation
of the certificate after publication in the <Name of Registry> RPKI
repository system, as described in Section 4.9.3.
4.7.6. Publication of the re-keyed certificate by the CA 4.7.6. Publication of the re-keyed certificate by the CA
<Describe your policy regarding publication of the new certificate. A re-keyed certificate will be published in the Repository system
This should be consistent with the publication process for any new within 1 business day of being issued by this CA.
certificate (see section 4.4.2).>
4.7.7. Notification of certificate issuance by the CA to other entities 4.7.7. Notification of certificate issuance by the CA to other entities
[OMITTED] [OMITTED]
4.8. Certificate modification 4.8. Certificate modification
4.8.1. Circumstance for certificate modification 4.8.1. Circumstance for certificate modification
As per the CP, modification of a certificate occurs to implement As per the CP, modification of a certificate occurs to implement
changes to the RFC 3779 extension values in a certificate. A changes to the RFC 3779 extension values in a certificate. A
skipping to change at page 25, line 40 skipping to change at page 24, line 45
public key and the same expiration date as the original certificate, public key and the same expiration date as the original certificate,
but with the incidental information corrected and/or the address but with the incidental information corrected and/or the address
space and AS allocations expanded. When previously allocated address space and AS allocations expanded. When previously allocated address
space or AS numbers are to be removed from a certificate, then the space or AS numbers are to be removed from a certificate, then the
old certificate MUST be revoked and a new certificate (reflecting old certificate MUST be revoked and a new certificate (reflecting
the new allocation) issued. the new allocation) issued.
4.8.2. Who may request certificate modification 4.8.2. Who may request certificate modification
The certificate holder or <Name of Registry> may initiate the The certificate holder or <Name of Registry> may initiate the
certificate modification process. <For the case of the certificate certificate modification process. If a certificate holder requests
holder, state here what steps will be taken to verify the identity the modification, the request is authenticated using the <Name of
and authorization of the entity requesting the modification.> Registry> BPKI, as described in [up/down]. <Name of Registry> will
modify a certificate, and revoke the old certificate, if, for
example, a Subscriber fails to renew membership in a timely fashion.
4.8.3. Processing certificate modification requests 4.8.3. Processing certificate modification requests
<Describe your procedures for verification of the modification A certificate can be modified (other than for re-key) only by the
request and procedures for the issuance of a new certificate. These addition or removal or resources. A Subscriber requests certificate
should be consistent with the processes described in Sections 4.2 modification by submitting a Certificate Issuance Request. If the
and 4.3.1.> request contains values for AS and/or (IPv4 or IPv6) address
resource sets that the Subscriber already holds, but which are
different from those in the currently issued certificates, the
request is interpreted as a request for certificate modification.
4.8.4. Notification of modified certificate issuance to subscriber 4.8.4. Notification of modified certificate issuance to subscriber
<Describe your procedure for notification of issuance of a modified A Subscriber is notified of the issuance of a modified certificate
certificate. This should be consistent with the notification by the publication of the certificate in the <Name of Registry> RPKI
process for any new certificate (see section 4.3.2).> repository system.
4.8.5. Conduct constituting acceptance of modified certificate 4.8.5. Conduct constituting acceptance of modified certificate
When a modified certificate is issued, the CA will place it in the When a modified certificate is issued, the CA will place it in the
repository and notify the subscriber. This will be done without repository and notify the subscriber. A subject is deemed to have
subscriber review and acceptance. accepted the modified certificate unless the subject explicitly
requests revocation of the certificate after publication in the
<Name of Registry> RPKI repository system, as described in Section
4.9.3.
4.8.6. Publication of the modified certificate by the CA 4.8.6. Publication of the modified certificate by the CA
<Describe your procedure for publication of a modified certificate. A modified certificate will be published in the <Name of Registry>
This should be consistent with the publication process for any new RPKI Repository system within 1 business day of being issued by this
certificate (see section 4.4.2).> CA.
4.8.7. Notification of certificate issuance by the CA to other entities 4.8.7. Notification of certificate issuance by the CA to other entities
[OMITTED] [OMITTED]
4.9. Certificate revocation and suspension 4.9. Certificate revocation and suspension
4.9.1. Circumstances for revocation 4.9.1. Circumstances for revocation
As per the CP, certificates can be revoked for several reasons. As per the CP, certificates can be revoked for several reasons.
Either <Name of Registry> or the subject may choose to end the Either <Name of Registry> or the subject may choose to end the
skipping to change at page 26, line 44 skipping to change at page 26, line 10
public key in the certificate are no longer associated with the public key in the certificate are no longer associated with the
subject, that too constitutes a basis for revocation. A certificate subject, that too constitutes a basis for revocation. A certificate
also may be revoked due to loss or compromise of the private key also may be revoked due to loss or compromise of the private key
corresponding to the public key in the certificate. Finally, a corresponding to the public key in the certificate. Finally, a
certificate may be revoked in order to invalidate data signed by certificate may be revoked in order to invalidate data signed by
that certificate. that certificate.
4.9.2. Who can request revocation 4.9.2. Who can request revocation
The certificate holder or <Name of Registry> may request a The certificate holder or <Name of Registry> may request a
revocation. <For the case of the certificate holder, describe what revocation. A Subscriber requests certificate revocation using the
steps will be taken to verify the identity and authorization of the Certificate Revocation Request message described in [up/down].
entity requesting the revocation.>
4.9.3. Procedure for revocation request 4.9.3. Procedure for revocation request
<Describe your process for handling a certificate revocation A Subscriber requests certificate revocation using the Certificate
request. This should include: Revocation Request message described in [up/down]. The Certificate
Revocation Response message confirms receipt of the revocation
Procedure to be used by the certificate holder to request a request by <Name of Registry>, and indicates that <Name of Registry>
revocation will include the revoked certificate in a CRL.
Procedure for notification of the certificate holder when the CRL is
published by <Name of Registry>.
4.9.4. Revocation request grace period 4.9.4. Revocation request grace period
A subscriber should request revocation as soon as possible after the A Subscriber should request revocation as soon as possible after the
need for revocation has been identified. need for revocation has been identified.
4.9.5. Time within which CA must process the revocation request 4.9.5. Time within which CA must process the revocation request
<Describe your policy on the time period within which you will <Describe your policy on the time period within which you will
process a revocation request.> process a revocation request.>
4.9.6. Revocation checking requirement for relying parties 4.9.6. Revocation checking requirement for relying parties
As per the CP, a relying party is responsible for acquiring and As per the CP, a relying party is responsible for acquiring and
checking the most recent, scheduled CRL from the issuer of the checking the most recent, scheduled CRL from the issuer of the
certificate, whenever the relying party validates a certificate. certificate, whenever the relying party validates a certificate.
4.9.7. CRL issuance frequency 4.9.7. CRL issuance frequency
<Name of Registry> will publish CRLs approximately every 24 hours. The <Name of Registry> RPKI production CA will publish CRLs
Each CRL will carry a nextScheduledUpdate value and a new CRL will approximately every 24 hours. The <Name of Registry> RPKI offline CA
be published at or before that time. <Name of Registry> will set will publish CRLs on a monthly basis. Each CRL will carry a
the nextScheduledUpdate value when it issues a CRL, to signal when nextScheduledUpdate value and a new CRL will be published at or
the next scheduled CRL will be issued. before that time. <Name of Registry> will set the
nextScheduledUpdate value when it issues a CRL, to signal when the
next scheduled CRL will be issued.
4.9.8. Maximum latency for CRLs 4.9.8. Maximum latency for CRLs
A CRL will be posted to the repository system with minimal delay A CRL will be posted to the repository system with minimal delay
after generation. after generation.
4.9.9. On-line revocation/status checking availability [OMITTED] 4.9.9. On-line revocation/status checking availability [OMITTED]
4.9.10. On-line revocation checking requirements [OMITTED] 4.9.10. On-line revocation checking requirements [OMITTED]
skipping to change at page 28, line 23 skipping to change at page 27, line 23
4.9.13. Circumstances for suspension [OMITTED] 4.9.13. Circumstances for suspension [OMITTED]
4.9.14. Who can request suspension [OMITTED] 4.9.14. Who can request suspension [OMITTED]
4.9.15. Procedure for suspension request [OMITTED] 4.9.15. Procedure for suspension request [OMITTED]
4.9.16. Limits on suspension period [OMITTED] 4.9.16. Limits on suspension period [OMITTED]
4.10. Certificate status services 4.10. Certificate status services
<Name of Registry> does <not> support OCSP. <Name of Registry> does not support OCSP. <Name of Registry> issues
CRLs.
4.10.1. Operational characteristics [OMITTED] 4.10.1. Operational characteristics [OMITTED]
4.10.2. Service availability [OMITTED] 4.10.2. Service availability [OMITTED]
4.10.3. Optional features [OMITTED] 4.10.3. Optional features [OMITTED]
4.11. End of subscription [OMITTED] 4.11. End of subscription [OMITTED]
4.12. Key escrow and recovery [OMITTED] 4.12. Key escrow and recovery [OMITTED]
skipping to change at page 33, line 36 skipping to change at page 32, line 36
6.1.2. Private key delivery to subscriber 6.1.2. Private key delivery to subscriber
<If the procedures in 6.1.1 include providing key pair generation <If the procedures in 6.1.1 include providing key pair generation
services for subscribers, describe the means by which private keys services for subscribers, describe the means by which private keys
are delivered to subscribers in a secure fashion. Otherwise say this are delivered to subscribers in a secure fashion. Otherwise say this
is not applicable.> is not applicable.>
6.1.3. Public key delivery to certificate issuer 6.1.3. Public key delivery to certificate issuer
<Describe the means by which the public keys are delivered to you, Subscribers deliver public keys to the <Name of Registry> RPKI CA by
e.g., electronic submission using a PKCS#10 Certificate Signing use of the up/down protocol as described in [up/down].
Request (CSR). This description should explain how this public key
delivery fits in with the process whereby the subscriber requests IP
address space (and/or AS numbers), authenticates itself, pays for
the resources, etc. The security of the procedures used by a
subscriber to deliver its public key to you need only be
commensurate with the security of the procedures already employed
for management of the IP address space and AS numbers.>
6.1.4. CA public key delivery to relying parties 6.1.4. CA public key delivery to relying parties
CA public keys for all entities other than RIRs are contained in CA public keys for all entities other than RIRs are contained in
certificates issued by other CAs. These certificates plus certificates issued by other CAs. These certificates plus
certificates used to represent inter-RIR transfers of address space certificates used to represent inter-RIR transfers of address space
or AS numbers will be published via a repository system. Relying or AS numbers will be published via a repository system. Relying
parties will download these certificates from this system. Public parties will download these certificates from this system. Public
key values and associated data for the trust anchors (RIRs) will be key values and associated data for the trust anchors (RIRs) will be
distributed out of band, e.g., embedded in path validation software distributed out of band, e.g., embedded in path validation software
that will be made available to the Internet community. that will be made available to the Internet community.
6.1.5. Key sizes 6.1.5. Key sizes
For the <Name of Registry> CA's certificate and shadow CA For the <Name of Registry> offline CA'sand production CA's
certificate, the RSA key size will be 2048 bits. For subscriber certificates, the RSA key size will be 2048 bits. For subscriber
certificates, the RSA keys will be <insert key size -- e.g., 2048 or certificates, the RSA keys will be <insert key size -- e.g., 2048 or
1024 bits. If NIR key size is larger than LIR/ISP/subscriber key 1024 bits. If NIR key size is larger than LIR/ISP/subscriber key
size, describe each independently.> size, describe each independently.>
6.1.6. Public key parameters generation and quality checking 6.1.6. Public key parameters generation and quality checking
The RSA algorithm [RSA] is used in this PKI with the public exponent The RSA algorithm [RSA] is used in this PKI with the public exponent
(e) F4 (65,537). (e) F4 (65,537).
<If the procedures in 6.1.1 include subscriber key pair generation, <If the procedures in 6.1.1 include subscriber key pair generation,
skipping to change at page 34, line 41 skipping to change at page 33, line 38
For <Name of Registry>'s CA certificates, the keyCertSign and For <Name of Registry>'s CA certificates, the keyCertSign and
cRLSign bits will be set TRUE. All other bits (including cRLSign bits will be set TRUE. All other bits (including
digitalSignature) will be set FALSE, and the extension will be digitalSignature) will be set FALSE, and the extension will be
marked critical. marked critical.
6.2. Private Key Protection and Cryptographic Module Engineering 6.2. Private Key Protection and Cryptographic Module Engineering
Controls Controls
6.2.1. Cryptographic module standards and controls 6.2.1. Cryptographic module standards and controls
The <Name of Registry> CA employs a cryptographic module evaluated The <Name of Registry> RPKI CA employs a cryptographic module
under FIPS 140-2, at level 3 [FIPS]. evaluated under FIPS 140-2, at level 3 [FIPS].
6.2.2. Private key (n out of m) multi-person control 6.2.2. Private key (n out of m) multi-person control
There will be private key <insert here n> out of <insert here m> There will be private key <insert here n> out of <insert here m>
multi-person control. multi-person control.
6.2.3. Private key escrow 6.2.3. Private key escrow
No private key escrow procedures are required for this PKI. No private key escrow procedures are required for this PKI.
skipping to change at page 35, line 19 skipping to change at page 34, line 19
done under the same multi-party control as is used for controlling done under the same multi-party control as is used for controlling
the original private key. (2) At least one copy should be kept at the original private key. (2) At least one copy should be kept at
an off-site location for disaster recovery purposes.> an off-site location for disaster recovery purposes.>
6.2.5. Private key archival 6.2.5. Private key archival
See sections 6.2.3 and 6.2.4 See sections 6.2.3 and 6.2.4
6.2.6. Private key transfer into or from a cryptographic module 6.2.6. Private key transfer into or from a cryptographic module
The private keys for <Name of Registry>'s CA and shadow CA will be The private keys for <Name of Registry>'s offline CA and production
generated by the cryptographic module specified in 6.2.1. The CA will be generated by the cryptographic module specified in 6.2.1.
private keys will never leave the module except in encrypted form The private keys will never leave the module except in encrypted
for backup and/or transfer to a new module. form for backup and/or transfer to a new module.
6.2.7. Private key storage on cryptographic module 6.2.7. Private key storage on cryptographic module
The private keys for <Name of Registry>'s CA will be stored in the The private keys for <Name of Registry>'s CA will be stored in the
cryptographic module and will be protected from unauthorized use in cryptographic module and will be protected from unauthorized use in
accordance with the FIPS 140-2 requirements applicable to the accordance with the FIPS 140-2 requirements applicable to the
module. (See [FIPS]) module. (See [FIPS])
6.2.8. Method of activating private key 6.2.8. Method of activating private key
skipping to change at page 35, line 51 skipping to change at page 34, line 51
will be stored securely when not in use. will be stored securely when not in use.
6.2.10. Method of destroying private key 6.2.10. Method of destroying private key
<Describe the method used for destroying your CA's private key, <Describe the method used for destroying your CA's private key,
e.g., when it is superseded. This will depend on the particular e.g., when it is superseded. This will depend on the particular
module.> module.>
6.2.11. Cryptographic Module Rating 6.2.11. Cryptographic Module Rating
The cryptographic module will be certified FIPS 140-2, at level 3 The cryptographic module used by the <Name of Registry> production
[FIPS]. CA will be certified FIPS 140-2, at level 3 [FIPS].
6.3. Other aspects of key pair management 6.3. Other aspects of key pair management
6.3.1. Public key archival 6.3.1. Public key archival
Because this PKI does not support non-repudiation, there is no need Because this PKI does not support non-repudiation, there is no need
to archive public keys. to archive public keys.
6.3.2. Certificate operational periods and key pair usage periods 6.3.2. Certificate operational periods and key pair usage periods
skipping to change at page 37, line 20 skipping to change at page 36, line 20
<Describe any system development controls that you will apply to the <Describe any system development controls that you will apply to the
PKI systems, e.g., use of Trusted System Development Methodology PKI systems, e.g., use of Trusted System Development Methodology
(TSDM) Level 2.> (TSDM) Level 2.>
6.6.2. Security management controls 6.6.2. Security management controls
<Describe the security management controls that will be used for the <Describe the security management controls that will be used for the
software and equipment employed by the CA. These security measures software and equipment employed by the CA. These security measures
should be commensurate with those used for the systems used by the should be commensurate with those used for the systems used by the
CAs for managing and allocating IP address and AS number resources.> CAs for managing and allocating RPKI resources.>
6.6.3. Life cycle security controls 6.6.3. Life cycle security controls
<Describe how the equipment (hardware and software) used for PKI <Describe how the equipment (hardware and software) used for PKI
functions will be procured, installed, maintained, and updated. functions will be procured, installed, maintained, and updated.
This should be done in a fashion commensurate with the way in which This should be done in a fashion commensurate with the way in which
equipment for the management and allocation of IP address space and equipment for the management and allocation of IP address space and
AS numbers is handled. > AS numbers is handled. >
6.7. Network security controls 6.7. Network security controls
skipping to change at page 38, line 7 skipping to change at page 37, line 7
operation. These should be commensurate with the network security operation. These should be commensurate with the network security
controls employed for the computers used for managing allocation of controls employed for the computers used for managing allocation of
IP addresses and AS numbers.> IP addresses and AS numbers.>
6.8. Time-stamping 6.8. Time-stamping
The PKI in question does not make use of time stamping. The PKI in question does not make use of time stamping.
7. Certificate and CRL Profiles 7. Certificate and CRL Profiles
Please refer to the Certificate and CRL Profile [RESCERT]. Please refer to the Certificate and CRL Profile [RFCyyyy].
7.1. Certificate profile [OMITTED] 7.1. Certificate profile [OMITTED]
7.1.1. Version number(s) [OMITTED] 7.1.1. Version number(s) [OMITTED]
7.1.2. Certificate extensions [OMITTED] 7.1.2. Certificate extensions [OMITTED]
7.1.2.1. Required certificate extensions [OMITTED] 7.1.2.1. Required certificate extensions [OMITTED]
7.1.2.2. Deprecated certificate extensions [OMITTED] 7.1.2.2. Deprecated certificate extensions [OMITTED]
skipping to change at page 40, line 11 skipping to change at page 39, line 11
8.5. Actions taken as a result of deficiency 8.5. Actions taken as a result of deficiency
8.6. Communication of results 8.6. Communication of results
9. Other Business And Legal Matters 9. Other Business And Legal Matters
<The sections below are optional. Fill them in as appropriate for <The sections below are optional. Fill them in as appropriate for
your organization. Note that the manner in which you manage your your organization. Note that the manner in which you manage your
business and legal matters for this PKI should be commensurate with business and legal matters for this PKI should be commensurate with
the way in which you manage business and legal matters for the the way in which you manage business and legal matters for the
allocation of IP address and AS numbers.> allocation of RPKI resources.>
9.1. Fees 9.1. Fees
9.1.1. Certificate issuance or renewal fees 9.1.1. Certificate issuance or renewal fees
9.1.2. Fees for other services (if applicable) 9.1.2. Fees for other services (if applicable)
9.1.3. Refund policy 9.1.3. Refund policy
9.2. Financial responsibility 9.2. Financial responsibility
skipping to change at page 43, line 50 skipping to change at page 42, line 50
13.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3280] Housley, R., Polk, W. Ford, W., Solo, D., "Internet [RFC3280] Housley, R., Polk, W. Ford, W., Solo, D., "Internet
X.509 Public Key Infrastructure Certificate and Certificate X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile", BCP 14, RFC 2119, March 1997. Revocation List (CRL) Profile", BCP 14, RFC 2119, March 1997.
[CP] Seo, K., Watro, R., Kong, D., and Kent, S., "Certificate [RFCxxxx] Seo, K., Watro, R., Kong, D., and Kent, S. ,
Policy for the Internet IP Address and AS Number PKI", draft- "Certificate Policy for the Resource PKI (RPKI)", work in
ietf-sidr-cp, July 2007 (work in progress). progress, February 2008.
[RESCERT] Huston, G., Loomans, R., Michaelson, G., "A Profile for [RFCyyyy] Huston, G., Loomans, R., Michaelson, G., "A Profile for
X.509 PKIX Resource Certificates", draft-ietf-sidr-res-certs, X.509 PKIX Resource Certificates", work in progress, November
June 2007 (work in progress). 2007.
[up/down] Houston, G., Loomis, R., Ellacott, B., Austein, R., "A
Protocol for Provisioning Resource Certificates," January
2008.
13.2. Informative References 13.2. Informative References
[BGP4] Y. Rekhter, T. Li (editors), A Border Gateway Protocol 4 [BGP4] Y. Rekhter, T. Li (editors), A Border Gateway Protocol 4
(BGP-4). IETF RFC 1771, March 1995. (BGP-4). IETF RFC 1771, March 1995.
[cps-business-pki] <Certification Practice Statement (CPS) for
this registry's business PKI -- to be filled in>
[FIPS] Federal Information Processing Standards Publication 140-2 [FIPS] Federal Information Processing Standards Publication 140-2
(FIPS PUB 140-2), "Security Requirements for Cryptographic (FIPS PUB 140-2), "Security Requirements for Cryptographic
Modules", Information Technology Laboratory, National Modules", Information Technology Laboratory, National
Institute of Standards and Technology, May 25, 2001. Institute of Standards and Technology, May 25, 2001.
[operations-business-pki] <Document or pointer to document
describing the operations of this registry's business PKI --
to be filled in>
[RSA] Rivest, R., Shamir, A., and Adelman, L. M. 1978. A method for [RSA] Rivest, R., Shamir, A., and Adelman, L. M. 1978. A method for
obtaining digital signatures and public-key cryptosystems. obtaining digital signatures and public-key cryptosystems.
Commun. ACM 21, 2 (Feb.), 120-126. Commun. ACM 21, 2 (Feb.), 120-126.
Author's Addresses Author's Addresses
Stephen Kent Stephen Kent
BBN Technologies BBN Technologies
10 Moulton Street 10 Moulton Street
Cambridge MA 02138 Cambridge MA 02138
skipping to change at page 45, line 42 skipping to change at page 45, line 18
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
 End of changes. 112 change blocks. 
500 lines changed or deleted 506 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/