BIND 10 #809: Create tickets for remaining RR types
BIND 10 Development
do-not-reply at isc.org
Tue Jul 12 09:21:30 UTC 2011
#809: Create tickets for remaining RR types
-------------------------------------+-------------------------------------
Reporter: | Owner:
stephen | Status: new
Type: task | Milestone: Year 3 Task
Priority: major | Backlog
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 0.0
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by shane):
There are several categories of missing RR types:
* standard types, defined in IETF RFCs
* standard types, defined in other documents
* experimental types, defined in IETF RFCs
* obsolete types, defined in IETF RFCs
* proposed types, published in IETF drafts
* old proposed types, published in expired IETF drafts
I propose to use the priority 'minor' for standard types, and 'trivial'
for all other types. None of these is very important, but some are even
less important than others!
--
Ticket URL: <http://bind10.isc.org/ticket/809#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list