[dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
- Previous message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
- Next message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Tue Aug 21 10:28:54 CEST 2012
Peter Koch wrote: [...] >>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. Well, I guess it takes Anand to describe the motivations for the changes, but from a SW point of view, it might be a tad more "beautiful" to move away from lists in the tag:value pairs. this *might* make parsing cleaner. OTOH, unless implicitely required by business rules or otherwise, I presume it would be allowed to submit nserver: ns1.2.0.192.in-addr.arpa 192.0.2.1 nserver: ns2.2.0.192.in-addr.arpa 2001:db8::2 nserver: ns1.2.0.192.in-addr.arpa 2001:db8::1 nserver: ns2.2.0.192.in-addr.arpa 2001:db8::2 or any other permutations? Leading to complex value gathering code again... > It would appear more natural to me to list all IP addresses on a single line > after the name server's name. > > -Peter Wilfried
- Previous message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
- Next message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]