Subject: [DNSOP] Fwd: draft-andrews-dnsop-update-parent-zones-01.txt

From: Mark Andrews <[email-masked]>
Date: Wed, 09 Oct 2013 12:25:34 +1100

------- Forwarded Message

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: [email-masked]
To: Mark Andrews <[email-masked]>, M. Andrews <[email-masked]>
Subject: New Version Notification for
	draft-andrews-dnsop-update-parent-zones-01.txt
Message-ID: <[email-masked]>
Date: Tue, 08 Oct 2013 17:31:48 -0700

A new version of I-D, draft-andrews-dnsop-update-parent-zones-01.txt
has been successfully submitted by M. Andrews and posted to the
IETF repository.

Filename:	 draft-andrews-dnsop-update-parent-zones
Revision:	 01
Title:		 Updating Parent Zones
Creation date:	 2013-10-09
Group:		 Individual Submission
Number of pages: 5
URL:             http://www.ietf.org/internet-drafts/draft-andrews-dnsop-up=
date-parent-zones-01.txt
Status:          http://datatracker.ietf.org/doc/draft-andrews-dnsop-update=
- -parent-zones
Htmlized:        http://tools.ietf.org/html/draft-andrews-dnsop-update-pare=
nt-zones-01
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-andrews-dnsop-upd=
ate-parent-zones-01

Abstract:
   DNS UPDATE was developed to allow DNS zones to be updated.

   There is a perception that UPDATE can not be used in conjuction with
   the Registry, Registar, Registrant (RRR) model to update a zone.

   This document explains how UPDATE can be used in the RRR model.

                                                                           =
       =

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

------- End of Forwarded Message