[Sidrops] Protocol Action: 'Resource Public Key Infrastructure (RPKI) Manifest Number Handling' to Proposed Standard (draft-ietf-sidrops-manifest-numbers-08.txt)

The IESG <iesg-secretary@ietf.org> Tue, 13 January 2026 17:21 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <176832487244.1004010.4890524735497659966@dt-datatracker-5656579b89-r5kdq>
Date: Tue, 13 Jan 2026 09:21:12 -0800
Message-ID-Hash: UUIFJCXFAMFNKZMMGC2VOECWRILJRY3Y
CC: The IESG <iesg@ietf.org>, draft-ietf-sidrops-manifest-numbers@ietf.org, ggx@gigix.net, mohamed.boucadair@orange.com, rfc-editor@rfc-editor.org, sidrops-chairs@ietf.org, sidrops@ietf.org
Subject: [Sidrops] Protocol Action: 'Resource Public Key Infrastructure (RPKI) Manifest Number Handling' to Proposed Standard (draft-ietf-sidrops-manifest-numbers-08.txt)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/MCxA5N56R3xuusXsXquPE31uh-U>

The IESG has approved the following document:
- 'Resource Public Key Infrastructure (RPKI) Manifest Number Handling'
  (draft-ietf-sidrops-manifest-numbers-08.txt) as Proposed Standard

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

The IESG contact persons are Mahesh Jethanandani and Mohamed Boucadair.

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




Technical Summary

   The Resource Public Key Infrastructure (RPKI) makes use of signed
   objects called manifests.  A manifest lists each file that an issuer
   intends to include within an RPKI repository, and can be used to
   detect certain forms of attack against a repository.  Manifests
   include a "manifest number" (manifestNumber), which an issuer must
   increment whenever it issues a new manifest, and Relying Parties
   (RPs) are required to verify that a newly-retrieved manifest for a
   given Certification Authority (CA) has a higher manifestNumber than
   the previously-validated manifest. However, the manifestNumber field
   is 20 octets in length (i.e.,  bounded), and no behavior is specified
   for when a manifestNumber reaches the largest possible value.  This
   document updates RFC 9286 by specifying issuer and RP behavior for
   this scenario.

Working Group Summary

    No issue was raised against the specification during it devleoppement.
    Even if the number of support during the WGLC is not huge there
    were no objections in moving this document forward.    

Document Quality

    Two independent implementations were disclosed:

    - NLnet Labs, "Routinator", June 2024,
    <https://www.nlnetlabs.nl/projects/routing/routinator/>.

    - OpenBSD Project, "rpki-client", January 2024,
    <https://www.rpki-client.org/>.

Personnel

   The Document Shepherd for this document is Luigi Iannone.
   The Responsible Area Director is Mohamed Boucadair.

[Sidrops] Protocol Action: 'Resource Public Key I… The IESG