On Fri, Jul 27, 2012 at 02:57:57PM +0200, Anand Buddhdev wrote:
The RIPE NCC proposes to make the "nserver:" attribute mandatory in DOMAIN objects and delete any objects from the RIPE Database that do not have this attribute.
{no hats} For domain objects covering the reverse space, I believe this makes sense. For ENUM (for those who remember), this might be different due to layer 9 involvement. Numbers are small, though and I do not recall a non-delegation entry precedent.
To simplify the parsing of DOMAIN objects, the RIPE NCC also proposes to deprecate the list option on the "nserver:" attribute (a list, when used in combination with end-of-line comments and continuation lines, is very complex to parse). This means adding multiple name servers to a single attribute will no longer be allowed. For example, an attribute currently formatted as:
nserver: ns1.example.com ns2.example.net
will have to be rewritten as:
nserver: ns1.example.com nserver: ns2.example.net
If glue records are required, they would be written like this:
nserver: ns1.2.0.192.in-addr.arpa 192.0.2.1 nserver: ns1.2.0.192.in-addr.arpa 2001:db8::1 nserver: ns2.2.0.192.in-addr.arpa 192.0.2.2 nserver: ns2.2.0.192.in-addr.arpa 2001:db8::2
While I agree with the first move, I do not see the beauty in the second. It would appear more natural to me to list all IP addresses on a single line after the name server's name. -Peter