YT YouTube2Text

YouTube2Text → Transcripts → Designing IP Addressing and Selecting Routing Protocols Part 1

Designing IP Addressing and Selecting Routing Protocols Part 1 — Transcript

by Santelmo · 6,366 words · 1,337 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:04hi hello there
0:05welcome to designing ip addressing and
0:07selecting routing protocols
0:11this video lecture begins with a
0:14discussion of the design of an
0:16ip address or ipv4 addressing scheme
0:20it continues with an introduction to
0:22ipv6 or ipv version 6
0:25and a discussion of ipb4 to ipv6
0:29migration strategies afterwards
0:32it describes considerations for
0:34selecting the most appropriate network
0:36routing protocol
0:38first routing protocol features are
0:40discussed
0:41followed by a description of various
0:43routing protocols appropriate
0:46for the enterprise use the video
0:49discusses why certain protocols are
0:51suitable for specific modules
0:53in the enterprise architecture it
0:56concludes
0:57with a description of some advanced
1:00routing protocol deployment features
1:02including redistribution
1:05filtering and summarization
1:08let's get started designing ip
1:11addressing
1:16designing an ip addressing plan this
1:18section
1:19explores private and public address
1:22types
1:23how to determine the size of the network
1:25in relation to addressing plan
1:28and how to plan an ip addressing
1:30hierarchy
1:32this section concludes with a discussion
1:35of various ip address assignment
1:38and name resolution methods
1:43prerequisite knowledge this includes
1:46ipv4 address
1:47and mask structure ipv4 classes
1:51and cider or the cidr
1:54static addressing dynamic addressing
1:57with dhcp
1:59dns private and public addresses
2:03the network address translation and the
2:05port address translation static
2:08network address translation dynamic
2:11network address translation
2:12and overloading so this are the
2:15prerequisite topic
2:17prior to designing ip addressing
2:22private and public ipb4 addresses
2:26recall from the previous video that ipb4
2:29or ip address space is divided into
2:32public
2:33and private spaces that is for
2:37ipv4 and ipv6
2:40private addresses are reserved ip
2:43addresses
2:44that are used to implement
2:47within the company's network so that is
2:50used internally
2:52within the organization's network not on
2:55the internet
2:56private addresses must therefore be
2:58mapped to companies external registered
3:01addresses
3:02when sending anything on the internet
3:05public ip addresses are provided
3:07for external communication
3:10the figure illustrates the use of
3:13private and public addresses
3:15in the network so what are the
3:17guidelines for the use of private and
3:19public addresses
3:21in the enterprise network now as shown
3:24here in the figure
3:26the typical enterprise network uses both
3:29private and uh public ip addresses
3:33so private ip addresses are used
3:35throughout the enterprise campus
3:40also on the enterprise branch and
3:42enterprise
3:43teleworker modules the following modules
3:47include public addresses you've got the
3:51internet connectivity
3:55where public ip addresses are used for
3:58internet connections
3:59and publicly accessible servers
4:02you also have that on e-commerce module
4:06where public ip addresses are used for
4:09the database
4:10application and web servers the remote
4:14access and
4:15virtual private network or vpn module
4:18the enterprise data center module and
4:21the one and the metropolitan area
4:23network
4:23are mann and the side-to-side vpn module
4:27where public ip addresses are used for
4:30certain connections
4:35network size and ip addressing planning
4:39so determining the size of the network
4:42so the first step
4:43in designing an ip addressing plan is
4:46determining the size
4:48of the network to establish how many ip
4:51subnets and how many ip addresses
4:54are needed on each subnet
4:58so to gather this information we need to
5:01answer the following questions here
5:04first how many locations does the
5:07network consists of
5:09the designer must determine the number
5:11and type of
5:12locations next would be
5:15how many devices in each location needs
5:18addresses
5:21the network designer must determine the
5:23number of devices
5:25that need to be addressed including end
5:27systems
5:28router interfaces switches firewall
5:31interfaces
5:33and any other devices
5:36next would be what are the ip addressing
5:39requirements
5:40for individual locations so the designer
5:43must collect information about which
5:45system will use
5:47dynamic addressing which will use
5:50static addresses and which systems can
5:53use
5:54private instead of public addresses
5:59next would be what subnet size is
6:02appropriate
6:03based on the collected information about
6:05the number of
6:06networks and planned switch deployment
6:10the designer estimates the appropriate
6:12subnet size
6:13for example deploying a 48 port switches
6:17would mean that subnets with 64 host
6:20addresses
6:21would be appropriate assuming one device
6:25per port determining the network
6:29topology
6:30initially the designer should acquire a
6:33general picture
6:34of the network topology this will help
6:36determine
6:37the correct information together about
6:39network size
6:40and its relation to the ip addressing
6:43plan
6:44with this general network topology
6:46information the designer determines
6:49the number of locations location types
6:52and their correlations for example the
6:55network location information for the
6:57topology
6:58shown in the figure is shown in the
7:00table on the next slide
7:02okay so basically this includes the size
7:06of individual locations
7:09so the network size in terms of the ip
7:12addressing plan
7:13relates to the number of devices and
7:15interfaces that needs
7:16an ip addresses to establish
7:20the overall network size in a simplistic
7:23way
7:24the designer determines the appropriate
7:26number of workstations
7:28servers the ip phones
7:31router interfaces switch management
7:34and layer 3 interfaces this also
7:37includes
7:38firewall interfaces okay or
7:41the other network devices at each
7:44location
7:45okay now this estimate provides the
7:48minimum overall number of ip addresses
7:51that are needed for the network so the
7:54table
7:55provides an ip addresses requirements by
7:57location
7:59for the topology shown in the figure
8:00from the previous slides
8:03so some additional addresses should be
8:06reserved
8:07to allow for seamless potential network
8:10growth
8:11the commonly suggested reserve is 20 for
8:14the main
8:15and regional offices and 10 for remote
8:18offices
8:19however this can vary from case to case
8:24the designer should carefully discuss
8:26future network growth
8:28with the organization's representative
8:30to obtain a more precise estimate
8:33of the required resources
8:39planning the ip addressing hierarchy so
8:42the ip addressing hierarchy influences
8:44network routing this section describes
8:47ip addressing hierarchy and how it
8:50reduces routing overhead
8:53this section discusses the issues
8:56that influence the ip addressing plan
8:59and the routing protocol choice
9:01including summarization
9:02fixed length subnet masking or the flsm
9:06variable length subnet masking are the
9:08vlsm
9:09and the classful and classless routing
9:11protocols
9:13so benefits of hierarchical addressing
9:16so a network designer decides
9:18how to implement the ip addressing
9:21hierarchy
9:22based on the network's size geography
9:25and
9:25topology in a large network
9:29hierarchy within the ip addressing plan
9:31is mandatory
9:32for a stable network including stable
9:35routing tables
9:37for the following reason a planned
9:39hierarchical ip addressing structure
9:42with room for growth is recommended for
9:45networks of
9:46all sizes so
9:49this includes influence of ip addressing
9:53on routing okay so
9:57an ip addressing plan influences the
9:59network's overall routing
10:01before allocating blocks of ip addresses
10:04to various parts of the network
10:06and assigning ip addresses to devices
10:09consider the criteria for an appropriate
10:11and effective ip addressing scheme
10:14so routing stability service
10:16availability
10:17network scalability and modularity are
10:20some of the crucial and preferred
10:21network characteristics
10:23that are directly affected by ip address
10:27allocation
10:28and deployment so the next one would be
10:31the modular design
10:33and scalable solutions so whether
10:36building
10:36a new network or adding a new service on
10:40top of the existing infrastructure
10:42a modular design helps to deliver a
10:45long-term
10:46scalable solution so ip addressing
10:49modularity
10:50allows the aggregation of routing
10:52information on hierarchical
10:54basis next would be route aggregation
10:59so route aggregation is used to reduce
11:02the routing overhead
11:03and improve routing stability and
11:05scalability
11:07so however to implement route
11:10aggregation
11:11a designer must be able to divide the
11:13network into contiguous ip address areas
11:17and must have a solid understanding of
11:20ip address assignment
11:22route aggregation and hierarchical
11:24routing
11:26so also there is a summarization groups
11:30so to reduce the routing overhead in a
11:33large network
11:34a multi-level hierarchy might be
11:36required
11:37the depth of the hierarchy depends on
11:40the network size
11:41and the size of the highest level
11:43summarization group
11:44so the figure here shows an example of
11:48network hierarchy
11:51so a typical organization has up to
11:53three levels of
11:55the hierarchy so the first level
11:58the network locations typically
12:00represented the first level of the
12:01hierarchy in the enterprise network
12:04so each location is typically
12:08represents a group of summarized subnets
12:12known as summarization group so the
12:15second level
12:17okay so a second level of hierarchy can
12:19be done
12:20within the first level summarization
12:22group for example
12:24a large location can be divided into
12:26smaller summarization groups
12:28that represents the buildings or cities
12:31within that location
12:34not all first level summarization groups
12:36require a second level of
12:38the hierarchy okay
12:42and you've got also the third level
12:45so to further minimize the potential
12:47routing overhead and
12:48instability a third level of the
12:51hierarchy can exist
12:52within the second level summarization
12:54group
12:55okay so for example sections or floors
12:59within the individual buildings can
13:01represent the third
13:02summarization group
13:08so route summarization groups so what
13:11are the impact
13:12of poorly designed ip addressing
13:16so a poorly designed ip addressing
13:18scheme usually results
13:20in ip addresses that are randomly
13:23assigned
13:24on as needed basis in this case
13:28the ip addresses are most likely
13:31dispersed
13:32through the network with no thought as
13:35to whether they can be grouped or
13:37summarized a poor design provides
13:41no opportunity for dividing the network
13:44into contiguous areas okay
13:48and therefore no means of implementing
13:50route summarization
13:53now the benefits of route aggregations
13:57implementing a route aggregation on a
14:00border routers
14:01between contiguously addressed areas
14:03controls
14:04the routing table size okay
14:09so let's have an example
14:13of the hierarchical ip addressing and
14:15summarization planning
14:18okay now recall that the number of
14:20available host
14:21addresses on a subnet is calculated by
14:24the formula
14:26two raised to h okay or any variable
14:31minus two okay so where h is the number
14:34of host bits
14:35okay so the number of bits set to zero
14:39in the subnet mask so the first two
14:42columns in the table
14:44shows the location and the number of ip
14:47addresses
14:48required at each location for the sample
14:51network
14:53so the third column in this table is the
14:55next higher
14:56or the next highest power of two from
14:59the required number of addresses
15:01this value is used to calculate the
15:04required number of host bits
15:06okay and then assuming that the class b
15:09address
15:09for instance 172.16.
15:13is used to address this network
15:16so you might have the fifth column okay
15:18illustrate sample
15:20address blocks allocated to each
15:24location
15:26okay so basically if the san francisco
15:29campus requires
15:311290 so you won't be getting an exact
15:341290 so based on our formula 2 raised to
15:37h
15:38that would yield to 2048. so if you need
15:42441 that would drill to 512.
15:46okay and then if you need 21
15:49so you could get 64 there of course with
15:51the consideration of the future growth
15:57all right so this is a complete
16:01address block by location for san
16:04francisco campus
16:06so using the 172.16.0.0
16:10address block that is a class b network
16:13and
16:13after the careful planning for the
16:16redistribution of ip addresses
16:18so we have uh come up with this
16:21assignment
16:22of ip addresses per location
16:27okay so there are online tools that you
16:30can use
16:31to come up with this type of table
16:35okay so you don't have to manually
16:37compute
16:38okay the number of hosts
16:41needed and of course the division of the
16:44addresses
16:45within the block you just have to use
16:47that application you can go ahead and
16:49search that on the internet
16:54okay so another example is the
16:56hierarchical
16:57ip addressing plan okay so take note
17:00that
17:01from the topology that we have
17:04so basically that comprises of the san
17:07francisco campus
17:08the denver region and the houston region
17:11so summarization point basically is
17:14on the edge network okay so if it is on
17:18the denver region
17:19so that happens on the router connected
17:21to san francisco campus
17:24so details of routing remain within the
17:26area simplifying
17:28routing tables and reducing processing
17:30time
17:33so if you want to know more about this
17:35um ip addressing scheme you can go ahead
17:37and check
17:38the videos
17:42or the provided videos
17:45okay or the supplementary videos
17:48all right so next would be
17:52so on the summarization point okay
17:55on the summarized trout for instance
17:58172.16
17:598 is propagated on the rest of the
18:03network so basically
18:04it will not uh propagate
18:07addresses within the block so it has to
18:10be summarized at some point on the
18:12network
18:13to simplify and to minimize the use of
18:15the resources
18:17so for the main campus 2048 addresses
18:20are allocated
18:22so 11 host bits are required
18:25okay now this subnet is further divided
18:28into smaller subnets
18:30supporting floors or wiring flow sets
18:33now for the denver region 1024 addresses
18:38are allocated
18:3910 host bits are required okay
18:43now this address block is further
18:45divided into smaller subnets supporting
18:47buildings
18:48floors or wiring closets so that's how
18:51you plan
18:52distribution of ip addresses within the
18:55network
18:56and similarly for the houston region
19:00so there are about 1024 addresses
19:03which are also allocated and further
19:05subdivided
19:06okay as shown in the table from the
19:09previous slide
19:11all right so on this table here you've
19:13got houston
19:17now this figure illustrates one of the
19:20links
19:21in the denver region going down
19:24and how summarization is performed to
19:27reduce the routing update
19:29okay or the traffic generated by
19:32those routing updates
19:37managing ip addresses so there are a lot
19:40of ways
19:41on how to manage ip addresses
19:44so some includes using date cheap in the
19:47enterprise
19:49using dns in the enterprise and of
19:51course using the network address
19:52translation
19:53on the enterprise now using the http to
19:57assign an ip addresses
19:59so dhcp or dynamic host configuration
20:02protocol is used
20:03to provide dynamic ip address allocation
20:06to hosts
20:07so dhep uses a client server model
20:11the date cheap server can be windows
20:14server
20:14a unix based server or it could be a
20:17cisco ios device
20:19so cisco ios devices can also be dhcp
20:23relay agents
20:24and dhcp clients
20:28now using the dns or the domain name
20:30system
20:31for name resolution so to resolve
20:34symbolic names
20:35to actual network addresses applications
20:39use resolver or the name resolver
20:43programs
20:44which are usually part of the host
20:46operating system
20:48an application sends a query to a name
20:50resolver
20:51that resolves the request with either
20:54the local database host file or the dns
20:57server
20:59now when numerous hosts or names must be
21:02resolved to
21:03ip addresses statically defined
21:05resolution in hosts
21:08are widely to maintain okay
21:11so to use this process dns is used
21:15for name resolution so dns
21:19is a client server mechanism used to
21:21access a distributed
21:23database providing address to name
21:25resolution
21:27so a dns server is special software
21:30that usually resides on a dedicated
21:32hardware
21:33so dns servers are organized in
21:36hierarchical structure
21:38a dns server can query other dns servers
21:42to retrieve partial resolutions for a
21:44certain name
21:45for example one dns server could resolve
21:49say cisco.com and another could resolve
21:53www okay
21:56so next would be the use of the network
21:58address translation or not
22:00this is a process in which one or more
22:03local ip
22:04addresses is translated into one or more
22:08global ip addresses and vice versa in
22:12order to provide
22:13internet access to the local hosts
22:20now recommended practices for ip address
22:22assignment
22:24so we have the method here is either you
22:27assigned it
22:28okay statically or you assign it
22:30dynamically
22:32so strategic address assignment so
22:35infrastructure devices such as routers
22:37and switches
22:38should be given a static ip assignment
22:42okay now for the
22:45day gp of course the end user devices
22:48just like for instance if you are
22:50providing a free wi-fi
22:52access to the end user so we could put
22:55it in
22:56a day gpu or dynamic assignment okay
23:00now number of end user devices so
23:03well for static it could be up to 30 end
23:07user devices so if it is more than 30
23:09then it is recommended to use dhep
23:13so it's very hard to manually assign an
23:15ip address on multiple devices
23:19now in renumbering criteria so requires
23:22manual reconfiguration for all the hosts
23:26okay whereas for dhcp only the http
23:30server
23:31reconfiguration is needed so address
23:34tracking
23:35so it's easy address tracking for the
23:38static
23:38whereas for dynamic it requires
23:40additional dataship server configuration
23:43now additional parameters manual
23:46configurations of all
23:48hosts are required now for dhcp
23:52only the atp server needs to be
23:53configured
23:55now for high availability ip addresses
23:58are available at any time
24:01for dhcp so redundant day chip server
24:05is required now for security concerns
24:09well we've got minor security risk
24:13for this static assignment okay and then
24:16for
24:18dynamic so any device gets an ip address
24:23all right
24:26okay so let's have an ip assignment or
24:30ip address assignment methods in an
24:32enterprise network
24:34so what are the guidelines for assigning
24:37ip addresses
24:38in the enterprise network so the typical
24:41enterprise network uses both static and
24:44dynamic addresses
24:45assignment methods so as shown here in
24:47the figure
24:48the static ip address assignment method
24:51is typically used
24:52for campus network infrastructure
24:56okay and in all the modules of the
25:00enterprise
25:00edge the e-commerce the internet
25:03connectivity the remote access and vpn
25:05and the one-and-man and side-to-side vpn
25:08modules
25:10now static addresses are required for
25:12systems such as server
25:14or network devices in which the ip
25:17address must be known at all times
25:19for connectivity so general access
25:23or management all right
25:26so whenever you assign an ip address to
25:28the server or router interfaces or
25:30switches
25:31okay so for management purposes it is
25:34better to do
25:35a static assignment on them
25:38okay so also on the server form so it
25:41should be given
25:42a static ip assignment now for the end
25:45user
25:46we have to use dynamic so dynamic ip
25:49addresses
25:50or address assignment is used for
25:52assigning
25:53ip address to end user devices so
25:56including workstations
25:58iphones if you have ip phones and mobile
26:01devices
26:02on the network
26:06static versus dynamic name resolution
26:10so names are used to identify different
26:13hosts and resources
26:14on the network and to provide user
26:16friendly interaction
26:18with computers a name is
26:21much easier to remember than an ip
26:24address
26:25okay now this section covers the purpose
26:28of the name resolution
26:30provides information about different
26:32available name resolution
26:33strategies and discusses the domain name
26:36systems or dns name resolution
26:40now let's focus on the static versus
26:43dynamic
26:44okay the process of resolving a host
26:47name
26:48to an ip address can either be static or
26:51dynamic
26:53now following are the differences
26:56between these
26:57two methods okay now let's start with
27:02static okay now for the static
27:06with static name to ip address
27:08resolution
27:10both the administrative overhead and the
27:12configuration are very similar
27:14to those of the static address
27:16assignment strategy
27:18so the network administrator manually
27:21defines
27:22name to ip address resolutions
27:25by entering the name and ip address
27:27appears
27:28into the local database or the host file
27:32using either a graphical or text
27:35interface
27:36okay and then manual entries create
27:39additional work
27:40for the administrator so they must be
27:44entered on every host and are prone to
27:48errors and emissions that's a problem
27:50with static
27:51all right now for dynamic
27:55the dynamic name to ip address
27:57resolution a similar dynamic address
27:59assignment strategy
28:01the administrator has to enter the name
28:03to ip address resolutions only on a
28:05local dns server
28:07rather than on every host so the dns
28:11server
28:11then performs the name to ip address
28:14resolution so renumbering and renaming
28:17are easier
28:19with dynamic name to address or ip
28:22address resolution method
28:26recommended practices for name
28:28resolution
28:30okay so to select the desired name
28:32resolution method
28:34the following questions should be
28:36answered okay
28:37so first would be how many hosts
28:40required
28:41name resolution okay the number of hosts
28:45again for static up to 30 hosts
28:48and then if it is more than 30 hosts
28:50then go for dynamic
28:52name resolution all right
28:55next should be are applications that
28:57depend on the name resolution present
29:00so that should be answered
29:03all right application depending on the
29:05name resolution
29:06so if in static name resolution it is
29:10not recommended
29:11now it is more or best recommended
29:14on dynamic name resolution okay
29:18so next would be is the network isolated
29:21or
29:21it is connected to the internet so
29:24isolated network
29:25well static is applicable and so with
29:28dynamic
29:30okay next would be
29:34um if the network is isolated
29:37okay how frequently are new hosts added
29:41and how frequently do names change
29:45okay so this are the recommended
29:48processes
29:49for name resolution both for the use of
29:52the static name resolution
29:54and dynamic name resolution
29:59using dns for name resolution the figure
30:02illustrates the process of resolving an
30:05ip address
30:06using dns server okay so
30:09in here step one okay a user wants to
30:13browse maybe
30:14myweb.com because the host does not
30:18know the site's ip address it queries
30:21the dns server okay
30:24now step two okay
30:28so step two would be the dns server
30:31response
30:31with the appropriate ip address for
30:34instance
30:35for www.mywebs.com
30:40all right and then step three the host
30:43establishes a connection
30:46to the appropriate ip address which is
30:50www.myweb.com
30:52site
30:57example of locating the gp and dns
31:00servers in the network
31:02so dhcp and dns server locations in the
31:04network as illustrated
31:06in this diagram here okay the dhcp and
31:09dns servers can be located at multiple
31:12places in the network
31:14depending on the service that they
31:16support
31:17okay now for the enterprise campus the
31:20hcp and internal dns servers
31:22should be located on the server farm
31:25these servers
31:26should be redundant now for the
31:29remote location okay routers can provide
31:32the
31:32gp and dns at the enterprise
31:36edge okay now
31:39external dns server should be redundant
31:41for example
31:44uh two service provider facilities
31:47or one at the service uh provider
31:49facility
31:50and one in a demilitarized zone or dmz
31:54at the enterprise campus or remote data
31:58center
32:03ipv6 address structure so let us
32:06introduce
32:07ipv6 so ipv6 is a technology developed
32:12to overcome the limitations of the
32:15current standard
32:16ipb4 which allows and systems to
32:19communicate and forms the foundation
32:22of the internet as we know it today
32:25now this section on ipv6 specific design
32:29considerations
32:30provides an overview of ipv6
32:33features and addressing and explains
32:36the various ipv6 address types
32:40now the address assignment and name
32:42resolution strategies for ipv6
32:45are explored so the transition from ipv4
32:49to ipv6
32:50is discussed and the section concludes
32:53with brief description of the ipv6
32:57routing protocols now let's talk about
33:00the ipv6
33:02address format or structure so rather
33:05than using data decimal format
33:08so ipv6 addresses are written as
33:11hexadecimal numbers with columns
33:15between each set of four hexadecimal
33:17digits
33:18which is 16 bits which we refer to as
33:22hex okay so we like to call this one as
33:26the colon text format
33:28so the format is this one here
33:33okay where x is a 16-bit hexadecimal
33:36field
33:38so the sample address is provided for
33:40instance you've got this ip address or
33:42ipv6 address given to you here
33:45okay now the key point here is
33:48fortunately you can shorten the written
33:51form of ipv6 addresses
33:54leading zeros within each set of four
33:57hexadecimal digits
33:58can be omitted and a pair of columns
34:02can be used okay so like what we have
34:04here you've got pair of columns
34:07all right so once within
34:10an address that is to represent any
34:13successive
34:14zeros so for example the previous
34:17address can be shortened
34:19to the following so initially you are
34:22given this
34:22long ipv6 addresses okay or ipv6 address
34:27now the short annotation applying that
34:30principle
34:31omitting consecutive zeros
34:34and replacing it with a pair of columns
34:39so you'll have this simplified ipv6
34:42address
34:44okay again the key point a pair of
34:47columns
34:48can be used only once within
34:51the ipv6 addresses so this is because an
34:55ipv6 address
34:57parser identifies the number of missing
34:59zeros
35:00by separating the two parts and entering
35:02zero until the 128 bits are complete
35:06okay now if two semicolons
35:10or if two columns notations were to be
35:14placed
35:14in the address there would be no way
35:18to identify the size of each block of
35:21zeros okay now similar to ipb for subnet
35:26mask
35:26can be written as a prefix for example
35:29slash 24
35:31ipv6 uses prefixes
35:34to indicate the number of bits of
35:36network or subnet information
35:43now let's talk about ipv6 features
35:48okay the ability to scale networks for
35:50future demands
35:51requires a limitless supply of ip
35:54addresses
35:56and improved mobility ipv6 combines
36:00expanded addressing
36:02with a more efficient and feature-rich
36:05header
36:05to meet these demands now ipv6 satisfies
36:10the increasingly complex requirements
36:13for hierarchical addressing that ipb4
36:17does not support so what are the main
36:20benefits
36:20of ipv6 okay so first
36:25you've got largest or larger address
36:28space
36:29so ipv6 addresses are 128 bits
36:33compared to ipv4s 32 bits
36:36this larger addressing space allows more
36:39support
36:40for addressing hierarchy levels as much
36:43greater number of addressable nodes and
36:46simpler auto configuration for addresses
36:49okay next would be globally unique
36:53ip addresses so every node
36:56can have a unique global ipv6 address
37:00which eliminates the need for the
37:02network address translation
37:05okay how about site multi-homing
37:08so ipv6 allows host
37:11to have multiple ipv6 addresses
37:14and allows networks to have multiple
37:17ipv6
37:18prefixes consequently sites can have
37:22connections to multiple isps without
37:25breaking the global routing table
37:27all right so next would be header format
37:31efficiency
37:32so a simplified header with a fixed
37:35header size
37:36makes processing more efficient
37:39next would be improved privacy and
37:41security
37:43so ipsec is the ietf standard
37:46for ip network security so available
37:50for both ipv4 and ipv6
37:53although the functions are essentially
37:55identical in both environments
37:57ipsec is mandatory in ipv6
38:01so ipv6 also has optional security
38:04headers next would be
38:07flow labeling capability a new
38:11capability enables the labeling of
38:13packets
38:13belonging to a particular traffic flows
38:16for which the sender requests
38:18special handling such as non-default
38:22quality of service or qos or real-time
38:25service
38:28the last one would be increased mobility
38:30and multicast capabilities
38:33so mobile ipv6 allows an ipv6 node
38:36to change its location on an
38:40ipv6 network and still maintain its
38:43existing connections
38:45so with mobile ipv6 the mobile node is
38:49always reachable
38:50through one permanent address so a
38:53connection is established
38:54with a specific permanent address
38:57assigned
38:58to the mobile node and the node remains
39:00connected
39:02no matter how many times it changes
39:04locations
39:05and addresses
39:10ipv6 other scope
39:13so let's talk about the ipv6 address
39:16types here
39:17this section covers various ipv6 address
39:20types
39:21and their scopes okay so ipv6 address
39:26scope types so similar to ipv4
39:30a single source can address datagrams
39:34to either one or many destination at the
39:36same time in ipv6
39:39okay so following are the types of ipv6
39:43addresses so you have the unicast or one
39:46to one
39:48similar to an ipv4 unicast address
39:51an ipv6 unicast address is for single
39:55source
39:56to send data to single destination a
39:59packet
39:59sent to a unicast ipv6 address goes to
40:02the interface identified
40:04by that addresses so the ipv6
40:08unicast address space encompasses the
40:10entire ipv6 address range
40:13with the exception of the ff
40:170 0 colon colon 8 range okay
40:20so addresses is starting with binary
40:23one one one one one one one one or all
40:27ones of eight bits
40:28which is used for multicast addresses
40:32now the ipv6 unicast addresses
40:36okay it's discussed on
40:40different types of ipv6 unicast
40:42addresses
40:43from different sections okay
40:46now this is just to give you an overview
40:48about this
40:49scope types here next would be
40:52anycast or one to nearest
40:56so an ipv6 anycast address is a new type
41:00of
41:01address that is assigned to set of
41:04interfaces
41:05on different devices and anycast address
41:08identifies multiple interfaces
41:11so a packet that is sent to an anycast
41:15address goes to the closest
41:16interface as determined by the routing
41:18protocol being used
41:20identified by the anycast address
41:23so therefore all nodes with the same
41:26anycast address
41:27should provide uniform service
41:31anycast addresses are syntactically
41:33indistinguishable
41:35from global unicast addresses because
41:38any cast addresses are allocated from
41:41the global unicast address space
41:44okay so
41:47next would be the multicast or one too
41:50many
41:51so similar to ipv4 multicast an ipv6
41:55multicast address identifies a set of
41:58interfaces
42:00in a given scope typically on different
42:03devices
42:04a packet sent to multicast address
42:08is delivered to all interface identified
42:11by the multicast address in a given
42:13scope
42:15so ipv6 multicast addresses
42:18have a four bit scope identifier or id
42:21to specify how far the multicast packet
42:25may travel okay so ipv6 has no concept
42:30of broadcast addresses
42:32multicast addresses are used
42:35instead
42:39ipv6 address types focus on the link
42:43local and site
42:44local addresses okay now for the link
42:47local address
42:48so the key point here is every ipv6
42:52enabled interface
42:54must contain at least one loopback
42:57okay so that is colon colon one
43:01slash 128 and one linked local address
43:05so optionally an interface may have
43:08multiple unique local and global
43:11addresses
43:12so a link local address is useful only
43:15in the context
43:16of the local link network its scope
43:20limits its relevance to only one link
43:24okay now a link local address is an ipv6
43:28unicast address that can automatically
43:30configured
43:31on any interface by using the link local
43:34prefix
43:35fe 80 colon colon slash 10
43:39and the 64-bit interface identifier
43:43shown on the figure okay
43:46now link local addresses are used in the
43:49neighbor discovery protocol
43:51and the dynamic address assignment
43:53process
43:55now what is a site local address
43:58so a site local unicast address are
44:01another type of ipv6
44:03unicast addresses however the use of the
44:07site local
44:09or the site local addresses was
44:11deprecated
44:13by or in september 2004 okay
44:17so site local unicast addresses were
44:20similar to private addresses
44:22in ipv4 and were used to address a site
44:26without having a global
44:27prefix okay now the site local addresses
44:31used the prefix fez0
44:35okay colon colon's last 10 and an
44:38interface identifier
44:40concatenated after the prefix so the
44:43site local addresses
44:44were considered private addresses to be
44:47used
44:48for strict communication to a limited
44:50domain
44:51so ipv6 routers must not advertise
44:55routes or forward packets that have site
44:58local source or destination addresses
45:01outside the site
45:08how about the ipv6 address types global
45:11aggregatable so let's start with a key
45:14point
45:15ipv6 global aggregatable unicast
45:18addresses are equivalent to ipv4
45:21unicast addresses so the structure
45:24of a global agreeable unicast addresses
45:27enable summarization or
45:28aggregation of routing prefixes
45:32so that the number of routing table
45:33entries in the global routing table can
45:35be reduced
45:37so global unicast addresses used on
45:40links are aggregated upward through
45:43organizations
45:44and then to immediate or intermediate
45:47level isps
45:49and eventually to top level isps
45:56ipv6 address assignment strategies
45:59so basically if you're planning to
46:02migrate or use
46:03uh ipv6 so for the static
46:06assignment it's same with ipv4 okay
46:10now for dynamic so you have to consider
46:13either
46:14the use of the link local the stateless
46:17and stateful using the http version 6.
46:24how about the ipv6 name resolution
46:28so this section discusses ipv6 name
46:31resolution strategies
46:33and name resolution on a dual stock ipb
46:36for an ipv6 host
46:38so when you have heard of the term dual
46:40stock that pertains to ipv4
46:43and ipv6 running on the network
46:47now for the ipv6 name resolution
46:50it starter it's either static or dynamic
46:54okay now static name resolution
46:57accomplished by manual entries in the
46:59host's local
47:00configuration files now
47:04dynamic name resolution accomplished
47:06using a dns server
47:08that supports ipv6 usually
47:12along with ipb4 support now as shown
47:15here in the diagram
47:17an ipv6 aware application requests
47:21the destination host names ipv6 address
47:25from the dns server using a request
47:28for an a6 record now
47:32an a6 record is a new dns feature
47:36that contains an address record
47:39for an ipv6 host so the task of querying
47:44for the address is done with the name
47:47resolver
47:48which is usually part of the operating
47:51system
47:52so the network administrator must set up
47:55the appropriate dns server with ipv6
47:58support
47:59and connect it
48:04how about ipb4 and ipv6 aware
48:07applications and name resolution so a
48:10dual stack host
48:12has both ipv4 and ipv6 protocol stacks
48:16and has a new application program
48:18interface or api
48:20defined to support both ipv4 and ipv6
48:25addresses and dns requests
48:28so an application can use both ipv4 and
48:32ipv6 an
48:34application can be converted to the new
48:37api
48:38while still using only ipv4
48:42now as shown in the figure here an ipv6
48:45and ipv4 enabled application chooses
48:48which stack to use so the typical
48:52default is ipv6
48:55okay and asks the
48:59dns server for the destination hosts
49:02address in this example it requests
49:06the host's ipv6 address
49:10okay now after receiving the response
49:14from the dns server
49:15the application asks the source host
49:18to connect to the destination host using
49:21ipv6
49:27ipv4 to ipv6 transition strategies
49:31and deployments okay so ipv4 and ipv6
49:35migration does not happen
49:37automatically the following section
49:41explores the differences between ipv4
49:44and ipv6 and then
49:46discuss possible transition okay
49:50or different strategies and deployments
49:53so the first one would be ipv4 and ipv6
49:58transition okay from ipv4 to ipv6
50:03will take several years because of the
50:05high cost of upgrading equipment
50:08so in the meantime ipb4 and ipv6
50:12must coexist all right
50:15so the following are the three primary
50:17mechanisms for the transition from ipb4
50:19to ipv6
50:21not all organization has migrated
50:25to ipv6 there are some organizations who
50:28are still running their network on ipb4
50:31okay so the first mechanism is a dual
50:35stop
50:37both the ipb4 and the ipv6 stacks
50:41run on a system that can communicate
50:44with both
50:44ipv6 and ipv4 devices
50:48okay so the next one is tunneling
50:51okay tunneling uses encapsulation of
50:55ipv6
50:56packets to traverse ipv4 networks and
50:59vice versa
51:02next would be translation this is a
51:04mechanism
51:06that translates one protocol
51:09to the other to facilitate communication
51:12between
51:12the two networks
51:16so let's deal with each of this
51:18mechanism let's start with the dual
51:20stock mechanism
51:22now as shown here in the figure a dual
51:25stock
51:26node enables both ipv4
51:29and ipv6 stocks the ipv version choice
51:33is based on the name
51:34lookup and application preference
51:38so this is the most appropriate method
51:41for campus and access networks during
51:44the transition period
51:46and it is preferred technique for
51:48transitioning to ipv6
51:51so a dual stack approach supports the
51:53maximum number of
51:55applications
51:59tunneling mechanism okay or the
52:01tunneling transition mechanism
52:04the purpose of tunneling is to
52:06encapsulate packets
52:07of one type in packets of another type
52:11so when transitioning to ipv6 tunneling
52:14encapsulates ipv6 packets in ipv4
52:17packets
52:18as shown on the speaker okay
52:21by using an overlay tunnels isolated
52:24ipv6 networks
52:26can communicate without having to
52:28upgrade the ipv4 infrastructure between
52:31them
52:32both routers and hosts can use
52:36tunneling so it's either
52:40manually configured semi-automated
52:44and automatic
52:48how about the translation transition
52:51mechanism
52:53so a dual stack and channeling
52:54techniques manage the interconnection of
52:56ipv6
52:58domains for legacy equipment that will
53:01not be upgraded to ipv6
53:03and for some deployment scenarios
53:06techniques
53:07are available for connecting ipv4 only
53:10nodes to ipv6 only nodes using
53:14translation an extension of the nut
53:18techniques
53:19now as shown on this diagram here an
53:22ipv6
53:24network or node behind the translation
53:27device has full connectivity
53:30to other ipv6 nodes and uses not
53:33functionality to communicate with ipv4
53:35devices here
53:37now translation techniques are available
53:39for translating ipv4 addresses
53:42to ipv6 addresses and vice versa
53:45similar to current nat devices
53:48translation is done
53:50at either the transport layer or the
53:53network layer
53:54so not protocol translation or the not
53:57pt
53:58is the main translation technique the
54:01dual stack
54:02transition mechanism or the dstm
54:05might also be available
54:12ipv6 routing protocols
54:16since there are protocols or routing
54:18protocols
54:19for ipb4 there are also routing
54:22protocols for ipv6
54:24so the routing protocols available in
54:26ipv6 includes
54:28interior gateway protocols or igp
54:31for use within the autonomous system and
54:34exterior gateway protocols or egp
54:38for use between autonomous systems
54:41so igp or the interior gateway protocol
54:43is used within the autonomous system
54:45autonomous system pertains to an area
54:49being maintained by a single
54:50administrator
54:52okay and between different autonomous
54:54systems basically
54:56that is where we use the exterior
54:59gateway protocols or egp
55:01specifically bgp or the border gateway
55:04protocol
55:06okay now as with ipb4
55:10uh cider ipv6 uses the same longest
55:15prefix match routing so
55:18updates to existing ipb for routing
55:20protocols
55:21were necessary for handling longer ipv6
55:25addresses
55:26and different header structures so
55:28currently
55:29the following updated routing protocols
55:31or draft proposals are available
55:34so that includes rip ng
55:37okay for uh ipv4
55:41rip version one and reversion two so for
55:43ipv6 it's
55:44rip ng okay or the new generation rip
55:50for ipb4 eigrp
55:53okay for ipv6 we also have eigrp for
55:56ipv6
55:58now ospf version 2 for ipv4
56:02and ospf version 3 for ipv56
56:05you also have the integrated isis
56:08okay so this is is here
56:12we're already obsolete but it it makes a
56:15huge comeback
56:16okay on the network that is currently
56:20being used
56:21on the implementation of the
56:22virtualization okay
56:25now for the exterior gateway routing
56:27protocol so a specific example
56:30is the border gateway protocol or bgp
56:36okay so let's summarize what we've
56:39talked about
56:40on designing ip addressing so key
56:44components
56:45of an ipv4 addressing scheme includes ip
56:47address structure
56:49address classes subnetting and masking
56:53well-designed hierarchical ip addressing
56:56enables efficient aggregation of routing
56:59advertisements
57:00which consumes less bandwidth and router
57:04cpu
57:05okay now dynamic address assignment
57:09is a recommended practice in the
57:11enterprise
57:12specifically assigning an ip address to
57:16the endnotes so dynamic name resolution
57:19with dns server
57:21is a recommended practice in the
57:23enterprise
57:25so ipv6 was designed as a successor to
57:28ipv4
57:30to overcome ipv4 limitations
57:34so the ipv6 address structure and
57:37address types
57:38supports a much larger address space
57:41than ipv4
57:42okay ipb4 you've got something like 4
57:45billion
57:46okay with ipv6 well you have
57:50100 or 340 and the
57:53so could you just imagine the address
57:55space there
57:56okay so ipv6 supports
57:59two address types the link local
58:02and the global aggregatable

About this transcript

This page contains the full transcript of Designing IP Addressing and Selecting Routing Protocols Part 1 by Santelmo, generated from the public captions YouTube serves with the video. The transcript has 6,366 words across 1,337 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.