In 1985, RFC 950 defined a standard procedure to support the subnetting, or division, of
a single Class A, B, or C network number into smaller pieces. Subnetting was
introduced to overcome some of the problems that parts of the Internet were beginning
to experience with the classful two-level addressing hierarchy:
- Internet routing tables were beginning to grow.
- Local administrators had to request another network number from the Internet
before a new network could be installed at their site.
Both of these problems were attacked by adding another level of hierarchy to the IP
addressing structure. Instead of the classful two-level hierarchy, subnetting supports a
three-level hierarchy. Figure 6 illustrates the basic idea
a single Class A, B, or C network number into smaller pieces. Subnetting was
introduced to overcome some of the problems that parts of the Internet were beginning
to experience with the classful two-level addressing hierarchy:
- Internet routing tables were beginning to grow.
- Local administrators had to request another network number from the Internet
before a new network could be installed at their site.
Both of these problems were attacked by adding another level of hierarchy to the IP
addressing structure. Instead of the classful two-level hierarchy, subnetting supports a
three-level hierarchy. Figure 6 illustrates the basic idea
0 comments:
Post a Comment