RFC 8748 on Registry Fee Extension for the Extensible Provisioning Protocol (EPP)

rfc-editor@rfc-editor.org Sat, 14 March 2020 16:45 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA0283A0781; Sat, 14 Mar 2020 09:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bfcNfvYIvIBo; Sat, 14 Mar 2020 09:45:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A5DE3A0780; Sat, 14 Mar 2020 09:45:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0B10EF406C9; Sat, 14 Mar 2020 09:45:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3NDggb24gUmVnaXN0cnkgRmVlIEV4dGVuc2lvbiBmb3IgdGhlIEV4dGVuc2libGUgUHJvdmlzaW9uaW5nIFByb3RvY29sIChFUFAp?=
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, regext@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200314164521.0B10EF406C9@rfc-editor.org>
Date: Sat, 14 Mar 2020 09:45:21 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5PnAlo7QugqAcJCzYtC6kZbexLk>
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: Sat, 14 Mar 2020 16:45:30 -0000

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

        
        RFC 8748

        Title:      Registry Fee Extension for the 
                    Extensible Provisioning Protocol (EPP) 
        Author:     R. Carney, 
                    G. Brown,
                    J. Frakes
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    rcarney@godaddy.com, 
                    gavin.brown@centralnic.com, 
                    jothan@jothan.com
        Pages:      30
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-epp-fees-20.txt

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

        DOI:        10.17487/RFC8748

Given the expansion of the DNS namespace and the proliferation of
novel business models, it is desirable to provide a method for
Extensible Provisioning Protocol (EPP) clients to query EPP servers
for the fees and credits associated with various billable
transactions and provide expected fees and credits for certain
commands and objects. This document describes an EPP extension
mapping for registry fees.

This document is a product of the Registration Protocols Extensions 
Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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