Rfc 4648

This RFC proposes to document how IETF Subrfc4871 defines
functions for implementing the IANA DNS SRV 1.1 SRV
information from a top-level authoritative domain i.e.,
a domain that it doesn't control.
This RFC seeks to
implement function 2 of SRV documentation found in RFC 4648.
RFC 4648 defines functions for finding the version 1
and 2 IANA SRV information of a domain.

Subject:

Tuning Sizing and Limitations of ICANN Domain Names

Issued:

(written to by M. Gropp)

Status:

Present

Additional Comments:

Both IANA and ICANN have addressed the need for
sizing ICANN domain names. Specifically the ICANN
domains are over 100,000 domain names, while IANA has
64,000.
This documentation proposes to evaluate
using larger domain names, which could allow for
sizing the entire IANA set. The proposal isn't
feasible for use in IPv4 name-resolution due to both
bound
routes/internets, but an attempt is made to make an
alternative set available via non-routable ICANN names.
RFC 4648 specifies how to read IANA SRV 1.1 info
from DNS root servers in top-level domains, and the
problem is the domain name itself has to be mapped to
something visible on the IANA DNS root servers; no less
than 12 domains per root server are excluded in this
RFC.
Non-Routable Names
Non-routable names are names that don't have
any associated real, routable domain for the name to
fall under in order to create a domain name.
Non-routable names are not suitable for IPv4
domain name resolution due to routing limitations and are
not suitable for ICANN domains either due to the
ability to route them via a "proto-domain"
alias.
Pending Moved, Version 1 of RFC 4648 was authored by
Marc Gropp, under the name "Non-Routable Names".
Moved
This RFC will be expanded to use a non-routable name
for the IANA DNS root if necessary.