RFC 9038: Extensible Provisioning Protocol (EPP) Unhandled Namespaces
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9038
- Published
- May 2021
- Authors
- J. Gould; M. Casanova
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3133Terminology for Frame Relay BenchmarkingCurrent
June 2001
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9278JWK Thumbprint URICurrent
August 2022
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
- RFC 8307Well-Known URIs for the WebSocket ProtocolCurrent
January 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?