Skip to main content

Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc:,, Joseph Yee <>, The IESG <>,,,,
Subject: Document Action: 'Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration' to Informational RFC (draft-ietf-regext-bundling-registration-09.txt)

The IESG has approved the following document:
- 'Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension
   for Strict Bundling Registration'
  (draft-ietf-regext-bundling-registration-09.txt) as Informational RFC

This document is the product of the Registration Protocols Extensions Working

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

This document describes a non-standard proprietary extension of
Extensible Provisioning Protocol (EPP) domain name mapping for the
provisioning and management of strict bundling registration of domain
names. Specified in XML, this mapping extends the EPP domain name mapping
to provide additional features required for the provisioning of bundled
domain names.

Working Group Summary

The WG discussed this topic in both mailing list and at meetings, there
are no controversies or lack of coverage.  The working group had
discussed and considered to move forward as an Informational RFC, the WG
and the related BOF (DNSBundle) discussed the topic this document covers
and nobody objects to its publication within the limited scope it covers.

The original draft has covers more different scenarios (relax bundling),
also had some other drafts covering similar problems, and the working
group was also mindful of work output and coordination needed with
DNSBundle.   The work effort was consolidated and moved forward to cover
a very specific scenario only. The working group also agrees that
DNSBundle does not prevent the publication of the draft covering the
specific scenario (strict bundling).

This document covers the very specific scenario, strict bundling, and
introduces one specific mechanism on how to manage that problem space.
The WG is aware of the narrow specific scope this document covers and
discussed how best to move this document forward. he consensus is to
progress this document as an Informational RFC.

Document Quality

There are two registry implementations captured in the Implementation Status section.
There is one open source implementation available on client side.


Joseph Yee is the document shepherd and Barry Leiba is the responsible AD.

RFC Editor Note