[regext] WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)

James Galvin via Datatracker <noreply@ietf.org> Mon, 13 October 2025 20:33 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@mail2.ietf.org
Received: from [10.244.8.144] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 971A272B5860; Mon, 13 Oct 2025 13:33:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: James Galvin via Datatracker <noreply@ietf.org>
To: draft-ietf-regext-ext-registry-epp@ietf.org, gavin.brown@icann.org, regext-chairs@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176038761756.679481.14812728809171611120@dt-datatracker-84f8f646b-tg6mn>
Date: Mon, 13 Oct 2025 13:33:37 -0700
Message-ID-Hash: SMBQPNMDHKXKDL4IHKUCDGY5HVVLICZA
X-Message-ID-Hash: SMBQPNMDHKXKDL4IHKUCDGY5HVVLICZA
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.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: James Galvin <galvin@elistx.com>
Subject: [regext] WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/mqTteZ5SvZdEv8SNttM0dk9GmMs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

Subject: WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)

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

Abstract:
   The Extensible Provisioning Protocol (EPP) includes features to add
   functionality by extending the protocol.  It does not, however,
   describe how those extensions are managed.  This document describes a
   procedure for the registration and management of extensions to EPP,
   and it specifies a format for an IANA registry to record those
   extensions.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-regext-ext-registry-epp/

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping
regext@ietf.org in copy. Objections should be motivated and suggestions to
resolve them are highly appreciated.

Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
[1]. 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/