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

rfc-editor@rfc-editor.org Wed, 28 July 2021 06:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0A1C93A1EF4 for <ietf-announce@ietfa.amsl.com>; Tue, 27 Jul 2021 23:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bexXhMKl_uj4 for <ietf-announce@ietfa.amsl.com>; Tue, 27 Jul 2021 23:15:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 405473A1EEB for <ietf-announce@ietf.org>; Tue, 27 Jul 2021 23:15:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6DBABF40752; Tue, 27 Jul 2021 23:14:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwOTUgb24gRXh0ZW5zaWJsZSBQcm92aXNpb25pbmcJUHJvdG9jb2wgKEVQUCkgRG9tYWluIE5hbWUgTWFwcGluZyBFeHRlbnNpb24gZm9yIFN0cmljdCBCdW5kbGluZyBSZWdpc3RyYXRpb24=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210728061448.6DBABF40752@rfc-editor.org>
Date: Tue, 27 Jul 2021 23:14:48 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/NsazbfPmmRGyDLp-P9TIsBKlJfw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2021 06:15:12 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9095

        Title:      Extensible Provisioning Protocol (EPP) Domain 
                    Name Mapping Extension for Strict Bundling 
        Author:     J. Yao,
                    L. Zhou,
                    H. Li,
                    N. Kong,
                    J. Xie
        Status:     Informational
        Stream:     Independent
        Date:       July 2021
        Mailbox:    yaojk@cnnic.cn,
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-yao-regext-bundling-registration-06.txt

        URL:        https://www.rfc-editor.org/info/rfc9095

        DOI:        10.17487/RFC9095

This document describes an 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. This is a nonstandard proprietary extension.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC