draft-ietf-dnsop-name-server-management-reqs-03.txt		draft-ietf-dnsop-name-server-management-reqs-04.txt
	DNSOP W. Hardaker		DNSOP W. Hardaker
	Internet-Draft Sparta, Inc.		Internet-Draft Sparta, Inc.
	Intended status: Informational May 4, 2009		Intended status: Informational June 11, 2010
	Expires: November 5, 2009		Expires: December 13, 2010
	Requirements for Management of Name Servers for the DNS		Requirements for Management of Name Servers for the DNS
	draft-ietf-dnsop-name-server-management-reqs-03.txt		draft-ietf-dnsop-name-server-management-reqs-04.txt
			Abstract
			Management of name servers for the Domain Name System (DNS) has
			traditionally been done using vendor-specific monitoring,
			configuration and control methods. Although some service monitoring
			platforms can test the functionality of the DNS itself there is not
			an interoperable way to manage (monitor, control and configure) the
			internal aspects of a name server itself.
			This document discusses the requirements of a management system for
			name servers and can be used as a shopping list of needed features
			for such a system.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79. This document may contain material		provisions of BCP 78 and BCP 79.
	from IETF Documents or IETF Contributions published or made publicly
	available before November 10, 2008. The person(s) controlling the
	copyright in some of this material may not have granted the IETF
	Trust the right to allow modifications of such material outside the
	IETF Standards Process. Without obtaining an adequate license from
	the person(s) controlling the copyright in such materials, this
	document may not be modified outside the IETF Standards Process, and
	derivative works of it may not be created outside the IETF Standards
	Process, except to format it for publication as an RFC or to
	translate it into languages other than English.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on December 13, 2010.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on November 5, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2010 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents in effect on the date of		Provisions Relating to IETF Documents
	publication of this document (http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info) in effect on the date of
	Please review these documents carefully, as they describe your rights		publication of this document. Please review these documents
	and restrictions with respect to this document.		carefully, as they describe your rights and restrictions with respect
			to this document. Code Components extracted from this document must
	Abstract		include Simplified BSD License text as described in Section 4.e of
			the Trust Legal Provisions and are provided without warranty as
	Management of name servers for the Domain Name System (DNS) has		described in the Simplified BSD License.
	traditionally been done using vendor-specific monitoring,
	configuration and control methods. Although some service monitoring
	platforms can test the functionality of the DNS itself there is not
	an interoperable way to manage (monitor, control and configure) the
	internal aspects of a name server itself.
	This document discusses the requirements of a management system for		This document may contain material from IETF Documents or IETF
	name servers and can be used as a shopping list of needed features		Contributions published or made publicly available before November
	for such a system.		10, 2008. The person(s) controlling the copyright in some of this
			material may not have granted the IETF Trust the right to allow
			modifications of such material outside the IETF Standards Process.
			Without obtaining an adequate license from the person(s) controlling
			the copyright in such materials, this document may not be modified
			outside the IETF Standards Process, and derivative works of it may
			not be created outside the IETF Standards Process, except to format
			it for publication as an RFC or to translate it into languages other
			than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 5		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 5
	1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 6		1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 6
	1.1.2. Document Layout and Requirements . . . . . . . . . . . 6		1.1.2. Document Layout and Requirements . . . . . . . . . . . 6
	2. Management Architecture Requirements . . . . . . . . . . . . . 6		2. Management Architecture Requirements . . . . . . . . . . . . . 6
	2.1. Expected Deployment Scenarios . . . . . . . . . . . . . . 6		2.1. Expected Deployment Scenarios . . . . . . . . . . . . . . 6
	2.1.1. Zone Size Constraints . . . . . . . . . . . . . . . . 6		2.1.1. Zone Size Constraints . . . . . . . . . . . . . . . . 6
End of changes. 8 change blocks.
	42 lines changed or deleted		42 lines changed or added
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/