Fundamental problem with mandatory field zone-c

Ruediger Volk <rv at deins.informatik.uni-dortmund.de> writes
 * Andreas writes:
 *   > There is no zone for aic.de, thus there is no zone contact.
 * and the data base entry for AIC.DE is gone also...
 * 
 *   > Opinions ?
 * possible ways out:
 * 
 * (a)	drop domain entries completely
 * (b)	don't register MX-only domains (in RIPE db)
 * (c)	make zone-c optional (with the convention that this is only allowed
 * 	for MX-only domains)
 * (d)	insert the zone contact for MX-only - defaulting to zone-c of
 * 	the zone containing the MX
 * 
 * I vote for (c)

In the past (Blasco has mentioned this before) we said to include the
zone-c of the parent zone, since he/she maintains the MX records. This
is Ruediger's option (d). Looking at the number of syntax errors in
the database currently for domains, and the population, I would even
vote for (a) or (b), but this has been rejected by the dns-wg on
several occassions (on very good grounds). The question was and is
whether the domain objects give added information compared to what is
in the DNS. With 4.9 and the TXT and RP RRs I am not quite sure if
these grounds still hold ...

Other opinions ?

-Marten

PS I have CCed the dns-wg as well ...