A new Request for Comments is now available in online RFC libraries.


        BCP 20:
	RFC 2317:

        Title:      Classless IN-ADDR.ARPA delegation
	Author(s):  H. Eidnes, G. de Groot, P. Vixie
        Status:     Best Current Practice
	Date:       March 1998
        Mailbox:    Havard.Eidnes@runit.sintef.no,
		    GeertJan.deGroot@bsdi.com,
		    paul@vix.com
	Pages:      10
        Characters: 17744
        Updates/Obsoletes: None

        URL:        ftp://ftp.isi.edu/in-notes/rfc2317.txt


This document describes a way to do IN-ADDR.ARPA delegation on
non-octet boundaries for address spaces covering fewer than 256
addresses.  The proposed method should thus remove one of the
objections to subnet on non-octet boundaries but perhaps more
significantly, make it possible to assign IP address space in smaller
chunks than 24-bit prefixes, without losing the ability to delegate
authority for the corresponding IN-ADDR.ARPA mappings.  The proposed
method is fully compatible with the original DNS lookup mechanisms
specified in [1], i.e. there is no need to modify the lookup algorithm
used, and there should be no need to modify any software which does
DNS lookups.

This document is a product of the DNS IXFR, Notification, and Dynamic
Update Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@ISI.EDU.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute