Last Call: <draft-ietf-sidrops-6486bis-08.txt> (Manifests for the Resource Public Key Infrastructure (RPKI)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 16 December 2021 20:13 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>
Subject: Last Call: <draft-ietf-sidrops-6486bis-08.txt> (Manifests for the Resource Public Key Infrastructure (RPKI)) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-sidrops-6486bis@ietf.org, morrowc@ops-netman.net, sidrops-chairs@ietf.org, sidrops@ietf.org, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <163968561528.5705.3344262878453726327@ietfa.amsl.com>
Date: Thu, 16 Dec 2021 12:13:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/pH-UvM7Txzr5VIrfrE7U8RrZpX0>

The IESG has received a request from the SIDR Operations WG (sidrops) to
consider the following document: - 'Manifests for the Resource Public Key
Infrastructure (RPKI)'
<draft-ietf-sidrops-6486bis-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-12-30. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract

This document defines a "manifest" for use in the Resource Public Key
Infrastructure (RPKI). A manifest is a signed object (file) that
contains a listing of all the signed objects (files) in the
repository publication point (directory) associated with an authority
responsible for publishing in the repository. For each certificate,
Certificate Revocation List (CRL), or other type of signed objects
issued by the authority that are published at this repository
publication point, the manifest contains both the name of the file
containing the object and a hash of the file content. Manifests are
intended to enable a relying party (RP) to detect certain forms of
attacks against a repository. Specifically, if an RP checks a
manifest's contents against the signed objects retrieved from a
repository publication point, then the RP can detect "stale" (valid)
data and deletion of signed objects.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
rfc8488: RIPE NCC's Implementation of Resource Public Key Infrastructure (RPKI) Certificate Tree Validation (Informational - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-sidrops-6486bis-08.txt> (M… The IESG