> On Tue, 20 Jun 2006, [EMAIL PROTECTED] wrote:
> > Title : Locally-served Zones
> > Author(s) : M. Andrews
> > Filename : draft-ietf-dnsop-default-local-zones-00.txt
> > Pages : 10
> > Date : 2006-6-20
>
> As I said before, the draft includes section on RFC 3330 zones (such
> as the broadcast and loopback), but it not in sync with RFC 3330
> and/or does not justify the reason. Most importantly, it's not clear
> why 255.255.255.255.IN-ADDR.ARPA is there instead of the whole 255/8
> or even 240/4.
As far as I am concerned it is perfectly in sync with RFC 3330.
240.0.0.0/4 - This block, formerly known as the Class E address
space, is reserved. The "limited broadcast" destination address
255.255.255.255 should never be forwarded outside the (sub-)net of
the source. The remainder of this space is reserved for future use.
[RFC1700, page 4]
The address space is RESERVED not ASSIGNED. You really do
not want to put addresses here that have the potential to
be used on the Internet as a whole. 255.255.255.255 is the
one address that has been cut out of 240.0.0.0/4.
> It is debatable whether any of the others (e.g., 198.18.0.0/15) should
> be on that list.
>
> --
> Pekka Savola "You each name yourselves king, yet the
> Netcore Oy kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
