All fields are mandatory unless optional, excluding those that can be blank, or errors in the specification ;) Or in English * optional fields - dont output the label & data if the data is not provided * fields explicity mentioned as allowed to be blank - output the label but no data if the data is not provided * everything else - output the label and the data
KF - You and I have subtly different interpretations of Clarification
Where a 'clarification' contradicts the _contract_ then as the contact is the thing that is 'binding', I would always go with that :) Contract = what you must do, Clarifications tend to = 'we'd like this and use it to sneak things in the back-door'
Clarification 7. If IP addresses are provided for name servers Clarification 8. Hosts may be added without IP addresses. For self-referencing domains (glue) output the label, IP and FQDNs otherwise just label and FQDN KF - It is perfectly legal to have no IP address for a host and to assign a domain to such a host.
Not for any gTLD that I'm aware of - the registry will reject it at time of registration (happens *very* frequently according to my epp error logs)
I echo Alexander's request that a complete specification, with no contradictions and no guesses, is required. Yes, and that doenst contradict the *contract* KF - completely agree.
Rob