draft-ietf-sidr-publication-03.txt   draft-ietf-sidr-publication-04.txt 
Network Working Group S. Weiler Network Working Group S. Weiler
Internet-Draft SPARTA, Inc. Internet-Draft SPARTA, Inc.
Intended status: Standards Track A. Sonalker Intended status: Standards Track A. Sonalker
Expires: January 17, 2013 Battelle Memorial Institute Expires: April 23, 2014 Battelle Memorial Institute
R. Austein R. Austein
Dragon Research Labs Dragon Research Labs
July 16, 2012 October 20, 2013
A Publication Protocol for the Resource Public Key Infrastructure (RPKI) A Publication Protocol for the Resource Public Key Infrastructure (RPKI)
draft-ietf-sidr-publication-03 draft-ietf-sidr-publication-04
Abstract Abstract
This document defines a protocol for publishing Resource Public Key This document defines a protocol for publishing Resource Public Key
Infrastructure (RPKI) objects. Even though the RPKI will have many Infrastructure (RPKI) objects. Even though the RPKI will have many
participants issuing certificates and creating other objects, it is participants issuing certificates and creating other objects, it is
operationally useful to consolidate the publication of those objects. operationally useful to consolidate the publication of those objects.
This document provides the protocol for doing so. This document provides the protocol for doing so.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 17, 2013. This Internet-Draft will expire on April 23, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Context . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Context . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Specification . . . . . . . . . . . . . . . . . . . . 4 3. Protocol Specification . . . . . . . . . . . . . . . . . . . 3
3.1. Common Details . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Common Details . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Common XML Message Format . . . . . . . . . . . . . . 4 3.1.1. Common XML Message Format . . . . . . . . . . . . . . 4
3.2. Control Sub-Protocol . . . . . . . . . . . . . . . . . . . 5 3.2. Control Sub-Protocol . . . . . . . . . . . . . . . . . . 5
3.2.1. Config Object . . . . . . . . . . . . . . . . . . . . 5 3.2.1. Config Object . . . . . . . . . . . . . . . . . . . . 5
3.2.2. Client Object . . . . . . . . . . . . . . . . . . . . 5 3.2.2. Client Object . . . . . . . . . . . . . . . . . . . . 5
3.3. Publication Sub-Protocol . . . . . . . . . . . . . . . . . 6 3.3. Publication Sub-Protocol . . . . . . . . . . . . . . . . 6
3.4. Error handling . . . . . . . . . . . . . . . . . . . . . . 7 3.4. Error handling . . . . . . . . . . . . . . . . . . . . . 7
3.5. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . 7 3.5. XML Schema . . . . . . . . . . . . . . . . . . . . . . . 7
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Config Set Query and Response . . . . . . . . . . . . . . 9 4.1. <config/> Set Query . . . . . . . . . . . . . . . . . . . 11
4.2. Config Get Query and Response . . . . . . . . . . . . . . 10 4.2. <config/> Set Reply . . . . . . . . . . . . . . . . . . . 12
4.3. Example 3: Client Create Query and Reply . . . . . . . . . 11 4.3. <config/> Get Query . . . . . . . . . . . . . . . . . . . 12
4.4. Example 4: Client Set Query and Reply . . . . . . . . . . 12 4.4. <config/> Get Reply . . . . . . . . . . . . . . . . . . . 13
4.5. Example 5: Client Get Query and Reply . . . . . . . . . . 13 4.5. <client/> Create Query . . . . . . . . . . . . . . . . . 13
4.6. Example 6: Client List Query and Reply . . . . . . . . . . 13 4.6. <client/> Create Reply . . . . . . . . . . . . . . . . . 14
4.7. Example 7: Client Destroy Query and Reply . . . . . . . . 14 4.7. <client/> Set Query . . . . . . . . . . . . . . . . . . . 14
4.8. Example 8: Publish Query and Reply . . . . . . . . . . . . 14 4.8. <client/> Set Reply . . . . . . . . . . . . . . . . . . . 15
4.9. Example 9: Withdraw Query and Reply . . . . . . . . . . . 15 4.9. <client/> Get Query . . . . . . . . . . . . . . . . . . . 15
4.10. Example 10: Report Error Reply . . . . . . . . . . . . . . 16 4.10. <client/> Get Reply . . . . . . . . . . . . . . . . . . . 15
5. Operational Considerations . . . . . . . . . . . . . . . . . . 16 4.11. <client/> List Query . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4.12. <client/> List Reply . . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 4.13. <client/> Destroy Query . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.14. <client/> Destroy Reply . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 4.15. <publish/> Query . . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 4.16. <publish/> Reply . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 4.17. <withdraw/> Query . . . . . . . . . . . . . . . . . . . . 18
4.18. <withdraw/> Reply . . . . . . . . . . . . . . . . . . . . 19
4.19. <report_error/> With Text . . . . . . . . . . . . . . . . 19
4.20. <report_error/> Without Text . . . . . . . . . . . . . . 19
5. Operational Considerations . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.1. Normative References . . . . . . . . . . . . . . . . . . 21
8.2. Informative References . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
This document assumes a working knowledge of the Resource Public Key This document assumes a working knowledge of the Resource Public Key
Infrastructure (RPKI), which is intended to support improved routing Infrastructure (RPKI), which is intended to support improved routing
security on the Internet. [RFC6480] security on the Internet. [RFC6480]
In order to make participation in the RPKI easier, it is helpful to In order to make participation in the RPKI easier, it is helpful to
have a few consolidated repositories for RPKI objects, thus saving have a few consolidated repositories for RPKI objects, thus saving
every participant from the cost of maintaining a new service. every participant from the cost of maintaining a new service.
skipping to change at page 4, line 30 skipping to change at page 4, line 27
This section discusses details that the two subprotocols have in This section discusses details that the two subprotocols have in
common, including the transport and CMS wrappers. common, including the transport and CMS wrappers.
Both protocols use a simple request/response interaction. The client Both protocols use a simple request/response interaction. The client
passes a request to the server, and the server generates a passes a request to the server, and the server generates a
corresponding response. corresponding response.
A message exchange commences with the client initiating an HTTP POST A message exchange commences with the client initiating an HTTP POST
with content type of "application/rpki-publication", with the message with content type of "application/rpki-publication", with the message
object as the body. The server's response will similarly be the body object as the body. The server's response will similarly be the body
of the response with a content type of "application/ of the response with a content type of "application/rpki-
rpki-publication". publication".
The content of the POST and the server's response will be a well- The content of the POST and the server's response will be a well-
formed Cryptographic Message Syntax (CMS) [RFC5652] object with OID = formed Cryptographic Message Syntax (CMS) [RFC5652] object with OID =
1.2.840.113549.1.7.2 as described in Section 3.1 of [RFC6492]. 1.2.840.113549.1.7.2 as described in Section 3.1 of [RFC6492].
3.1.1. Common XML Message Format 3.1.1. Common XML Message Format
The XML schema for this protocol (including both subprotocols) is The XML schema for this protocol (including both subprotocols) is
below in Section 3.5. Both subprotocols use the same basic XML below in Section 3.5. Both subprotocols use the same basic XML
message format, which looks like: message format, which looks like:
<?xml version='1.0' encoding='us-ascii'?> <?xml version='1.0' encoding='us-ascii'?>
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/"
version="2" version="2"
type="message type"> type="message type">
[one or more PDUs] [one or more PDUs]
</msg> </msg>
version: version: The value of this attribute is the version of this
The value of this attribute is the version of this protocol. protocol. This document describes version 2.
This document describes version 2.
type: type: The possible values of this attribute are "reply" and "query".
The possible values of this attribute are "reply" and "query".
A query PDU may be one of four types: config_query, client_query, A query PDU may be one of four types: config_query, client_query,
publish_query, or withdraw_query. The first two are used by the publish_query, or withdraw_query. The first two are used by the
control sub-protocol, the latter two by the publication sub-protocol. control sub-protocol, the latter two by the publication sub-protocol.
A reply PDU may be one of five types: config_reply, client_reply, A reply PDU may be one of five types: config_reply, client_reply,
publish_reply, withdraw_reply, or report_error_reply. publish_reply, withdraw_reply, or report_error_reply.
Each of these PDUs may include an optional tag to facilitate bulk Each of these PDUs may include an optional tag to facilitate bulk
operation. If a tag is set in a query PDU, the corresponding operation. If a tag is set in a query PDU, the corresponding
skipping to change at page 6, line 10 skipping to change at page 5, line 45
3.2.2. Client Object 3.2.2. Client Object
Unlike the <config/> object, the <client/> object represents one Unlike the <config/> object, the <client/> object represents one
client authorized to use the publication server. There may be more client authorized to use the publication server. There may be more
than one <client/> object on each publication server. Again, its use than one <client/> object on each publication server. Again, its use
is typically restricted to the respository operator. is typically restricted to the respository operator.
The <client/> object supports five actions: "create", "set", "get", The <client/> object supports five actions: "create", "set", "get",
"list", and "destroy". Each client has a "client_handle" attribute, "list", and "destroy". Each client has a "client_handle" attribute,
which is used in responses and must be specified in "create", "set", which is used in responses and must be specified in "create", "set",
"get", or "destroy" actions. The "create" and "set" actions take "get", or "destroy" actions. The "create" and "set" actions have an
optional boolean attributes. The only attribute currently defined is optional flag to clear CMS-timestamp-based replay protection, to
used to clear CMS-timestamp-based replay protection, to allow allow recovery from misconfigured clocks.
recovery from misconfigured clocks.
Payload data which can be configured in a <client/> object include: Payload data which can be configured in a <client/> object include:
o base_uri (attribute): This attribute represents the base URI below o base_uri (attribute): This attribute represents the base URI below
which the client will be allowed to publish data. Additional which the client will be allowed to publish data. Additional
constraints may be imposed by the publication server in certain constraints may be imposed by the publication server in certain
cases, for e.g., a child publishing directly under its parent. cases, for e.g., a child publishing directly under its parent.
o bpki_cert (element): This represents the X.509 BPKI CA certificate o bpki_cert (element): This represents the X.509 BPKI CA certificate
for this client. This should be used as part of the certificate for this client. This should be used as part of the certificate
chain when validating incoming CMS messages. Two valid approaches chain when validating incoming CMS messages. Two valid approaches
exist. If the optional bpki_glue certificate is being used, then exist. If the optional bpki_glue certificate is being used, then
the bpki_cert certificate should be issued by the bpki_glue the bpki_cert certificate should be issued by the bpki_glue
certificate; otherwise, the bpki_cert certificate should be issued certificate; otherwise, the bpki_cert certificate should be issued
by the publication engine's bpki_ta certificate. by the publication engine's bpki_ta certificate.
o bpki_glue (element): This is an additional (optional) X.509 o bpki_glue (element): This is an additional (optional) type of
certificate for this client. It may be used in certain X.509 certificate for this client. It may be used in certain
pathological cross-certification cases which require a two- pathological cross-certification cases which require a two-
certificate chain due to issuer name conflicts. When being used, certificate chain due to issuer name conflicts. When being used,
issuing order is that the bpki_glue certificate should be the issuing order is that the bpki_glue certificate should be the
issuer of the bpki_cert certificate. Otherwise, it should be issuer of the bpki_cert certificate. Otherwise, it should be
issued by the publication engine's bpki_ta certificate. Since issued by the publication engine's bpki_ta certificate. Since
this is an optional use certificate, it may be left unset if not this is an optional use certificate, it may be left unset if not
needed. needed.
3.3. Publication Sub-Protocol 3.3. Publication Sub-Protocol
skipping to change at page 7, line 48 skipping to change at page 7, line 43
occurred. occurred.
The body of the <report_error/> element itself is an optional text The body of the <report_error/> element itself is an optional text
string; if present, this is debugging information. string; if present, this is debugging information.
3.5. XML Schema 3.5. XML Schema
The following is a RelaxNG compact form schema describing the The following is a RelaxNG compact form schema describing the
Publication Protocol. Publication Protocol.
default namespace = "http://www.hactrn.net/uris/rpki/publication-spec/" # $Id: rpki-publication.rnc 2601 2013-10-18 19:21:28Z sra $
# RelaxNG schema for RPKI publication protocol.
# Top level PDU default namespace =
start = element msg { "http://www.hactrn.net/uris/rpki/publication-spec/"
attribute version { "2" } ,
( ( attribute type { "query" }, query_elt*) |
(attribute type { "reply" }, reply_elt*))
}
# PDUs allowed in a query # This is version 2 of the protocol.
query_elt = ( config_query | client_query | publish_query |
withdraw_query )
# PDUs allowed in a reply version = "2"
reply_elt = ( config_reply | client_reply | publish_reply | # Top level PDU is either a query or a reply.
withdraw_reply | report_error_reply )
# Tag attributes for bulk operations start = element msg {
tag = attribute tag { xsd:token {maxLength="1024" } } attribute version { version } ,
( ( attribute type { "query" }, query_elt* ) |
( attribute type { "reply" }, reply_elt* ) )
}
# Base64 encoded DER stuff # PDUs allowed in a query.
base64 = xsd:base64Binary
# Publication URLs query_elt |= config_query
uri_t = xsd:anyURI { maxLength="4096" } query_elt |= client_query
uri = attribute uri { uri_t } query_elt |= publish_query
query_elt |= withdraw_query
# Handles on remote objects (replaces passing raw SQL IDs). NB: # PDUs allowed in a reply.
# Unlike the up-down protocol, handles in this protocol allow
# "/" as a hierarchy delimiter.
object_handle = xsd:string {
maxLength="255" pattern="[\-_A-Za-z0-9/]*" }
# <config/> element (use restricted to repository operator) reply_elt |= config_reply
# config_handle attribute: create, list, and destroy commands reply_elt |= client_reply
# omitted deliberately. reply_elt |= publish_reply
config_payload = (element bpki_crl { base64 }?) reply_elt |= withdraw_reply
config_query |= element config { attribute action { "set" }, tag?, reply_elt |= report_error_reply
config_payload }
config_reply |= element config { attribute action { "set" }, tag? }
config_query |= element config { attribute action { "get" }, tag? }
config_reply |= element config { attribute action { "get" }, tag?,
config_payload }
# <client/> element (use restricted to repository operator) # Tag attributes for bulk operations.
client_handle = attribute client_handle { object_handle }
client_payload = (attribute base_uri { uri_t }?, element bpki_cert {
base64 }?, element bpki_glue { base64 }?)
client_bool = attribute clear_replay_protection { "yes" }?
client_query |= element client { attribute action { "create" }, tag = attribute tag { xsd:token { maxLength="1024" } }
tag?, client_handle, client_bool, client_payload }
client_reply |= element client { attribute action { "create" },
tag?, client_handle }
client_query |= element client { attribute action { "set" }, tag?,
client_handle, client_bool, client_payload }
client_reply |= element client { attribute action { "set" }, tag?,
client_handle }
client_query |= element client { attribute action { "get" }, tag?,
client_handle }
client_reply |= element client { attribute action { "get" }, tag?,
client_handle, client_payload }
client_query |= element client { attribute action { "list" }, tag? }
client_reply |= element client { attribute action { "list" }, tag?,
client_handle, client_payload }
client_query |= element client { attribute action { "destroy" },
tag?, client_handle }
client_reply |= element client { attribute action { "destroy" },
tag?, client_handle }
# <publish/> element # Base64 encoded DER stuff.
publish_query |= element publish { tag?, uri, base64 }
publish_reply |= element publish { tag?, uri }
# <withdraw/> element base64 = xsd:base64Binary
withdraw_query |= element withdraw { tag?, uri }
withdraw_reply |= element withdraw { tag?, uri }
# <report_error/> element # Publication URLs.
error = xsd:token { maxLength="1024" }
report_error_reply = element report_error {
tag?,
attribute error_code { error },
xsd:string { maxLength="512000" }?
}
4. Examples uri_t = xsd:anyURI { maxLength="4096" }
uri = attribute uri { uri_t }
Following are various queries and the corresponding replies for the # Handles on remote objects (replaces passing raw SQL IDs).
RPKI publication protocol
4.1. Config Set Query and Response object_handle = xsd:string {
maxLength = "255"
pattern="[\-_A-Za-z0-9/]*"
}
A. Config "Set" Query # Error codes.
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/"
type="query" version="2">
<config action="set">
<bpki_crl>
MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vyd
GlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1Wq
AOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljVqX/
CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDWAV6U
G6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ16aF5f
ubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ftF8zZAF
pDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHSIbjiy0W
uuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoisHKkehy4
Y0GySdj98fV+OuiRTH9vt/M=
</bpki_crl>
</config>
</msg>
B. Config "Set" Reply error = xsd:token { maxLength="1024" }
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" # <config/> element (use restricted to repository operator)
type="reply" version="2"> config_payload = (element bpki_crl { base64 }?)
<config action="set"/>
</msg>
4.2. Config Get Query and Response config_query |= element config {
attribute action { "set" },
tag?,
config_payload
}
A. Config "Get" Query config_reply |= element config {
attribute action { "set" },
tag?
}
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" config_query |= element config {
type="query" version="2"> attribute action { "get" },
<config action="get"/> tag?
</msg> }
B. Config "Get" Reply config_reply |= element config {
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" attribute action { "get" },
type="reply" version="2"> tag?,
<config action="get"> config_payload
<bpki_crl> }
MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vyd
GlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1Wq # <client/> element (use restricted to repository operator)
AOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljVqX/
CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDWAV6U client_handle = attribute client_handle { object_handle }
G6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ16aF5f
ubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ftF8zZAF client_payload = (
pDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHSIbjiy0W attribute base_uri { uri_t }?,
uuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoisHKkehy4 element bpki_cert { base64 }?,
Y0GySdj98fV+OuiRTH9vt/M= element bpki_glue { base64 }?
)
client_clear_replay = (
attribute clear_replay_protection { "yes" }?
)
client_query |= element client {
attribute action { "create" },
tag?,
client_handle,
client_clear_replay,
client_payload
}
client_reply |= element client {
attribute action { "create" },
tag?,
client_handle
}
client_query |= element client {
attribute action { "set" },
tag?,
client_handle,
client_clear_replay,
client_payload
}
client_reply |= element client {
attribute action { "set" },
tag?,
client_handle
}
client_query |= element client {
attribute action { "get" },
tag?,
client_handle
}
client_reply |= element client {
attribute action { "get" },
tag?,
client_handle,
client_payload
}
client_query |= element client {
attribute action { "list" },
tag?
}
client_reply |= element client {
attribute action { "list" },
tag?,
client_handle,
client_payload
}
client_query |= element client {
attribute action { "destroy" },
tag?,
client_handle
}
client_reply |= element client {
attribute action { "destroy" },
tag?,
client_handle
}
# <publish/> element
publish_query |= element publish {
tag?,
uri,
base64
}
publish_reply |= element publish {
tag?,
uri
}
# <withdraw/> element
withdraw_query |= element withdraw {
tag?,
uri
}
withdraw_reply |= element withdraw {
tag?,
uri
}
# <report_error/> element
report_error_reply = element report_error {
tag?,
attribute error_code { error },
xsd:string { maxLength="512000" }?
}
4. Examples
Following are examples of various queries and the corresponding
replies for the RPKI publication protocol
4.1. <config/> Set Query
<msg
type="query"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<config
action="set">
<bpki_crl>
MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vy
dGlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1
WqAOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljV
qX/CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDW
AV6UG6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ1
6aF5fubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ft
F8zZAFpDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHS
Ibjiy0WuuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoi
sHKkehy4Y0GySdj98fV+OuiRTH9vt/M=
</bpki_crl> </bpki_crl>
</config> </config>
</msg> </msg>
4.3. Example 3: Client Create Query and Reply 4.2. <config/> Set Reply
A. Client "Create" Query <msg
type="reply"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<config
action="set"/>
</msg>
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" 4.3. <config/> Get Query
version="2" type="query">
<client action="create" client_handle="3"
base_uri="rsync://wombat.invalid/">
<bpki_cert>
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==
</bpki_cert>
</client>
</msg>
B. Client "Create" Reply <msg
type="query"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<config
action="get"/>
</msg>
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" 4.4. <config/> Get Reply
version="2" type="reply">
<client action="create" client_handle="3"/>
</msg>
4.4. Example 4: Client Set Query and Reply <msg
type="reply"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<config
action="get">
<bpki_crl>
MIIBezBlAgEBMA0GCSqGSIb3DQEBCwUAMCMxITAfBgNVBAMTGFRlc3QgQ2Vy
dGlmaWNhdGUgcHViZCBUQRcNMDgwNjAyMjE0OTQ1WhcNMDgwNzAyMjE0OTQ1
WqAOMAwwCgYDVR0UBAMCAQEwDQYJKoZIhvcNAQELBQADggEBAFWCWgBl4ljV
qX/CHo+RpqYtvmKMnjPVflMXUB7i28RGP4DAq4l7deDU7Q82xEJyE4TXMWDW
AV6UG6uUGum0VHWOcj9ohqyiZUGfOsKg2hbwkETm8sAENOsi1yNdyKGk6jZ1
6aF5fubxQqZa1pdGCSac1/ZYC5sLLhEz3kmz+B9z9mXFVc5TgAh4dN3Gy5ft
F8zZAFpDGnS4biCnRVqhGv6R0Lh/5xmii+ZU6kNDhbeMsjJg+ZOmtN+wMeHS
Ibjiy0WuuaZ3k2xSh0C94anrHBZAvvCRhbazjR0Ef5OMZ5lcllw3uO8IHuoi
sHKkehy4Y0GySdj98fV+OuiRTH9vt/M=
</bpki_crl>
</config>
</msg>
A. Client "Set" Query 4.5. <client/> Create Query
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="query"> type="query"
<client action="set" client_handle="3"> version="2"
<bpki_glue> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAgB <client
gNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1Mz action="create"
EwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmljYXR base_uri="rsync://wombat.invalid/"
lIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArKYU client_handle="3">
tJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79pWf3GI <bpki_cert>
dnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuEPPOG8U MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAg
N17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShLi8GKgVd BgNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1
qb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8mAkGf79Tb MzEwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmlj
a0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZePr79j7LK/h YXRlIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
kZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNVHRMEBTADAQ rKYUtJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79p
H/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNVHSMEGDAWgBT Wf3GIdnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuE
DEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOCAQEAWWkNcW6S PPOG8UN17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShL
1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0n96P7CUHOWP8Q i8GKgVdqb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8m
Bb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHhMW+Dv0PhIKu2Cg AkGf79Tba0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZeP
D4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep6LAlFj62qqaIJzN r79j7LK/hkZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNV
eQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdHYyMNrG2xMOtIC7T4 HRMEBTADAQH/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNV
+IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6hdEq3ORv7RZMJNYqv HSMEGDAWgBTDEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOC
1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ== AQEAWWkNcW6S1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0
</bpki_glue> n96P7CUHOWP8QBb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHh
</client> MW+Dv0PhIKu2CgD4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep
</msg> 6LAlFj62qqaIJzNeQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdH
YyMNrG2xMOtIC7T4+IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6
hdEq3ORv7RZMJNYqv1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ==
</bpki_cert>
</client>
</msg>
B. Client "Set" Reply 4.6. <client/> Create Reply
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="reply"
<client action="set" client_handle="3"/> version="2"
</msg> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="create"
client_handle="3"/>
</msg>
4.5. Example 5: Client Get Query and Reply 4.7. <client/> Set Query
A. Client "Get" Query <msg
type="query"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="set"
client_handle="3">
<bpki_cert>
MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAg
BgNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1
MzEwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmlj
YXRlIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
rKYUtJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79p
Wf3GIdnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuE
PPOG8UN17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShL
i8GKgVdqb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8m
AkGf79Tba0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZeP
r79j7LK/hkZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNV
HRMEBTADAQH/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNV
HSMEGDAWgBTDEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOC
AQEAWWkNcW6S1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0
n96P7CUHOWP8QBb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHh
MW+Dv0PhIKu2CgD4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep
6LAlFj62qqaIJzNeQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdH
YyMNrG2xMOtIC7T4+IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6
hdEq3ORv7RZMJNYqv1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ==
</bpki_cert>
</client>
</msg>
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" 4.8. <client/> Set Reply
version="2" type="query">
<client action="get" client_handle="3"/>
</msg>
B. Client "Get" Reply <msg
type="reply"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="set"
client_handle="3"/>
</msg>
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" 4.9. <client/> Get Query
version="2" type="reply">
<client action="get" client_handle="3"
base_uri="rsync://wombat.invalid/">
<bpki_cert>
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==
</bpki_cert>
</client>
</msg>
4.6. Example 6: Client List Query and Reply <msg
type="query"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="get"
client_handle="3"/>
</msg>
A. Client "List" Query 4.10. <client/> Get Reply
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="query"> type="reply"
<client action="list"/> version="2"
</msg> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="get"
base_uri="rsync://wombat.invalid/"
client_handle="3">
<bpki_cert>
MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAg
BgNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1
MzEwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmlj
YXRlIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
rKYUtJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79p
Wf3GIdnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuE
PPOG8UN17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShL
i8GKgVdqb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8m
AkGf79Tba0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZeP
r79j7LK/hkZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNV
HRMEBTADAQH/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNV
HSMEGDAWgBTDEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOC
AQEAWWkNcW6S1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0
n96P7CUHOWP8QBb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHh
MW+Dv0PhIKu2CgD4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep
6LAlFj62qqaIJzNeQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdH
YyMNrG2xMOtIC7T4+IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6
hdEq3ORv7RZMJNYqv1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ==
</bpki_cert>
</client>
</msg>
B. Client "List" Reply 4.11. <client/> List Query
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/"
version="2" type="reply">
<client action="list" client_handle="3">
<bpki_cert>
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==
</bpki_cert>
</client>
</msg>
4.7. Example 7: Client Destroy Query and Reply <msg
type="query"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="list"/>
</msg>
A. Client "Destroy" Query 4.12. <client/> List Reply
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="query"> type="reply"
<client action="destroy" client_handle="3"/> version="2"
</msg> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="list"
client_handle="3">
<bpki_cert>
MIIDGzCCAgOgAwIBAgIJAKi+/+wUhQlxMA0GCSqGSIb3DQEBBQUAMCQxIjAg
BgNVBAMTGVRlc3QgQ2VydGlmaWNhdGUgQm9iIFJvb3QwHhcNMDcwODAxMTk1
MzEwWhcNMDcwODMxMTk1MzEwWjAkMSIwIAYDVQQDExlUZXN0IENlcnRpZmlj
YXRlIEJvYiBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
rKYUtJaM5PH5917SG2ACc7iBYdQO2HYyu8Gb6i9Q2Gxc3cWEX7RTBvgOL79p
Wf3GIdnoupzMnoZVtY3GUx2G/0WkmLui2TCeDhcfXdQ4rcp8J3V/6ESj+yuE
PPOG8UN17mUKKgujrch6ZvgCDO9AyOK/uXu+ABQXTPsn2pVe2EVh3V004ShL
i8GKgVdqb/rW/6GTg0Xb/zLT6WWMuT++6sXTlztJdQYkRamJvKfQDU1naC8m
AkGf79Tba0xyBGAUII0GfREY6t4/+NAP2Yyb3xNlBqcJoTov0JfNKHZcCZeP
r79j7LK/hkZxxip+Na9xDpE+oQRV+DRukCRJdiqg+wIDAQABo1AwTjAMBgNV
HRMEBTADAQH/MB0GA1UdDgQWBBTDEsXJe6pjAQD4ULlB7+GMDBlimTAfBgNV
HSMEGDAWgBTDEsXJe6pjAQD4ULlB7+GMDBlimTANBgkqhkiG9w0BAQUFAAOC
AQEAWWkNcW6S1tKKqtzJsdfhjJiAAPQmOXJskv0ta/8f6Acgcum1YieNdtT0
n96P7CUHOWP8QBb91JzeewR7b6WJLwb1Offs3wNq3kk75pJe89r4XY39EZHh
MW+Dv0PhIKu2CgD4LeyH1FVTQkF/QObGEmkn+s+HTsuzd1l2VLwcP1Smsqep
6LAlFj62qqaIJzNeQ9NVkBqtkygnYlBOkaBTHfQTux3jYNpEo8JJB5e/WFdH
YyMNrG2xMOtIC7T4+IOHgT8PgrNhaeDg9ctewj0X8Qi9nI9nXeinicLX8vj6
hdEq3ORv7RZMJNYqv1HQ3wUE2B7fCPFv7EUwzaCds1kgRQ==
</bpki_cert>
</client>
</msg>
B. Client "Destroy" Reply 4.13. <client/> Destroy Query
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="query"
<client action="destroy" client_handle="3"/> version="2"
</msg> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<client
action="destroy"
client_handle="3"/>
</msg>
4.8. Example 8: Publish Query and Reply 4.14. <client/> Destroy Reply
A. Publish Query <msg
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" type="reply"
version="2" type="query"> version="2"
<publish uri="rsync://wombat.invalid/testbed/RIR/1/j7ghjwblCr xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
cCp9ltyPDNzYKPfxc.cer"> <client
MIIE+jCCA+KgAwIBAgIBDTANBgkqhkiG9w0BAQsFADAzMTEwLwYDVQQDEyhER action="destroy"
jRBODAxN0U2NkE5RTkxNzJFNDYxMkQ4Q0Y0QzgzRjIzOERFMkEzMB4XDTA4MD client_handle="3"/>
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
</publish>
</msg> </msg>
B. Publish Reply 4.15. <publish/> Query
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="query"
<publish uri="rsync://wombat.invalid/testbed/RIR/1/j7ghjwblCr version="2"
cCp9ltyPDNzYKPfxc.cer"/> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
</msg> <publish
uri="rsync://wombat.invalid/Alice/blCrcCp9ltyPDNzYKPfxc.cer">
MIIE+jCCA+KgAwIBAgIBDTANBgkqhkiG9w0BAQsFADAzMTEwLwYDVQQDEyhE
RjRBODAxN0U2NkE5RTkxNzJFNDYxMkQ4Q0Y0QzgzRjIzOERFMkEzMB4XDTA4
MDUyMjE4MDUxMloXDTA4MDUyNDE3NTQ1M1owMzExMC8GA1UEAxMoOEZCODIx
OEYwNkU1MEFCNzAyQTdEOTZEQzhGMENEQ0Q4MjhGN0YxNzCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAMeziKp0k5nP7v6SZoNsXIMQYRgNtC6F
r/9Xm/1yQHomiPqHUk47rHhGojYiK5AhkrwoYhkH4UjJl2iwklDYczXuaBU3
F5qrKlZ4aZnjIxdlP7+hktVpeApL6yuJTUAYeC3UIxnLDVdD6phydZ/FOQlu
ffiNDjzteCCvoyOUatqt8WB+oND6LToHp028g1YUYLHG6mur0dPdcHOVXLSm
UDuZ1HDz1nDuYvIVKjB/MpH9aW9XeaQ6ZFIlZVPwuuvI2brR+ThH7Gv27GL/
o8qFdC300VQfoTZ+rKPGDE8K1cI906BL4kiwx9z0oiDcE96QCz+B0vsjc9mG
aA1jgAxlXWsCAwEAAaOCAhcwggITMB0GA1UdDgQWBBSPuCGPBuUKtwKn2W3I
8M3Ngo9/FzAfBgNVHSMEGDAWgBTfSoAX5mqekXLkYS2M9Mg/I43iozBVBgNV
HR8ETjBMMEqgSKBGhkRyc3luYzovL2xvY2FsaG9zdDo0NDAwL3Rlc3RiZWQv
UklSLzEvMzBxQUYtWnFucEZ5NUdFdGpQVElQeU9ONHFNLmNybDBFBggrBgEF
BQcBAQQ5MDcwNQYIKwYBBQUHMAKGKXJzeW5jOi8vbG9jYWxob3N0OjQ0MDAv
dGVzdGJlZC9XT01CQVQuY2VyMBgGA1UdIAEB/wQOMAwwCgYIKwYBBQUHDgIw
DwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMCAQYwgZsGCCsGAQUFBwEL
BIGOMIGLMDQGCCsGAQUFBzAFhihyc3luYzovL2xvY2FsaG9zdDo0NDAwL3Rl
c3RiZWQvUklSL1IwLzEvMFMGCCsGAQUFBzAKhkdyc3luYzovL2xvY2FsaG9z
dDo0NDAwL3Rlc3RiZWQvUklSL1IwLzEvajdnaGp3YmxDcmNDcDlsdHlQRE56
WUtQZnhjLm1uZjAaBggrBgEFBQcBCAEB/wQLMAmgBzAFAgMA/BUwPgYIKwYB
BQUHAQcBAf8ELzAtMCsEAgABMCUDAwAKAzAOAwUAwAACAQMFAcAAAiAwDgMF
AsAAAiwDBQDAAAJkMA0GCSqGSIb3DQEBCwUAA4IBAQCEhuH7jtI2PJY6+zwv
306vmCuXhtu9Lr2mmRw2ZErB8EMcb5xypMrNqMoKeu14K2x4a4RPJkK4yATh
M81FPNRsU5mM0acIRnAPtxjHvPME7PHN2w2nGLASRsZmaa+b8A7SSOxVcFUR
azENztppsolHeTpm0cpLItK7mNpudUg1JGuFo94VLf1MnE2EqARG1vTsNhel
/SM/UvOArCCOBvf0Gz7kSuupDSZ7qx+LiDmtEsLdbGNQBiYPbLrDk41PHrxd
x28qIj7ejZkRzNFw/3pi8/XK281h8zeHoFVu6ghRPy5dbOA4akX/KG6b8XIx
0iwPYdLiDbdWFbtTdPcXBauY
</publish>
</msg>
4.9. Example 9: Withdraw Query and Reply 4.16. <publish/> Reply
A. Withdraw Query <msg
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" type="reply"
version="2" type="query"> version="2"
<withdraw uri="rsync://wombat.invalid/testbed/RIR/1/j7ghjwblCr xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
cCp9ltyPDNzYKPfxc.cer"/> <publish
</msg> uri="rsync://wombat.invalid/Alice/blCrcCp9ltyPDNzYKPfxc.cer"/>
</msg>
B. Withdraw Reply 4.17. <withdraw/> Query
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="query"
<withdraw uri="rsync://wombat.invalid/testbed/RIR/1/j7ghjwblCr version="2"
cCp9ltyPDNzYKPfxc.cer"/> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
</msg> <withdraw
uri="rsync://wombat.invalid/Alice/blCrcCp9ltyPDNzYKPfxc.cer"/>
4.10. Example 10: Report Error Reply </msg>
A. Report Error Reply 1 4.18. <withdraw/> Reply
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="reply"
<report_error error_code="your_hair_is_on_fire">text string</ version="2"
report_error> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
</msg> <withdraw
uri="rsync://wombat.invalid/Alice/blCrcCp9ltyPDNzYKPfxc.cer"/>
</msg>
B. Report Error Reply 2 4.19. <report_error/> With Text
<msg xmlns="http://www.hactrn.net/uris/rpki/publication-spec/" <msg
version="2" type="reply"> type="reply"
<report_error error_code="your_hair_is_on_fire"/> version="2"
</msg> xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<report_error
error_code="your_hair_is_on_fire">
Shampooing with sterno again, are we?
</report_error>
</msg>
4.20. <report_error/> Without Text
<msg
type="reply"
version="2"
xmlns="http://www.hactrn.net/uris/rpki/publication-spec/">
<report_error
error_code="your_hair_is_on_fire"/>
</msg>
5. Operational Considerations 5. Operational Considerations
There are two basic options open to the repository operator as to how 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 the publication tree is laid out. The first option is simple: each
publication client is given its own directory one level below the top publication client is given its own directory one level below the top
of the rcynic module, and there is no overlap between the publication of the rcynic module, and there is no overlap between the publication
spaces used by different clients. For example: spaces used by different clients. For example:
rsync://example.org/rpki/Alice/ rsync://example.org/rpki/Alice/
skipping to change at page 18, line 5 skipping to change at page 20, line 46
The details of how the repository operator determines that Alice has The details of how the repository operator determines that Alice has
given Bob permission to nest Bob's publication directory under given Bob permission to nest Bob's publication directory under
Alice's is outside the scope of this protocol. Alice's is outside the scope of this protocol.
6. IANA Considerations 6. IANA Considerations
IANA is asked to register the application/rpki-publication MIME media IANA is asked to register the application/rpki-publication MIME media
type as follows: type as follows:
MIME media type name: application MIME media type name: application
MIME subtype name: rpki-publication MIME subtype name: rpki-publication
Required parameters: None Required parameters: None
Optional parameters: None Optional parameters: None
Encoding considerations: binary Encoding considerations: binary
Security considerations: Carries an RPKI Publication Protocol Security considerations: Carries an RPKI Publication Protocol
Message, as defined in this document. Message, as defined in this document.
Interoperability considerations: None Interoperability considerations: None
Published specification: This document Published specification: This document
Applications which use this media type: HTTP Applications which use this media type: HTTP
Additional information: Additional information:
Magic number(s): None Magic number(s): None
File extension(s): File extension(s):
Macintosh File Type Code(s): Macintosh File Type Code(s):
Person & email address to contact for further information: Person & email address to contact for further information:
Rob Austein <sra@hactrn.net> Rob Austein <sra@hactrn.net>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: Rob Austein <sra@hactrn.net> Author/Change controller: Rob Austein <sra@hactrn.net>
7. Security Considerations 7. Security Considerations
The RPKI publication protocol and the data it publishes use entirely The RPKI publication protocol and the data it publishes use entirely
separate PKIs for authentication. The published data is separate PKIs for authentication. The published data is
authenticated within the RPKI, and this protocol has nothing to do authenticated within the RPKI, and this protocol has nothing to do
with that authentication, nor does it require that the published with that authentication, nor does it require that the published
objects be valid in the RPKI. The publication protocol uses a objects be valid in the RPKI. The publication protocol uses a
separate Business PKI (BPKI) to authenticate its messages. separate Business PKI (BPKI) to authenticate its messages.
skipping to change at page 19, line 4 skipping to change at page 21, line 39
mechanisms. mechanisms.
Compromise of a publication server, perhaps through mismanagement of Compromise of a publication server, perhaps through mismanagement of
BPKI keys, could lead to a denial-of-service attack on the RPKI. An 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 attacker gaining access to BPKI keys could use this protocol delete
(withdraw) RPKI objects, leading to routing changes or failures. (withdraw) RPKI objects, leading to routing changes or failures.
Accordingly, as in most PKIs, good key management practices are Accordingly, as in most PKIs, good key management practices are
important. important.
8. References 8. References
8.1. Normative References 8.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", RFC 2119, BCP 14, March 1997.
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", RFC
RFC 5652, September 2009. 5652, STD 70, September 2009.
[RFC6492] Huston, G., Loomans, R., Ellacott, B., and R. Austein, "A [RFC6492] Huston, G., Loomans, R., Ellacott, B., and R. Austein, "A
Protocol for Provisioning Resource Certificates", Protocol for Provisioning Resource Certificates", RFC
RFC 6492, February 2012. 6492, February 2012.
8.2. Informative References 8.2. Informative References
[RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support [RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support
Secure Internet Routing", RFC 6480, February 2012. Secure Internet Routing", RFC 6480, February 2012.
Authors' Addresses Authors' Addresses
Samuel Weiler Samuel Weiler
SPARTA, Inc. SPARTA, Inc.
7110 Samuel Morse Drive 7110 Samuel Morse Drive
Columbia, Maryland 21046 Columbia, Maryland 21046
US US
Email: weiler@tislabs.com Email: weiler@tislabs.com
Anuja Sonalker Anuja Sonalker
Battelle Memorial Institute Battelle Memorial Institute
Columbia, Maryland 21046
US
Email: sonalkera@battelle.org Email: sonalkera@battelle.org
Rob Austein Rob Austein
Dragon Research Labs Dragon Research Labs
Email: sra@hactrn.net Email: sra@hactrn.net
 End of changes. 81 change blocks. 
407 lines changed or deleted 571 lines changed or added

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