---
id: "1c7585f8-0eca-487d-b376-cb98136cb714"
kind: "link"
title: "IETF publishes RFC 10091 creating an IANA registry for EPP extensions"
language: "en"
section: "icann"
date: "2026-11-17T17:34:17Z"
updated: "2026-11-17T17:34:17Z"
canonical: "https://tldlog.com/l/ietf-publishes-rfc-10091-creating-iana-registry-epp/"
origin: "master"
translations:
  es: "https://tldlog.com/es/l/ietf-publica-rfc-10091-que-crea-registro-iana-extensiones/"
  de: "https://tldlog.com/de/l/ietf-veroeffentlicht-rfc-10091-iana-registry-epp/"
  fr: "https://tldlog.com/fr/l/ietf-publie-rfc-10091-creant-registre-iana-extensions-epp/"
  it: "https://tldlog.com/it/l/ietf-pubblica-rfc-10091-che-crea-registro-iana-estensioni/"
  pt-BR: "https://tldlog.com/pt/l/ietf-publica-rfc-10091-que-cria-registro-iana-extensoes-epp/"
  ru: "https://tldlog.com/ru/l/ietf-publikuet-rfc-10091-sozdayushchiy-reestr-iana/"
  zh-Hans: "https://tldlog.com/zh/l/ietf-fabu-rfc-10091-epp-kuozhan/"
source:
  name: "bortzmeyer.org"
  url: "https://www.bortzmeyer.org/10091.html"
  language: "fr"
  date: "2026-11-17T00:00:00Z"
---

# IETF publishes RFC 10091 creating an IANA registry for EPP extensions

## in plain words

EPP is a computer language that domain registries use to create, change and delete domain names. Some registries added their own extra features, which sometimes clashed with each other. This new RFC creates a shared public list so developers can see what already exists.

The Internet Engineering Steering Group (IESG) has published RFC 10091, a specification for a registry of extensions to the Extensible Provisioning Protocol (EPP), maintained by IANA. The document was written by S. Hollenbeck of Verisign Labs as part of the IETF regext working group. It replaces RFC 7451 and changes its status from informational to best practice.

EPP is mainly used by domain registries, and by registrants or their registrars, to create, modify and delete domain names. Because each registry has its own registration policy, the standard schema does not fit everyone, so many registries built their own extensions. RFC 3735 gives guidance on creating extensions but says little about how to publish them, and several registries have built different, incompatible extensions for the same problem, such as recording VAT information on objects created through EPP.

Under the new registry, extensions are registered under the “specification required” policy described in RFC 8126. This means a public specification must exist and be reviewed by an expert appointed by IANA, currently Gavin Brown. Discussion about a proposed extension or the quality of its documentation takes place on the regext mailing list. Reviewers must consider privacy effects, a concern the document says was absent from RFC 3735.

The RFC asks reviewers to be flexible. An extension that is documented and deployed should be registered even if the expert has technical objections. Several similar extensions may be registered, and a applicant proposing a close copy of an existing extension will be told about it, but will not be blocked.

The RFC also says that XML-related information for EPP must be recorded in the XML registry under RFC 3688. To register, applicants send IANA a form giving the extension name, a link to its specification, contact details, the TLD it applies to or “Any”, and any intellectual property disclosures, such as patents under RFC 8179. The document includes an example form and a real registration, for the grace period extension in RFC 3915, where the IESG is the contact.

The document also summarises the main changes from RFC 7451, including the new status and the move of the discussion list from `eppext@ietf.org` to `regext@ietf.org`.

Source: [bortzmeyer.org](https://www.bortzmeyer.org/10091.html)

## also covered by

- [Domain Brief](https://domainbrief.de/artikel/rfc-10091-legt-neue-regeln-fuer-das-register-der-epp-erweiterungen-fest) (in German)
