[Sidrops] I-D Action: draft-ietf-sidrops-manifest-numbers-00.txt
internet-drafts@ietf.org Fri, 19 April 2024 15:02 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DB9C14F602; Fri, 19 Apr 2024 08:02:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sidrops@ietf.org
Message-ID: <171353896701.25456.6881232945682055615@ietfa.amsl.com>
Date: Fri, 19 Apr 2024 08:02:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/5eGRg0szagA0tbnz9jeD9Pu7k8I>
Subject: [Sidrops] I-D Action: draft-ietf-sidrops-manifest-numbers-00.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2024 15:02:47 -0000
Internet-Draft draft-ietf-sidrops-manifest-numbers-00.txt is now available. It is a work item of the SIDR Operations (SIDROPS) WG of the IETF. Title: RPKI Manifest Number Handling Authors: Tom Harrison George G. Michaelson Job Snijders Name: draft-ietf-sidrops-manifest-numbers-00.txt Pages: 10 Dates: 2024-04-19 Abstract: The Resource Public Key Infrastructure (RPKI) makes use of signed objects called manifests. A manifest lists each file that a publisher 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 the publisher 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. not unbounded), and no behaviour is specified for when a manifestNumber reaches the largest possible value. This document specifies publisher and RP behaviour for this scenario. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-sidrops-manifest-numbers/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-manifest-numbers-00 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [Sidrops] I-D Action: draft-ietf-sidrops-manifest… internet-drafts