Organization Extension for the Extensible Provisioning Protocol (EPP)
Extracted elements (25)
The extension is designed to be generic — applicable to any existing EPP object (domain, host, contact) and any future objects — rather than being tied to a specific object type, enabling broad reuse across the EPP ecosystem.
Organization role values used in the 'role' attribute of <orgext:id> are defined in Section 7.3 of RFC 8543 (EPP Organization Mapping); implementations must refer to that registry for valid role values.
After a successful transfer of an object with an assigned organization, handling of the assigned organization is dependent on the organization roles and server policy; the transfer command itself adds no extension elements.
An attempt to add an organization ID with a role that already exists does not change the object at all; the server SHOULD notify clients by sending a 2305 error response code. Likewise for remove/change when the role does not exist.
Any given EPP object MUST have at most one associated organization ID for any given role value.
Elements and element content described in this document MUST inherit the internationalization conventions used in the XML instance that includes this extension. UTF-8 encoding is RECOMMENDED.
For <orgext:add>, the <orgext:id> element MUST have a non-empty organization identifier value; the server SHOULD validate that the role does not already exist.
For <orgext:chg>, the server SHOULD validate the existence of the <orgext:id> element role; the existing organization identifier value will be replaced for the defined role.
For <orgext:rem>, the <orgext:id> element MAY have an empty organization identifier value; the server SHOULD validate the existence of the role and the identifier if provided.
For the <create> command, the EPP <extension> element MUST contain a child <orgext:create> element if the client wants to associate organization data to the object. The <orgext:create> element must contain one or more <orgext:id> elements.
For the <update> command, the <extension> element MUST contain a child <orgext:update> element, which MUST contain at least one of <orgext:add>, <orgext:rem>, or <orgext:chg>.
Implementations MUST NOT depend on the 'orgext' XML namespace prefix; they should use a proper namespace-aware XML parser and serializer.
Organization object identifiers defined in RFC 8543 MUST be known to the server before the organization object can be associated with the EPP object.
The <orgext:infData> element or its ancestor element MUST identify the extension namespace 'urn:ietf:params:xml:ns:epp:orgext-1.0'.
When an <info> command has been processed successfully, the EPP <extension> element SHOULD contain a child <orgext:infData> element if the object has data associated with this extension, based on server policy.
The <orgext:create> element carries one or more <orgext:id> elements (each with a required 'role' attribute) used to associate organizations with an EPP object at creation time.
The <orgext:id> element provides the identifier of an organization, corresponding to the <org:id> element defined in RFC 8543. It carries a required 'role' attribute representing the relationship between the organization and the EPP object.
The <orgext:infData> element is the info response element containing zero or more <orgext:id> child elements, each with a 'role' attribute, returned when an object has organization associations.
The <orgext:update> element contains three optional child elements: <orgext:add> (adds nonexistent organization roles), <orgext:rem> (removes organization roles), and <orgext:chg> (changes existing organization role identifiers). At least one MUST be present.
IANA registered two URIs under the IETF XML Registry (RFC 3688): the namespace URI 'urn:ietf:params:xml:ns:epp:orgext-1.0' and the schema URI 'urn:ietf:params:xml:schema:epp:orgext-1.0', with IESG as registrant contact.
The extension was registered in the 'Extensions for the Extensible Provisioning Protocol (EPP)' registry (RFC 7451) with name 'Organization Extension for the Extensible Provisioning Protocol (EPP)', status Active, applicable to any TLD.
The organization extension does not introduce any security services or considerations beyond those described by the core EPP specifications (RFC 5730, RFC 5731, RFC 5732, RFC 5733) or by the protocol layers used by EPP.
The createType complex type contains a sequence of one or more <orgext:id> elements of orgIdType, constituting the <orgext:create> command payload. No maximum cardinality is imposed (maxOccurs='unbounded').
The orgIdType complex type encodes an organization identifier as an XML token (simpleContent) with a required 'role' attribute of type token. Used in <orgext:id> elements throughout create, update, and info response messages.
The updateType complex type contains an optional sequence of <add>, <rem>, and <chg> elements (each of addRemChgType), all with minOccurs='0'; the addRemChgType itself holds one or more <orgext:id> elements.