AFNIC: frnic-2.0 extension missing/version mismatch and/or extension not being selected

[server24]

Since the latest AFNIC Registry update the module fails with the following error message indicating a missing extension:

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    <response>
    <result code="2003">
        <msg>Missing required mandatory extensions</msg>
        <extValue>
        <value>http://www.afnic.fr/xml/epp/frnic-2.0</value>
        <reason>Missing mandatory frnic extURI EPP extension</reason>
        </extValue>
    </result>
    <trID>
        <clTRID>AFNIC::AFNIC-4468-1665071520682519</clTRID>
        <svTRID>EPP-ea041931-8c6c-4480-bd4d-66a2a715fa22</svTRID>
    </trID>
    </response>
</epp>

Bumping the namespace from 1.4 to 2.0 alone is not sufficient, so I am filing this issue. The new greeting message looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    <greeting>
    <svID>afnic</svID>
    <svDate>2022-10-06T15:52:00.664537Z</svDate>
    <svcMenu>
        <version>1.0</version>
        <lang>en-US</lang>
        <objURI>urn:ietf:params:xml:ns:host-1.0</objURI>
        <objURI>urn:ietf:params:xml:ns:contact-1.0</objURI>
        <objURI>urn:ietf:params:xml:ns:domain-1.0</objURI>
        <svcExtension>
        <extURI>urn:ietf:params:xml:ns:rgp-1.0</extURI>
        <extURI>urn:ietf:params:xml:ns:secDNS-1.1</extURI>
        <extURI>urn:ietf:params:xml:ns:launch-1.0</extURI>
        <extURI>urn:ietf:params:xml:ns:epp:fee-1.0</extURI>
        <extURI>http://www.afnic.fr/xml/epp/frnic-2.0</extURI>
        </svcExtension>
    </svcMenu>
    <dcp>
        <access>
        <all/>
        </access>
        <statement>
        <purpose>
            <admin/>
            <prov/>
        </purpose>
        <recipient>
            <ours/>
            <public/>
        </recipient>
        <retention>
            <stated/>
        </retention>
        </statement>
    </dcp>
    </greeting>
</epp>

[paullojorgge]

@server24 I submitted a pull request that should fix the issue. NOTE: I didn't spend much time looking at other changes - simply focused in fix the connectivity with AFNIC :)

[server24]

Thank you @paullojorgge, I have tested this also in production and it works.

[thedarkwinter]

Thank you @paullojorgge and @server24 , I have merged that into master (y)