RFC 9038 on Extensible Provisioning Protocol (EPP) Unhandled Namespaces

rfc-editor@rfc-editor.org Sun, 30 May 2021 05:32 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 D2AB13A2F3D; Sat, 29 May 2021 22:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 mlTmS1YkD_09; Sat, 29 May 2021 22:32:36 -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 786963A2F3A; Sat, 29 May 2021 22:32:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D7663F40720; Sat, 29 May 2021 22:32:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9038 on Extensible Provisioning Protocol (EPP) Unhandled Namespaces
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: <20210530053217.D7663F40720@rfc-editor.org>
Date: Sat, 29 May 2021 22:32:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HqgblrniruGgBlvNzhKyZGpRaEI>
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: Sun, 30 May 2021 05:32:42 -0000

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

        
        RFC 9038

        Title:      Extensible Provisioning Protocol (EPP)  
                    Unhandled Namespaces 
        Author:     J. Gould,
                    M. Casanova
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2021
        Mailbox:    jgould@verisign.com,
                    martin.casanova@switch.ch
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-unhandled-namespaces-08.txt

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

        DOI:        10.17487/RFC9038

The Extensible Provisioning Protocol (EPP), as defined in RFC 5730,
includes a method for the client and server to determine the objects
to be managed during a session and the object extensions to be used
during a session.  The services are identified using namespace URIs,
and an "unhandled namespace" is one that is associated with a service
not supported by the client. This document defines an operational
practice that enables the server to return information associated
with unhandled namespace URIs and that maintains compliance with the
negotiated services defined in RFC 5730.

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