[Sidrops] Call for adoption: draft-timbru-sidrops-change-pubserver-01 (Ends 2025-10-28)

Luigi Iannone via Datatracker <noreply@ietf.org> Tue, 14 October 2025 08:46 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from [10.244.8.144] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 237BB730447F; Tue, 14 Oct 2025 01:46:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Luigi Iannone via Datatracker <noreply@ietf.org>
To: draft-timbru-sidrops-change-pubserver@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176043159909.813615.14168220908814813708@dt-datatracker-84f8f646b-tg6mn>
Date: Tue, 14 Oct 2025 01:46:39 -0700
Message-ID-Hash: 6HDRMK7SIVJ4TRF3LSZU7ICFD76QODOY
X-Message-ID-Hash: 6HDRMK7SIVJ4TRF3LSZU7ICFD76QODOY
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Reply-To: Luigi Iannone <ggx@gigix.net>
Subject: [Sidrops] Call for adoption: draft-timbru-sidrops-change-pubserver-01 (Ends 2025-10-28)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/9aBrkG4JYVBclRhbjIeM5xnmcqQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Subject: Call for adoption: draft-timbru-sidrops-change-pubserver-01  (Ends
2025-10-28)

This message starts a 2-week Call for Adoption for this document.

Abstract:
   This document outlines how an RPKI CA can migrate from one RFC 8181
   Publication Server to another.  The process is similar to the RPKI CA
   Key Rollover process defined in RFC 6489, except that in this case a
   new location is used for the new key.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-timbru-sidrops-change-pubserver/

Please reply to this message keeping sidrops@ietf.org in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/