Test Requirements Task Force (TRTF)
- Sandoche Balakrichenan (Afnic)
Outline
Ø  Zonemaster
Ø  TRTF
Ø  What & Why
Ø  Your feedback
2
Why a new tool?
Ø  Zonecheck
Ø  Ruby
Ø  Legacy code
Ø  DNScheck
Ø  Does not provide deterministic results
Ø  Decision
Ø  Upgade existing tools ?
Ø  Start from the scratch ?
3
High level architecture
Usage method
CLI method
Test engine
Output type
CLI output
Machine parsable output
Web GUI method
Web output
Batch method
Reports
Sta@s@cs
Raw Data
4
Useful Information
Ø  All documentation are in github (CC 4.0 License)
Ø  All source codes are in github (BSD License)
Ø  Zonemaster
Ø  Zonemaster-Engine
Ø  Zonemaster-GUI
Ø  Zonemaster-CLI
Ø  Zonemaster-Backend
Ø  Stable Release
Ø  Maintenance until 2016
Ø  We need your inputs for new features
Ø
5
zonemaster-users@iis.se, zonemaster-devel@iis.se
Dilemma before implementing ZM
6
Test requirements
7
Test requirements
DNSCheck
ZoneCheck
Updated Test
Requirements
I/P from the team
IANA Policy
External I/P
8
Test classification
9
Test specification
10
Test specification
11
TRTF
Ø  The idea originated from CENTR Jamboree and
DNS-OARC to create a TRTF
Ø  TRTF is currently under the scope of CENTR
(https://github.com/CENTRccTLDs/TRTF)
Ø  Objective
Ø  BCP
Ø  Informational RFC
12
Issues
Ø  Tried number of times but did not materialise
Ø  Different people have different requirement
Ø  The TRTF mailing list is getting lukewarm
response
Ø  Volume of the work involved
13
Why this presentation?
Ø  Is this the right approach?
Ø  Is it possible to define generally accepted
requirements? Can we reach a best practice for
testing a delegation of a domain?
Ø  Can we reach the point where different tools test
the same thing? – If two come to different
conclusion, one is probably wrong?
Ø  Your thoughts?
14
Merci !
www.afnic.fr
contact@afnic.fr
Twitter : @AFNIC
Facebook : afnic.fr