Re: draft-ietf-dnsop-inaddr-required-03.txt

[John Schnizlein <jschnizl@cisco.com>]

Section 4 contains this:
   All IP address space which is assigned and in use SHOULD be resolved
   by IN-ADDR records. All PTR records MUST use canonical names.

Is this intended to outlaw the use of wildcards?
Is there a problem with explaining problems with wildcard use in in-addr?

There was a time when I received (possibly bad) advice to use wildcard
entries for subnets that contained what were called "consumer" only hosts.
This enabled service from the version of TCP wrappers at the time that
only checked for some DNS claim of responsibility for the address, but
did not work for those that performed double-reverse, checking the match
of the forward record against the original address.

John

At 08:15 AM 3/6/2002, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the Domain Name Server Operations Working Group of the IETF.
>
>        Title           : Requiring DNS IN-ADDR Mapping
>        Author(s)       : D. Senie
>        Filename        : draft-ietf-dnsop-inaddr-required-03.txt
>        Pages           : 5
>        Date            : 05-Mar-02
>        
>Mapping of addresses to names has been a feature of DNS. Many sites,
>implement it, many others don't. Some applications attempt to use it
>as a part of a security strategy. The goal of this document is to
>encourage proper deployment of address to name mappings, and provide
>guidance for their use.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-dnsop-inaddr-required-03.txt
>
>To remove yourself from the IETF Announcement list, send a message to 
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>        "get draft-ietf-dnsop-inaddr-required-03.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-ietf-dnsop-inaddr-required-03.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <20020305134121.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-dnsop-inaddr-required-03.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsop-inaddr-required-03.txt>