[Sidrops] Ketan Talaulikar's Yes on charter-ietf-sidrops-01-05: (with COMMENT)

Ketan Talaulikar via Datatracker <noreply@ietf.org> Wed, 07 January 2026 16:52 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from [10.244.9.115] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 0610FA418C5A; Wed, 7 Jan 2026 08:52:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ketan Talaulikar via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176780475592.3840977.5390849792306664270@dt-datatracker-5656579b89-p6k4r>
Date: Wed, 07 Jan 2026 08:52:35 -0800
Message-ID-Hash: XUNOCYZZ2CFW52TRRNKA55U6MLW4CNKD
X-Message-ID-Hash: XUNOCYZZ2CFW52TRRNKA55U6MLW4CNKD
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
CC: sidrops-chairs@ietf.org, sidrops@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Ketan Talaulikar <ketant.ietf@gmail.com>
Subject: [Sidrops] Ketan Talaulikar's Yes on charter-ietf-sidrops-01-05: (with COMMENT)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/eiFhopBBO8kLFyVMXOQ7u5Z4iQo>
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>

Ketan Talaulikar has entered the following ballot position for
charter-ietf-sidrops-01-05: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-sidrops/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Is RPKI cache to Router protocol is covered under "RPKI Technology Stack"? Is
there a definition of the components of this stack in some RFC? My understand
is that RPKI is an infrastructure and includes those various components but not
sure we can call it a stack.

I would be more comfortable if the word "stack" were to be replaced with the
components of the RPKI instead (including the RPKI-RTR).