Enum update command

The EPP update command allows you to change the token on the ENUM registration, modify its nameservers and modify the notes field. Nameserver objects can also be manipulated directly.

In order to modify the attributes of an ENUM registration, the update command must contain a <enum:update> element that identifies the enum namespace and location of the enum schema.

<enum:update> element

The <enum:update> element contains the following child elements:

• An optional <enum:E164Number> element identifying the enum registration to be modified. This should be provided if the following <token> element is not present.
• An optional <enum:token> element giving a new VA signed token to be assigned to the enum. registration. The e164Number and lastE164Number elements in this token must match the registration exactly.
• An optional <enum:ns> element giving new nameserver details to assign to the registration. This contains zero to ten elements of type <enum:hostName> which contain the name of each nameserver to attach to the enum.
• An optional <enum:notes> element.

Either the <enum:e164Number> or the <enum:token> element is required to identify the enum registration to modify.

As a signed token may be provided as part of a modification, this command may be used to perform a pull registrar change and to perform a renewal.  To combine a renewal with the modification, set the "renew" attribute on the <enum:update> element to "Y".

Examples

Example of an <enum:update> command with no token provided.

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
  epp-1.0.xsd">
  <command>
    <update>
      <enum:update 
        xmlns:enum="http://www.nominet.org.uk/epp/xml/nom-enum-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-enum-1.0
        nom-enum-1.0.xsd">
        <enum:E164Number>+441865332300</enum:E164Number>
        <enum:ns>
          <enum:hostName>ns0.example.com</enum:hostName>
          <enum:hostName>ns1.example.com</enum:hostName>
        </enum:ns>
      </enum:update>
    </update>
  </command>
</epp>

Example of an <enum:update> command where the token is updated. The token given here is illustrative. A complete token is available here.

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
  epp-1.0.xsd">
  <command>
    <update>
      <enum:update 
        xmlns:enum="http://www.nominet.org.uk/epp/xml/nom-enum-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-enum-1.0
        nom-enum-1.0.xsd">
        <token 
          xmlns="urn:ietf:params:xml:ns:enum-token-1.0" Id="TOKEN"
          xsi:schemaLocation= "urn:ietf:params:xml:ns:enum-token-1.0 
          enum-token-1.0.xsd">
          <validation serial="acmeve-000001">
            <E164Number>+441865332211</E164Number>
            <validationEntityID>ACME-VE</validationEntityID>
            <registrarID>44-EXAMPLE</registrarID>
            <methodID>42</methodID>
            <executionDate>2007-05-08</executionDate>
          </validation>
          <tokendata 
            xmlns="urn:ietf:params:xml:ns:enum-tokendata-1.0"
            xsi:schemaLocation="urn:ietf:params:xml:ns:enum-tokendata-1.0
            enum-tokendata-1.0.xsd">
            <contact>
              <organisation>Example Inc.</organisation>
              <commercialregisternumber>4711</commercialregisternumber>
              <title>Dr.</title>
              <firstname>Max</firstname>
              <lastname>Vanstone</lastname>
              <address>
                <streetName>Main</streetName>
                <houseNumber>10</houseNumber>
                <postalCode>1010</postalCode>
                <locality>London</locality>
                <countyStateOrProvince>London</countyStateOrProvince>
                <ISOcountryCode>GB</ISOcountryCode>
              </address>
            </contact>
          </tokendata>
          <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
            <SignedInfo>
              <CanonicalizationMethod
                Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
              <SignatureMethod
                Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
              <Reference URI="#TOKEN">
                <Transforms>
                  <Transform Algorithm=
                    "http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                  <Transform
                    Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
                    <InclusiveNamespaces
                      xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"
                      PrefixList="enum-token enum-tokendata"/>
                  </Transform>
                </Transforms>
                <DigestMethod
                  Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
                <DigestValue
                  >VxqsBxSNPFwPAUlCHts3g3DehcexnB1dqUz+GypLZ0k=</DigestValue>
              </Reference>
            </SignedInfo>
            <SignatureValue>
              QKqphKRNPokVZFbenje+HZZV+RLrNweGnlWBw7ngAtH+rtuslR8LhMLmC4DlBb9V
              HvKItl+7zLGm3VgYsqfHH8q3jCl1mFxUIuLlIPqtpJs+xAHAJDzZ+vmsF/q2IgrS
              K0uMmKuU5V1gydDBOvIipcJx+PrPYyXYZSjQXkWknK8=</SignatureValue>
            <KeyInfo>
              <X509Data>
                <X509Certificate>
                  MIIDZjCCAs+gAwIBAgIBBDANBgkqhkiG9w0BAQQFADB0MQswCQYDVQQGEwJBVDEP
                  MA0GA1UEBxMGVmllbm5hMRQwEgYDVQQKEwtCT0ZIIENlcnRzLjEbMBkGA1UEAxMS
                  Q0VSVFMuYm9maC5wcml2LmF0MSEwHwYJKoZIhvcNAQkBFhJjZXJ0c0Bib2ZoLnBy
                  aXYuYXQwHhcNMDQwNzIwMTMxNTA5WhcNMDUwNzIwMTMxNTA5WjB/MQswCQYDVQQG
                  EwJBVDEKMAgGA1UECBMBLTEPMA0GA1UEBxMGVmllbm5hMR0wGwYDVQQKExRBY21l
                  IEVOVU0gVmFsaWRhdGlvbjEQMA4GA1UEAxMHYWNtZS1WRTEiMCAGCSqGSIb3DQEJ
                  ARYTbm9ib2R5QGVudW0tYWNtZS5hdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC
                  sJWd+MYrNcuSrv3TIOsUkUgNpNNhmkZPtiXqfy3388IRdJtJiLWXSOb/XlZHOM9I
                  MvwKYwhcpQ9UdM/w7VpXQqf+CEj0XSyqxGw65UsHIOijgiG/WyhSj+Lzriw7CTge
                  P2iAJkJVC4t2XA==
                </X509Certificate>
              </X509Data>
            </KeyInfo>
          </Signature>
        </token>
      </enum:update>
    </update>
  </command>
</epp>

 

Example of a successful enum update response

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
       epp-1.0.xsd">
    <response>
      <result code="1000">
        <msg>Command completed successfully</msg>
      </result>
      <trID>
        <clTRID>ABC-12345</clTRID>
        <svTRID>65789465</svTRID>
      </trID>
    </response>
  </epp>