2.5. FRED protocol extension

Protocol-level extensions are extensions in the XPath /epp/extension/*:*.

The FRED EPP extends the protocol in such way that the <extension> element if used, must contain only a single child:

  • <fred:extcommand> (1) – container for extending commands which must declare the FRED namespace and schema and can contain one of the custom commands:

    • <fred:creditInfo/> – requests information about the credit of the current client (object-independent command), see Credit info,

    • <fred:sendAuthInfo> – requests an AuthInfo of an object (custom command type for object-related commands), see Send AuthInfo,

    • <fred:test> – requests a technical check (custom command type for object-related commands), see Test nsset,

    • or one of the listing commands (object-independent), e.g. <fred:listDomains/>, for the complete reference of listing commands see Listing.

    The custom command may be followed by the <fred:clTRID> element (0..1), which contains a client transaction identifier as epp:trIDStringType. (Same as with the standard commands but the element is in the fred namespace.)

Example of a protocol extension
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">

   <!-- Standard container for protocol extensions -->

   <!-- FRED's container for extending commands -->
   <fred:extcommand xmlns:fred="http://www.nic.cz/xml/epp/fred-1.5"
    xsi:schemaLocation="http://www.nic.cz/xml/epp/fred-1.5 fred-1.5.0.xsd">

      <!-- An extending command (some have descendants) -->
      <!-- Transaction identification of the extending command -->




Examples of responses are illustrated for each specific command with its structure description in further chapters.