--- 1/draft-ietf-sidr-publication-01.txt 2012-03-12 22:13:59.890671882 +0100 +++ 2/draft-ietf-sidr-publication-02.txt 2012-03-12 22:13:59.930671778 +0100 @@ -1,20 +1,20 @@ Network Working Group S. Weiler Internet-Draft A. Sonalker Intended status: Standards Track SPARTA, Inc. -Expires: January 12, 2012 R. Austein - ISC - July 11, 2011 +Expires: September 13, 2012 R. Austein + Dragon Research Labs + March 12, 2012 A Publication Protocol for the Resource Public Key Infrastructure (RPKI) - draft-ietf-sidr-publication-01 + draft-ietf-sidr-publication-02 Abstract This document defines a protocol for publishing Resource Public Key Infrastructure (RPKI) objects. Even though the RPKI will have many participants issuing certificates and creating other objects, it is operationally useful to consolidate the publication of those objects. This document provides the protocol for doing so. Status of this Memo @@ -25,25 +25,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 12, 2012. + This Internet-Draft will expire on September 13, 2012. Copyright Notice - Copyright (c) 2011 IETF Trust and the persons identified as the + Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -56,33 +56,44 @@ 2. Context . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Protocol Specification . . . . . . . . . . . . . . . . . . . . 4 3.1. Common Details . . . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Common XML Message Format . . . . . . . . . . . . . . 4 3.2. Control Sub-Protocol . . . . . . . . . . . . . . . . . . . 5 3.2.1. Config Object . . . . . . . . . . . . . . . . . . . . 5 3.2.2. Client Object . . . . . . . . . . . . . . . . . . . . 5 3.3. Publication Sub-Protocol . . . . . . . . . . . . . . . . . 6 3.4. Error handling . . . . . . . . . . . . . . . . . . . . . . 7 3.5. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . 7 - 4. Operational Considerations . . . . . . . . . . . . . . . . . . 9 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 - 7.2. Informative References . . . . . . . . . . . . . . . . . . 10 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 + 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + 4.1. Config Set Query and Response . . . . . . . . . . . . . . 9 + 4.2. Config Get Query and Response . . . . . . . . . . . . . . 10 + 4.3. Example 3: Client Create Query and Reply . . . . . . . . . 11 + 4.4. Example 4: Client Set Query and Reply . . . . . . . . . . 12 + 4.5. Example 5: Client Get Query and Reply . . . . . . . . . . 13 + 4.6. Example 6: Client List Query and Reply . . . . . . . . . . 13 + 4.7. Example 7: Client Destroy Query and Reply . . . . . . . . 14 + 4.8. Example 8: Publish Query and Reply . . . . . . . . . . . . 14 + 4.9. Example 9: Withdraw Query and Reply . . . . . . . . . . . 15 + 4.10. Example 10: Report Error Reply . . . . . . . . . . . . . . 16 + 5. Operational Considerations . . . . . . . . . . . . . . . . . . 16 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 + 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 + 8.2. Informative References . . . . . . . . . . . . . . . . . . 19 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 1. Introduction This document assumes a working knowledge of the Resource Public Key Infrastructure (RPKI), which is intended to support improved routing - security on the Internet. [I-D.ietf-sidr-arch] + security on the Internet. [RFC6480] In order to make participation in the RPKI easier, it is helpful to have a few consolidated repositories for RPKI objects, thus saving every participant from the cost of maintaining a new service. Similarly, relying parties using the RPKI objects will find it faster and more reliable to retrieve the necessary set from a smaller number of repositories. These consolidated RPKI object repositories will in many cases be outside the administrative scope of the organization issuing a given @@ -139,22 +150,21 @@ corresponding response. A message exchange commences with the client initiating an HTTP POST with content type of "application/rpki-publication", with the message object as the body. The server's response will similarly be the body of the response with a content type of "application/ rpki-publication". The content of the POST and the server's response will be a well- formed Cryptographic Message Syntax (CMS) [RFC5652] object with OID = - 1.2.840.113549.1.7.2 as described in Section 3.1 of - [I-D.ietf-sidr-rescerts-provisioning]. + 1.2.840.113549.1.7.2 as described in Section 3.1 of [RFC6492]. 3.1.1. Common XML Message Format The XML schema for this protocol (including both subprotocols) is below in Section 3.5. Both subprotocols use the same basic XML message format, which looks like: object only has one data element that can be set: the bpki_crl. This is used by the publication server when authenticating clients. 3.2.2. Client Object Unlike the object, the object represents one - client authorized to use the publication server. There may well be - more than one object on each publication server. Again, - its use is typically restricted to the respository operator. + client authorized to use the publication server. There may be more + than one object on each publication server. Again, its use + is typically restricted to the respository operator. The object supports five actions: "create", "set", "get", "list", and "destroy". Each client has a "client_handle" attribute, which is used in responses and must be specified in "create", "set", "get", or "destroy" actions. Payload data which can be configured in a object include: o base_uri (attribute): This attribute represents the base URI below which the client will be allowed to publish data. Additional @@ -231,21 +241,21 @@ pathological cross-certification cases which require a two- certificate chain due to issuer name conflicts. When being used, issuing order is that the bpki_glue certificate should be the issuer of the bpki_cert certificate. Otherwise, it should be issued by the publication engine's bpki_ta certificate. Since this is an optional use certificate, it may be left unset if not needed. 3.3. Publication Sub-Protocol - The sub-publication protocol requests publication or withdrawal from + The publication sub-protocol requests publication or withdrawal from publication of RPKI objects. The publication protocol uses a common message format to request publication of any RPKI object. This format was chosen specifically to allow this protocol to accommodate new types of RPKI objects without needing changes to this protocol. Both the and objects have a payload of an optional tag and a URI. The query also contains the DER object to be published, encoded in Base64. @@ -370,29 +380,372 @@ withdraw_reply |= element withdraw { tag?, uri } # element error = xsd:token { maxLength="1024" } report_error_reply = element report_error { tag?, attribute error_code { error }, xsd:string { maxLength="512000" }? } -4. Operational Considerations +4. Examples - Placeholder section to talk about nesting children under parents in - the same repository, to allow for a single rsync to fetch both - (observing that the rsync setup times tends to dominate over the sync - time). And, more distressingly, talk about the access control - impacts of that nesting. + Following are various queries and the corresponding replies for the + RPKI publication protocol -5. IANA Considerations +4.1. Config Set Query and Response + + A. Config "Set" Query + + + + MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vyd + GlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1Wq + AOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljVqX/ + CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDWAV6U + G6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ16aF5f + ubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ftF8zZAF + pDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHSIbjiy0W + uuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoisHKkehy4 + Y0GySdj98fV+OuiRTH9vt/M= + + + + + B. Config "Set" Reply + + + + + +4.2. Config Get Query and Response + + A. Config "Get" Query + + + + + + B. Config "Get" Reply + + + + MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vyd + GlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1Wq + AOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljVqX/ + CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDWAV6U + G6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ16aF5f + ubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ftF8zZAF + pDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHSIbjiy0W + uuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoisHKkehy4 + Y0GySdj98fV+OuiRTH9vt/M= + + + + +4.3. Example 3: Client Create Query and Reply + + A. Client "Create" Query + + + + + MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAgB + gNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1Mz + EwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmljYXR + lIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArKYU + tJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79pWf3GI + dnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuEPPOG8U + N17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShLi8GKgVd + qb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8mAkGf79Tb + a0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZePr79j7LK/h + kZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNVHRMEBTADAQ + H/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNVHSMEGDAWgBT + DEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOCAQEAWWkNcW6S + 1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0n96P7CUHOWP8Q + Bb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHhMW+Dv0PhIKu2Cg + D4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep6LAlFj62qqaIJzN + eQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdHYyMNrG2xMOtIC7T4 + +IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6hdEq3ORv7RZMJNYqv + 1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ== + + + + + B. Client "Create" Reply + + + + + +4.4. Example 4: Client Set Query and Reply + + A. Client "Set" Query + + + + + MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAgB + gNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1Mz + EwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmljYXR + lIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArKYU + tJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79pWf3GI + dnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuEPPOG8U + N17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShLi8GKgVd + qb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8mAkGf79Tb + a0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZePr79j7LK/h + kZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNVHRMEBTADAQ + H/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNVHSMEGDAWgBT + DEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOCAQEAWWkNcW6S + 1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0n96P7CUHOWP8Q + Bb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHhMW+Dv0PhIKu2Cg + D4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep6LAlFj62qqaIJzN + eQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdHYyMNrG2xMOtIC7T4 + +IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6hdEq3ORv7RZMJNYqv + 1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ== + + + + + B. Client "Set" Reply + + + + + +4.5. Example 5: Client Get Query and Reply + + A. Client "Get" Query + + + + + + B. Client "Get" Reply + + + + + MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAgB + gNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1Mz + EwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmljYXR + lIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArKYU + tJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79pWf3GI + dnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuEPPOG8U + N17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShLi8GKgVd + qb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8mAkGf79Tb + a0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZePr79j7LK/h + kZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNVHRMEBTADAQ + H/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNVHSMEGDAWgBT + DEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOCAQEAWWkNcW6S + 1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0n96P7CUHOWP8Q + Bb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHhMW+Dv0PhIKu2Cg + D4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep6LAlFj62qqaIJzN + eQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdHYyMNrG2xMOtIC7T4 + +IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6hdEq3ORv7RZMJNYqv + 1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ== + + + + +4.6. Example 6: Client List Query and Reply + + A. Client "List" Query + + + + + + B. Client "List" Reply + + + + MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAgB + gNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1Mz + EwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmljYXR + lIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArKYU + tJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79pWf3GI + dnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuEPPOG8U + N17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShLi8GKgVd + qb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8mAkGf79Tb + a0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZePr79j7LK/h + kZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNVHRMEBTADAQ + H/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNVHSMEGDAWgBT + DEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOCAQEAWWkNcW6S + 1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0n96P7CUHOWP8Q + Bb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHhMW+Dv0PhIKu2Cg + D4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep6LAlFj62qqaIJzN + eQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdHYyMNrG2xMOtIC7T4 + +IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6hdEq3ORv7RZMJNYqv + 1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ== + + + + +4.7. Example 7: Client Destroy Query and Reply + + A. Client "Destroy" Query + + + + + + B. Client "Destroy" Reply + + + + + +4.8. Example 8: Publish Query and Reply + + A. Publish Query + + + MIIE+jCCA+KgAwIBAgIBDTANBgkqhkiG9w0BAQsFADAzMTEwLwYDVQQDEyhER + jRBODAxN0U2NkE5RTkxNzJFNDYxMkQ4Q0Y0QzgzRjIzOERFMkEzMB4XDTA4MD + UyMjE4MDUxMloXDTA4MDUyNDE3NTQ1M1owMzExMC8GA1UEAxMoOEZCODIxOEY + wNkU1MEFCNzAyQTdEOTZEQzhGMENEQ0Q4MjhGN0YxNzCCASIwDQYJKoZIhvcN + AQEBBQADggEPADCCAQoCggEBAMeziKp0k5nP7v6SZoNsXIMQYRgNtC6Fr/9Xm + /1yQHomiPqHUk47rHhGojYiK5AhkrwoYhkH4UjJl2iwklDYczXuaBU3F5qrKl + Z4aZnjIxdlP7+hktVpeApL6yuJTUAYeC3UIxnLDVdD6phydZ/FOQluffiNDjz + teCCvoyOUatqt8WB+oND6LToHp028g1YUYLHG6mur0dPdcHOVXLSmUDuZ1HDz + 1nDuYvIVKjB/MpH9aW9XeaQ6ZFIlZVPwuuvI2brR+ThH7Gv27GL/o8qFdC300 + VQfoTZ+rKPGDE8K1cI906BL4kiwx9z0oiDcE96QCz+B0vsjc9mGaA1jgAxlXW + sCAwEAAaOCAhcwggITMB0GA1UdDgQWBBSPuCGPBuUKtwKn2W3I8M3Ngo9/FzA + fBgNVHSMEGDAWgBTfSoAX5mqekXLkYS2M9Mg/I43iozBVBgNVHR8ETjBMMEqg + SKBGhkRyc3luYzovL2xvY2FsaG9zdDo0NDAwL3Rlc3RiZWQvUklSLzEvMzBxQ + UYtWnFucEZ5NUdFdGpQVElQeU9ONHFNLmNybDBFBggrBgEFBQcBAQQ5MDcwNQ + YIKwYBBQUHMAKGKXJzeW5jOi8vbG9jYWxob3N0OjQ0MDAvdGVzdGJlZC9XT01 + CQVQuY2VyMBgGA1UdIAEB/wQOMAwwCgYIKwYBBQUHDgIwDwYDVR0TAQH/BAUw + AwEB/zAOBgNVHQ8BAf8EBAMCAQYwgZsGCCsGAQUFBwELBIGOMIGLMDQGCCsGA + QUFBzAFhihyc3luYzovL2xvY2FsaG9zdDo0NDAwL3Rlc3RiZWQvUklSL1IwLz + EvMFMGCCsGAQUFBzAKhkdyc3luYzovL2xvY2FsaG9zdDo0NDAwL3Rlc3RiZWQ + vUklSL1IwLzEvajdnaGp3YmxDcmNDcDlsdHlQRE56WUtQZnhjLm1uZjAaBggr + BgEFBQcBCAEB/wQLMAmgBzAFAgMA/BUwPgYIKwYBBQUHAQcBAf8ELzAtMCsEA + gABMCUDAwAKAzAOAwUAwAACAQMFAcAAAiAwDgMFAsAAAiwDBQDAAAJkMA0GCS + qGSIb3DQEBCwUAA4IBAQCEhuH7jtI2PJY6+zwv306vmCuXhtu9Lr2mmRw2ZEr + B8EMcb5xypMrNqMoKeu14K2x4a4RPJkK4yAThM81FPNRsU5mM0acIRnAPtxjH + vPME7PHN2w2nGLASRsZmaa+b8A7SSOxVcFURazENztppsolHeTpm0cpLItK7m + NpudUg1JGuFo94VLf1MnE2EqARG1vTsNhel/SM/UvOArCCOBvf0Gz7kSuupDS + Z7qx+LiDmtEsLdbGNQBiYPbLrDk41PHrxdx28qIj7ejZkRzNFw/3pi8/XK281 + h8zeHoFVu6ghRPy5dbOA4akX/KG6b8XIx0iwPYdLiDbdWFbtTdPcXBauY + + + + B. Publish Reply + + + + + +4.9. Example 9: Withdraw Query and Reply + + A. Withdraw Query + + + + + B. Withdraw Reply + + + + + +4.10. Example 10: Report Error Reply + + A. Report Error Reply 1 + + + text string + + + B. Report Error Reply 2 + + + + + +5. Operational Considerations + + There are two basic options open to the repository operator as to how + the publication tree is laid out. The first option is simple: each + publication client is given its own directory one level below the top + of the rcynic module, and there is no overlap between the publication + spaces used by different clients. For example: + + rsync://example.org/rpki/Alice/ + rsync://example.org/rpki/Bob/ + rsync://example.org/rpki/Carol/ + + This has the advantage of being very easy for the publication + operator to manage, but has the drawback of making it difficult for + relying parties to fetch published objects both safely and as + efficiently as possible. + + Given that the mandatory-to-implement retrieval protocol for relying + parties is rsync, a more efficient repository structure would be one + which minimized the number of rsync fetches required. One such + structure would be one in which the publication directories for + subjects were placed underneath the publication directories of their + issuers: since the normal synchronization tree walk is top-down, this + can significantly reduce the total number of rsync connections + required to synchronize. For example: + + rsync://example.org/rpki/Alice/ + rsync://example.org/rpki/Alice/Bob/ + rsync://example.org/rpki/Alice/Bob/Carol/ + + Preliminary measurement suggests that, in the case of large numbers + of small publication directories, the time needed to set up and tear + down individual rsync connections becomes significant, and that a + properly optimized tree structure can reduce synchronization time by + an order of magnitude. + + The more complex tree structure does require careful attention to the + base_uri attribute values when setting up clients. In the example + above, assuming that Alice issues to Bob who in turn issues to Carol, + Alice has ceded control of a portion of her publication space to Bob, + who has in turn ceded a portion of that to Carol, and the base_uri + attributes in the setup messages should reflect this. + + The details of how the repository operator determines that Alice has + given Bob permission to nest Bob's publication directory under + Alice's is outside the scope of this protocol. + +6. IANA Considerations IANA is asked to register the application/rpki-publication MIME media type as follows: MIME media type name: application MIME subtype name: rpki-publication Required parameters: None Optional parameters: None Encoding considerations: binary Security considerations: Carries an RPKI Publication Protocol @@ -402,60 +755,71 @@ Applications which use this media type: HTTP Additional information: Magic number(s): None File extension(s): Macintosh File Type Code(s): Person & email address to contact for further information: Rob Austein Intended usage: COMMON Author/Change controller: Rob Austein -6. Security Considerations +7. Security Considerations -7. References + The RPKI publication protocol and the data it publishes use entirely + separate PKIs for authentication. The published data is + authenticated within the RPKI, and this protocol has nothing to do + with that authentication, nor does it require that the published + objects be valid in the RPKI. The publication protocol uses a + separate Business PKI (BPKI) to authenticate its messages. -7.1. Normative References + Each of the RPKI publication protocol messages is CMS-signed. + Because of that protection at the application layer, this protocol + does not require the use of HTTPS or other transport security + mechanisms. - [I-D.ietf-sidr-rescerts-provisioning] - Huston, G., Loomans, R., Ellacott, B., and R. Austein, "A - Protocol for Provisioning Resource Certificates", - draft-ietf-sidr-rescerts-provisioning-10 (work in - progress), June 2011. + Compromise of a publication server, perhaps through mismanagement of + BPKI keys, could lead to a denial-of-service attack on the RPKI. An + attacker gaining access to BPKI keys could use this protocol delete + (withdraw) RPKI objects, leading to routing changes or failures. + Accordingly, as in most PKIs, good key management practices are + important. + +8. References +8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, September 2009. -7.2. Informative References + [RFC6492] Huston, G., Loomans, R., Ellacott, B., and R. Austein, "A + Protocol for Provisioning Resource Certificates", + RFC 6492, February 2012. - [I-D.ietf-sidr-arch] - Lepinski, M. and S. Kent, "An Infrastructure to Support - Secure Internet Routing", draft-ietf-sidr-arch-13 (work in - progress), May 2011. +8.2. Informative References + + [RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support + Secure Internet Routing", RFC 6480, February 2012. Authors' Addresses Samuel Weiler SPARTA, Inc. 7110 Samuel Morse Drive Columbia, Maryland 21046 US Email: weiler@tislabs.com Anuja Sonalker SPARTA, Inc. 7110 Samuel Morse Drive Columbia, Maryland 21046 US Email: Anuja.Sonalker@sparta.com Rob Austein - ISC - 950 Charter Street - Redwood City, CA 94063 - USA + Dragon Research Labs - Email: sra@isc.org + Email: sra@hactrn.net