draft-ietf-dnsext-dns-protocol-profile-01

1
draft-ietf-dnsext-dns-protocol-profile-01

• George Michaelson
• APNIC

2
Goals

• Request from RAI ADs
• Guide to implementers of what modern DNS really
  means
• Also for operators, purchasors others
• Is s/w compliant or not?
• What needs upgrading?

3
Goals

• Complaints from users
• Enum edns0, general glue issues
• Deployed services doing the wrong things
• History of bad implementations
• 25 Years old Time for a spring clean

4
Structure

• Consider DNS software by unit/function
• ie architectural element in global DNS
• Authoritative Server
• Stub Resolver
• Recursive Resolver
• Middleboxes
• Home routers, proxies, embedded systems

5
Structure

• Cross function issues
• Common requirements
• Things like EDNS0
• Avoid application specific issues
• Guidance but not normative possible

6
Approach

• Avoid new normative language
• Prefer -bis process for existing docs
• Call for deprecation where relevant
• If new work, propose as WG item
• Potential for document to be easy to revise,
  update
• Index into normative-language bearing docs

7
Methodology

• Subversion repository by section
• Elevate issues into trac
• Discuss on M/L
• divide and conquer approach
• Small edit team
• Joe Abley, Stephane Bortzemeyer Florian Weimer,
  Joao Damas
• ggm is document editor
• More help appreciated..

8
Status

• Holding at -01 draft for this meeting
• Regular updates as work progresses
• Is the structure/approach appropriate?
• Some ML discussion suggests alternates