Skip to main content

Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties
draft-ietf-sidrops-rp-06

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: rfc-editor@rfc-editor.org, sidrops@ietf.org, Nathalie Trenaman <nathalie@ripe.net>, nathalie@ripe.net, warren@kumari.net, draft-ietf-sidrops-rp@ietf.org, sidrops-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Document Action: 'Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties' to Informational RFC (draft-ietf-sidrops-rp-06.txt)

The IESG has approved the following document:
- 'Requirements for Resource Public Key Infrastructure (RPKI) Relying
   Parties'
  (draft-ietf-sidrops-rp-06.txt) as Informational RFC

This document is the product of the SIDR Operations Working Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rp/


Ballot Text

Technical Summary

This document provides a single reference point for requirements for Relying Party (RP) software for use in the Resource Public Key Infrastructure (RPKI) in the context of securing Internet routing.
 It cites requirements that appear in several RPKI RFCs, making it easier for implementers to become aware of these requirements that are segmented with orthogonal functionalities.

Working Group Summary

This document provides a single reference point for requirements for Relying Party (RP) software for use in the Resource Public Key Infrastructure (RPKI) in the context of securing Internet routing.
 It cites requirements that appear in several RPKI RFCs, making it easier for implementers to become aware of these requirements that are segmented with orthogonal functionalities.

Document Quality

Since the first version of the document, there has been support for this draft. The two points worth noting are the concern of the WG to keep the document current and the removal of normative language because of the type of draft (Informational).  This has been addressed.

Personnel

Nathalie Trenaman (nathalie@ripe.net) is Document Shepherd (DS)
Warren Kumari (warren@kumari.net) is Responsible Area Director (RAD!)

RFC Editor Note