A Suggested Scheme for DNS Resolution of Networks and Gateways
RFC 4183

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be: 
         draft-warnicke-network-dns-resolution-06.txt 

The IESG has no problem with the publication of 'A Suggested Scheme for 
DNS Resolution of Networks and Gateways' 
<draft-warnicke-network-dns-resolution-06.txt> as an Informational RFC. 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9969&rfc_flag=0) 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is David Kessens.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-warnicke-network-dns-resolution-06.txt


The process for such documents is described at http://www.rfc-editor.org/indsubs.html.

Thank you,

The IESG Secretary

Technical Summary

This document suggests a method of using DNS to determine the network
that contains a specified IP address, the netmask of that network,
and the address(es) of first-hop routers(s) on that network.  This
method supports variable length subnet masks, delegation of subnets
on non-octet boundaries, and multiple routers per subnet.

Protocol Quality

David Kessens reviewed this document for the IESG according to the guidelines
in RFC 3932.

IESG Note:

RFC Editor, please place the following IESG note either in or immediately
following the "Status of this Memo" section:

This RFC is not a candidate for any level of Internet Standard.
The IETF disclaims any knowledge of the fitness of this RFC for
any purpose and notes that the decision to publish is not based on
IETF review apart from IESG review for conflict with IETF work.
The RFC Editor has chosen to publish this document at its
discretion.  See RFC 3932 for more information.