VeriSign Syntax Update

[server24]

VeriSign implemented updates for the .COM and .NET SRS and I wanted to politely ask if somebody already implemented patches for NET::DRI?

[server24]

• The "urn:ietf:params:xml:ns:contact-1.0" element will be removed from the EPP Greeting and Registry Info responses
• "VeriSign" will be replaced with "Verisign" in the element of the EPP Greeting response
  • The new complete string will be "Verisign Com/Net EPP Registration Server"
• Support for the Whois Info extension will be removed
  • The "http://www.verisign.com/epp/whoisInf-1.0" element will be removed from the EPP Greeting and Registry Info responses
  • The EPP Domain Info command will disallow the extension
• Support for Related Domain extension will be removed
  • The "http://www.verisign.com/epp/relatedDomain-1.0" element will be removed from the EPP Greeting and Registry Info responses
  • The registry:related element will be removed from the EPP Registry Info response
  • The EPP Domain Info command and the EPP Domain transform commands will disallow this extension
• Support for Client Object Attribute extension will be removed
  • The "urn:ietf:params:xml:ns:coa-1.0" element will be removed from the EPP Greeting and Registry Info responses
  • The EPP Domain Info command, the EPP Domain Create command and the EPP Domain Update command will disallow this extension
• The Registry Info response will be updated
  • The registry:group element will be removed
  • The registry:extURI element for "urn:ietf:params:xml:ns:launch-1.0" will be removed
  • The registry:objURI element for "http://www.verisign.com/epp/registry-1.0", with required = "false", will be added
  • The registry:extURI element for "urn:ietf:params:xml:ns:secDNS-1.1" will be updated to set required = "false", since the DNSSEC extension is optional
  • The registry:extURI element for "http://www.verisign.com/epp/idnLang-1.0"  will be updated to set required = "false", since support for IDN Domain names is optional
  • The registry:extURI element for "http://www.verisign.com/epp/sync-1.0"  will be updated to set required = "false", since the Consolidate (Sync) extension is optional for registrars
  • The registry:extURI element for "urn:ietf:params:xml:ns:changePoll-1.0", with required="true", will be added
  • The registry:extURI element for "urn:ietf:params:xml:ns:epp:loginSec-1.0",  with required="false", will be added  
  • The registry:extURI element for "urn:ietf:params:xml:ns:verificationCode-1.0" element , with required="false", will be added
  • The registry:statuspendingRestore</registry:status> element will be removed, since "pendingRestore" is not a status defined in  RFC 5731
  • The registry:statusredemptionPeriod</registry:status> element will be removed, since "redemptionPeriod" is not a status defined in  RFC 5731
  • The registry:dsDataInterface child elements will be updated.
    • The registry:alg elements will be updated to only include the following:

1. RSA/SHA-1
2. RSASHA1-NSEC3-SHA1
3. RSA/SHA-256
4. RSA/SHA-512
5. ECDSA Curve P-256 with SHA-256
6. ECDSA Curve P-384 with SHA-384
7. Ed25519
8. Ed448
9. SM2 signing algorithm with SM3 hashing algorithm
10. GOST R 34.10-2012
11. Private algorithms - domain name
12. Private algorithms -- OID

• The registry:digestType elements will be updated to only include the following:

1. SHA-1
2. SHA-256
3. SHA-384
4. SM3

• NOTE: These are changes to the Registry Info data only. The DNSSEC implementation already supports this list.

[thedarkwinter]

HI @server24 . Another user has submitted this fix, which includes changes to the test files etc. Can you confirm if this works fine for you? I have merged it into master. It doesn't appear to address everything you have mentioned there, but I understand it fixes the immediate issues.