Why is the first element left out:
1. Define the processes by which Domain Name System (DNS) software
may be efficiently and correctly administered, configured, and
operated on Internet networks. This will include root zone
name servers, gTLD name servers, name servers for other DNS
zones, iterative DNS resolvers, and recursive DNS resolvers.
As part of this effort, the group will produce documents
explaining to the general Internet community what processes
and mechanisms should be employed for the effective management
and operation of DNS software.
It seems to me the issues outlined in the current charter element above are
still a fundamental and important part of the DNSOP mission, particularly with
respect to the ICANN MoU and RFC 2870, which give a substantial role to the IETF
on DNS Root server operations.
Has this change been discussed with ICANN? If so, what is the input from ICANN?
If the DNSOP group is to abandon the topics in section 1, what group is going to
take over these subjects? Is the IETF planning to abdicate its role in these
DNS operations subjects? Particularly DNS root server operations? If so, to what
standards organization should ICANN and others go to for root server engineering
standards and operations guidance?
I hope this omission is an oversight. If not, then a great deal more
coordination and discussion is necessary before simply re-chartering DNSOP and
leaving out this rather important subject matter from the charter.
--Dean
On Tue, 21 Mar 2006, Peter Koch wrote:
> Dear WG,
>
> as you might have seen on the agenda for tomorrow's meeting we'd like to
> discuss the rechartering of the dnsop WG. This is a text for the general
> mission statement, slightly adjusting the focus:
>
> -----------------------------------------------------------------------------
>
> The DNS Operations Working Group will develop and review guidelines for the
> correct, efficient and secure configuration of DNS authoritative servers,
> resolvers, and DNSSEC validators. Target audiences for those guidelines
> are zone administrators as well as software developers who provide tools
> for DNS zone administration or server/resolver/validator configuration.
>
> The group will perform the following activities:
>
> 1) develop or review guidelines for chosing zone configuration
> parameters that affect inter-server or server-resolver communication,
> including but not limited to SOA RR parameters, TTL values, and glue
> information
>
> 2) develop or review guidelines for any DNSSEC specific operational
> parameters, such as key length or key validity periods
>
> 3) develop or review operational guidelines that address the specifics of
> IPv4/v6 coexistence and transition
>
> 4) review the use of existing DNS frameworks (SRV, DDDS) in other protocols,
> especially focussing on operational consequences and scalability
>
> -----------------------------------------------------------------------------
>
> The old charter can be found at
> <http://www.ietf.org/html.charters/dnsop-charter.html>
>
> Please send comments to this list, during tomorrows session or on jabber
> <[EMAIL PROTECTED]> 2120-2320 UTC. We'll have to talk about
> milestones.
>
> -Peter
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>
>
--
Av8 Internet Prepared to pay a premium for better service?
www.av8.net faster, more reliable, better service
617 344 9000
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
