From: Scott Morris (smorris@ipexpert.com)
Date: Thu Apr 10 2008 - 08:18:08 ART
No, I think it's more of a jello-like substance. But apparantly can suck in
and contain things fairly well. :)
Scott
-----Original Message-----
From: Salau, Yemi [mailto:yemi.salau@siemens.com]
Sent: Thursday, April 10, 2008 4:03 AM
To: smorris@ipexpert.com; Larry; ccielab@groupstudy.com
Subject: RE: RFC 3330 Network Ranges
Well, here is a more comprehensive list from RFC3330 (an excerpt), I think
Larry was kind of looking for this list within the DocCD so he can refer to
it in the Lab incase it comes up, which is highly unlikely!
But I admire your Brain cells Scott! What on earth is it made of, huh?
Ultra-integrated-semiconductor-high-definition-chips?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++
2. Global and Other Specialized Address Blocks
0.0.0.0/8 - Addresses in this block refer to source hosts on "this"
network. Address 0.0.0.0/32 may be used as a source address for this
host on this network; other addresses within 0.0.0.0/8 may be used to
refer to specified hosts on this network [RFC1700, page 4].
10.0.0.0/8 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. Addresses within this
block should not appear on the public Internet.
14.0.0.0/8 - This block is set aside for assignments to the
international system of Public Data Networks [RFC1700, page 181]. The
registry of assignments within this block can be accessed from the
"Public Data Network Numbers" link on the web page at
http://www.iana.org/numbers.html. Addresses within this block are
assigned to users and should be treated as such.
24.0.0.0/8 - This block was allocated in early 1996 for use in
provisioning IP service over cable television systems. Although the
IANA initially was involved in making assignments to cable operators,
this responsibility was transferred to American Registry for Internet
Numbers (ARIN) in May 2001. Addresses within this block are assigned
in the normal manner and should be treated as such.
39.0.0.0/8 - This block was used in the "Class A Subnet Experiment"
that commenced in May 1995, as documented in [RFC1797]. The
experiment has been completed and this block has been returned to the
pool of addresses reserved for future allocation or assignment. This
block therefore no longer has a special use and is subject to
allocation to a Regional Internet Registry for assignment in the
normal manner.
127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].
128.0.0.0/16 - This block, corresponding to the numerically lowest of
the former Class B addresses, was initially and is still reserved by
the IANA. Given the present classless nature of the IP address
space, the basis for the reservation no longer applies and addresses
in this block are subject to future allocation to a Regional Internet
Registry for assignment in the normal manner.
169.254.0.0/16 - This is the "link local" block. It is allocated for
communication between hosts on a single link. Hosts obtain these
addresses by auto-configuration, such as when a DHCP server may not
be found.
172.16.0.0/12 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. Addresses within this
block should not appear on the public Internet.
191.255.0.0/16 - This block, corresponding to the numerically highest
to the former Class B addresses, was initially and is still reserved
by the IANA. Given the present classless nature of the IP address
space, the basis for the reservation no longer applies and addresses
in this block are subject to future allocation to a Regional Internet
Registry for assignment in the normal manner.
192.0.0.0/24 - This block, corresponding to the numerically lowest of
the former Class C addresses, was initially and is still reserved by
the IANA. Given the present classless nature of the IP address
space, the basis for the reservation no longer applies and addresses
in this block are subject to future allocation to a Regional Internet
Registry for assignment in the normal manner.
192.0.2.0/24 - This block is assigned as "TEST-NET" for use in
documentation and example code. It is often used in conjunction with
domain names example.com or example.net in vendor and protocol
documentation. Addresses within this block should not appear on the
public Internet.
192.88.99.0/24 - This block is allocated for use as 6to4 relay
anycast addresses, according to [RFC3068].
192.168.0.0/16 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. Addresses within this
block should not appear on the public Internet.
198.18.0.0/15 - This block has been allocated for use in benchmark
tests of network interconnect devices. Its use is documented in
[RFC2544].
223.255.255.0/24 - This block, corresponding to the numerically
highest of the former Class C addresses, was initially and is still
reserved by the IANA. Given the present classless nature of the IP
address space, the basis for the reservation no longer applies and
addresses in this block are subject to future allocation to a
Regional Internet Registry for assignment in the normal manner.
224.0.0.0/4 - This block, formerly known as the Class D address
space, is allocated for use in IPv4 multicast address assignments.
The IANA guidelines for assignments from this space are described in
[RFC3171].
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]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++
3. Summary Table
Address Block Present Use Reference
---------------------------------------------------------------------
0.0.0.0/8 "This" Network [RFC1700, page 4]
10.0.0.0/8 Private-Use Networks [RFC1918]
14.0.0.0/8 Public-Data Networks [RFC1700, page 181]
24.0.0.0/8 Cable Television Networks --
39.0.0.0/8 Reserved but subject
to allocation [RFC1797]
127.0.0.0/8 Loopback [RFC1700, page 5]
128.0.0.0/16 Reserved but subject
to allocation --
169.254.0.0/16 Link Local --
172.16.0.0/12 Private-Use Networks [RFC1918]
191.255.0.0/16 Reserved but subject
to allocation --
192.0.0.0/24 Reserved but subject
to allocation --
192.0.2.0/24 Test-Net
192.88.99.0/24 6to4 Relay Anycast [RFC3068]
192.168.0.0/16 Private-Use Networks [RFC1918]
198.18.0.0/15 Network Interconnect
Device Benchmark Testing [RFC2544]
223.255.255.0/24 Reserved but subject
to allocation --
224.0.0.0/4 Multicast [RFC3171]
240.0.0.0/4 Reserved for Future Use [RFC1700, page 4]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++
Many Thanks
Yemi Salau
-----Original Message-----
From: Scott Morris [mailto:smorris@ipexpert.com]
Sent: Wednesday, April 09, 2008 5:37 PM
To: Salau, Yemi; 'Larry'; ccielab@groupstudy.com
Subject: RE: RFC 3330 Network Ranges
Search the archives for more detail (I wrote some a while back).
Off the top of my head:
1. RFC 1918 addresses
10.0.0.0/8
172.16.0.0/12
192.168.0.0/1
2. Loopbacks
127.0.0.0/8
3. AutoNet
169.254.0.0/16
4. First and Last Class A, Class B, Class C
0.0.0.0/8
127.0.0.0/8 (same as loopbacks)
128.0.0.0/16
191.255.0.0/16
192.0.0.0/24
223.255.255.0/24
5. Multicast & Expirimental
224.0.0.0/4
240.0.0.0/4
6. Couple of oddball things
192.0.2.0/24
198.18.0.0/15
There were some others that have been deprecated (namely, they've been
assigned to RIR's and end-companies!)
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Salau, Yemi
Sent: Wednesday, April 09, 2008 11:26 AM
To: Larry; ccielab@groupstudy.com
Subject: RE: RFC 3330 Network Ranges
So funny mate!
Actually I feel your pain ... but I can assure you everything will be
alright.
I wouldn't expect Cisco to ask you to do RFC3330 though, except if they
provide this reference in the Lab workbook itself. ie. they could provide a
table similar to that of http://www.faqs.org/rfcs/rfc3330.html
The truth is I would save myself the worry craming such lists, CCIE lab is
more articulate than that. You seldom need to cram things, however, you have
to know the basic RFCs such as RFC1918 and RFC1700
I've also searched through the DocCD, can't find any detailed outline of the
RFC3330 addresses, if someone else find something, please let us know.
Many Thanks
Yemi Salau
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Larry
Sent: Wednesday, April 09, 2008 4:08 PM
To: ccielab@groupstudy.com
Subject: RFC 3330 Network Ranges
Hello,
Was wondering if anyone knew of a reference in the Doc CD that covers the
3330 ranges. I have a requirement to block all ranges defined by this RFC
but can not for the life of me find it on the Doc CD. Would something like
this even be asked knowing it would require the memorization of the specific
RFC's if not found in the CD?? I can see 1918 being asked as it is readily
used throughout but not the 20 or so ranges in 3330.
At this point I have 4 weeks left and can barely remember where my house is
let alone memorizing anything else. Thanks all!
Larry
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:50 ART