Hi all,

Comments on this document in this list would be most welcome.

My idea was that if the wg liked it, it might be adopted in the interests of producing a BCP. With hindsight, I should have called this "empty-mname" rather than "missing-mname", but really, what's in a name.

Now that I actually read the abstract I see at least one typo. Perhaps I should have read before submitting (imagine that!). Apologies; s/ usual purpose/useful purpose/.


Joe

Begin forwarded message:

From: IETF I-D Submission Tool <[EMAIL PROTECTED]>
Date: 27 June 2008 16:20:46 GMT-04:00
To: [EMAIL PROTECTED]
Subject: New Version Notification for draft-jabley-dnsop-missing- mname-00


A new version of I-D, draft-jabley-dnsop-missing-mname-00.txt has been successfuly submitted by Joe Abley and posted to the IETF repository.

Filename:        draft-jabley-dnsop-missing-mname
Revision:        00
Title:           Indicating Non-Availability of Dynamic Updates in the DNS
Creation_date:   2008-06-27
WG ID:           Independent Submission
Number_of_pages: 7

Abstract:
The Start of Authority (SOA) Resource Record (RR) in the Domain Name
System (DNS) specifies various parameters related to the handling of
data in DNS zones.  These parameters are variously used by authority-
only servers, caching resolvers and DNS clients to guide them in the
way that data contained within particular zones should be used.

One particular field in the SOA RR is known as MNAME, which is used
to specify the "Primary Master" server for a zone.  This is the
server to which Dynamic Updates are sent by clients.  Many zones do
not accept updates using the Dynamic Update mechanism, and any such
DNS UPDATE messages which are received provide no usual purpose.  For
such zones it may be preferable not to receive updates from clients
at all.

This document proposes a convention by which a zone operator can
signal to clients that a particular zone does not accept Dynamic
Updates.



The IETF Secretariat.




_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to