Re: FRED, foreign client error

Hi, I'm successfully connecting to and able to login to FRED (demo) at TZNIC - using the EPP Library that CentralNIC wrote (all PHP) - with some modifications. However - all "commands" after that seem to return the same (similar) error message. I've looked and copied examples from RFC5731... As an example - the Info Command... C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <info> C: <domain:info C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name hosts="all">example.com</domain:name> C: </domain:info> C: </info> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp> So I actually send: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name hosts="all">dnssec.or.tz</domain:name> </domain:info> </info> <clTRID>ABC-12345</clTRID> </command> </epp> and get back: <?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"><response><result code="2001"><msg>Command syntax error</msg><extValue><value><domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name hosts="all">dnssec.or.tz</domain:name> </domain:info></value><reason>Schemas validity error: Element '{urn:ietf:params:xml:ns:domain-1.0}info': No matching global element declaration available, but demanded by the strict wildcard.</reason></extValue></result><trID><svTRID>ReqID-0002778177</svTRID></trID></response></epp> What seems to be common is "Schemas validity error: Element '{urn:ietf:params:xml:ns:domain-1.0}info': No matching global element declaration available, but demanded by the strict wildcard." and I have no idea what that means. What should I be sending then???? ...and from a debugging prospective - getting the reply on more or less one line is real hard to read for a Human. Yes - a Machine has no problem. I wish there was a switch for "Human Readable XML" - all neatly grouped and indented like in the RFC documents. In case its my login - it looks like this - except with User/Passwd XXXX'ed out: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <login> <clID>REG-XXXXXXX</clID> <pw>XXXXXXXX</pw> <options> <version>1.0</version> <lang>en</lang> </options> <svcs> <objURI>urn:ietf:params:xml:ns:domain-1.0</objURI> <objURI>urn:ietf:params:xml:ns:contact-1.0</objURI> <svcExtension> <extURI>urn:ietf:params:xml:ns:secDNS-1.1</extURI> </svcExtension> </svcs> </login> </command> </epp> Reply==> <?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"><response><result code="1000"><msg>Command completed successfully</msg></result><trID><svTRID>ReqID-0002778173</svTRID></trID></response></epp> Please note - the current EPP XML works for the COZA System, Cocca and Central-NIC.