|
|
|
# Design Considerations
|
|
|
|
|
|
|
|
The [data tree](https://gitlab.labs.nic.cz/llhotka/zone-data-yang/raw/master/model.tree) represents configurations of any number of
|
|
|
|
*complete* zones.
|
|
|
|
Unlike [Daley et al.][1] who aimed to “use as closely as possible the presentation format for
|
|
|
|
RDATA fields given in various RFCs”, this data model uses an
|
|
|
|
organisation of data and types of RR fields so as to make
|
|
|
|
configuration of zones as effective and convenient as possible, even
|
|
|
|
though experienced DNS admins may need some time to get used to some
|
|
|
|
aspects.
|
|
|
|
|
|
|
|
The
|
|
|
|
[data tree](https://gitlab.labs.nic.cz/llhotka/zone-data-yang/raw/master/model.tree)
|
|
|
|
represents configurations of any number of *complete* zones. Every
|
|
|
|
zone is uniquely identified by its (domain) name.
|
|
|
|
|
|
|
|
Resource records are organised into RRSet
|
|
|
|
|
|
|
|
## References
|
|
|
|
|
|
|
|
[1]: [draft-daley-dnsxml-00](https://www.ietf.org/archive/id/draft-daley-dnsxml-00.txt) |
