1.1 What does Security and Stability mean?
1.1.1 Availability of data/system
1.1.2 Correctness/accuracy
1.1.5 Attribution/zone data?
1.2.1 Operational criteria
1.2.1.1 Roles and responsibilities
1.2.1.2 Physical/procedural/process
1.2.1.3 3rd party suppliers of services/SLA's
1.2.2 Institutional confidence
1.2.3 Accountability and transparency
2.1.3 Accuracy (e.g. errors/typos in names/IPs/etc.
2.2.1.1.1 At multiple ports
2.2.1.1.3 Officially intentional
2.2.1.2 Note -- WW CGI.hR, SIMET
2.2.2 Infrastructure (Mikey's suggestion for topic-header)
2.2.3 Content (Mikey's suggestion for topic-header)
2.2.3.2.2 Submission/registration
3.1 From whose perspective???
3.2.1.1 Operator (people, location, funds, experience)
3.2.1.2 Infrastructure (brand, spec, location)
3.3.1.1 Integrity of data
3.3.1.3 Resistant to attack
3.3.1.4 Manage threats effectively
3.3.2.1 Works and continues to work in a highly predictable way
3.3.2.2 Changes can be implemented with a predictable impact on services
3.3.2.4 Acceptable performance for all actors
4.2 Availability of DNS as a service
4.4 (1) Availability - n/a
4.4.1 DNS data accuracy -- 100%
4.5 (2) Availability - 90%
4.5.1 DNS data accuracy -- 100%
4.6.1 DNS data accuracy -- 100%
4.7 (4) Availability -- 100%
4.7.1 DNS data accuracy -- 100%
5.1 How can you tell the DNS stable?
5.2 Operability of DNS L and coordination of root servers
5.3.3 Hard to determine health of DNS based on unknown bu exploited holes in DNS
5.3.4 Healthy DNS needs good incident management and good network operations
5.3.5 Threat warning and recommendations of mitigation based on the warning
5.3.6 Need of service level of DNS (dashboard)